21
submitted 1 month ago* (last edited 1 month ago) by ueiqkkwhuwjw@lemmy.world to c/selfhosted@lemmy.world

According to the release:

Adds experimental PostgreSQL support

The code was written by Cursor and Claude

14,997 added lines of code, and 10,202 lines removed

reviewed and heavily tested over 2-3 weeks

This makes me uneasy, especially as ntfy is an internet facing service. I am now looking for alternatives.

Am I overreacting or do you all share the same concern?

(page 3) 25 comments
sorted by: hot top controversial new old
[-] Dojan@pawb.social 0 points 1 month ago

Send push notifications to your phone or desktop using PUT/POST

I'm sorry, how many lines of code for that?

load more comments (1 replies)
[-] melroy@kbin.melroy.org -1 points 1 month ago

Ai can be powerful and destructive at the same time. (note: I didn't use Ai to write this).

Ai coding can help a lot in accelerating software development. In the right hands that is. Meaning the software engineer still reviews the code. Test it. And takes responsibility. In those cases there is nothing wrong with using Ai for software development.

The problem is that some programmers are using AI without even looking at the end results. Just approves everything, commits, push and release. That approach is wrong and especially inexperience engineers might fail into this trap. So in this case the code has most likely a lot of duplicated code, full with bugs and other issues. Some issues you encounter it for the first time, since it wasn't tested etc.

In the latter story, you feel the impact. And the downsides of Ai. And only see the negatives of Ai. You might say it's Ai slop even. Or vibe coded. Which is correct.

Tldr: Ai can be very powerful in the right hands. It still requires a lot of human time and effort to get it correct. And if the engineer is too lazy then you feel the consequences. If you got an experienced software engineer that takes the responsibility of the code. Reviews it thoroughly. Test all corner cases, etc. Then AI can be powerful and helpful.

[-] ExFed@programming.dev 0 points 1 month ago

Agreed. I have a sense that, eventually, development communities will figure out etiquette and policies to govern LLM usage. But how do you enforce that kind of policy? Right now, it's essentially a judgement call by the maintainers. It's hard to catch sneaky LLM usage.

On the other hand, I think there are objectively good ways to use LLMs for software:

  • High-level design and planning
  • Technical Research (although this tends towards the most popular tech)
  • POCs & rapid prototyping
  • "Textbook" solutions
  • TDD Red/Green development (where the LLM generates failing tests based on the high-level spec, and the programmer writes the implementation)
[-] melroy@kbin.melroy.org 0 points 1 month ago

Indeed also read the paper called Programming as Theory building. From 1985. Which is very relevant today again. Since people lose the connection with the code due to Ai.

load more comments (3 replies)

Lot of hate for a project maintained by a volunteer and offered for free here. Nobody forces this free stuff on you.

[-] deathbird@mander.xyz -2 points 1 month ago

"but reviewed and heavily tested over 2-3 weeks by me. I created comparison documents, went through all queries multiple times and reviewed the logic over and over again. I also did load tests and manual regression tests, which took lots of evenings."

This is the way.

[-] douglasg14b@lemmy.world -1 points 1 month ago

Pretty much.

I've started using AI on a project last week and the first thing I do is write tests. Lots of tests.

With enough guardrails, you could actually get pretty decent quality output out of it and with enough regression tests, you can ensure that nothing's actually breaking.

Similarly, reviewing its changes and actually reading the code that's being generated to ensure correctness is necessary. However, I am finding ways to automate that and reduce the incident rate of problems to even lower than my co-workers.

load more comments (4 replies)
load more comments (3 replies)
load more comments
view more: ‹ prev next ›
this post was submitted on 08 Mar 2026
21 points (92.0% liked)

Selfhosted

58915 readers
37 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS