470
ntfy.sh v2.18.0 was written by AI (github.com)
submitted 6 months ago* by to c/selfhosted@lemmy.world
183 comments fedilink hide all child comments
 

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?

you are viewing a single comment's thread
view the rest of the comments
[–] 43 points 6 months ago (7 children)

Test in production is the best. We spent months warning from data bugs and nobody bat an eye (upstream bug, not our responsibility but we noticed) When it was d launched in prod we just pointed out the bug that nobody fixed was still there and immediately a war room was formed and the bug fixed within an hour.

It honestly seems more efficient to let shit hit the fan than to fight everybody to do their job.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] 3 points 6 months ago* (3 children)

    Testing in production is the most idiotic last 10 years or so concept, which is mainly driven by incompetence of project managers.

    Imagine if you get sold a car by a company, for 100k, then it starts having major issues and the car company tells you: "we'll fix it".

    While that does not necessarily apply to software or services or webapps, the logic still stands. You are selling bugs to people. Bugs that could have been cought, with some risk management and planning.

    Edit: F-ing ios keyboard.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 3 points 6 months ago (2 children)

    which is mainly driven by incompetence of project managers.

    I completely agree. I work on an internal solution, which is a part of a very large product. It's not a live product, only part of a pipeline that runs on a predetermined schedule. Our bit is the only one with actual business/performance KPIs, most of the other teams measure only "user story/CR points". If the other teams screw up, it will impact our performance unless we prove it's their fault. And of it's their fault, they open a US/bug which improves their metrics (one more US closed). Our team has to think ahead and try to do things well in one go, because our bugfixing doesn't count as work. But our speed is measured against people who benefits from half doing stuff. When we did massive effort, we got complaints we were slow. Now we do less effort and once every blue moon we have to do a hotfix. Most often than not when we have an production issue is due to the other teams that run before us on the pipeline, so we even had to develop checks to our input because they won't add checks to their outputs. And they won't because that's a CR that requires extra funding that's not approved, but we had to create them for our own sanity.

    Yes, I'm looking to move out haha

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 6 months ago (1 child)

    A project is as good as its weakest point. While people might get butthurt by getting pointed at, a project is a group effort. Segregated teams are always a problem and almost always becomes a vulnerability,

    Given current micro services architectures, we all have to get along with each other,for the greater good and the interest of the customer.

    You sell shit, you get shit back. You sell high quality products with less obvious faults, you profit in the long run.

    But no: "Let's test in production"...

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 6 months ago

    Again, I agree and I've fought for that. But this needs to be top to bottom. We have budget slashed, morale in the ground across the board. Those who keep trying for the best fight a losing battle with those who already have up trying.

    If the bosses don't care about the interest of the "customer", I don't either. I've already openly spoken to my team saying I'm now ready for things to blow up and get the attention we need from the ones really high up. I'm done working overtime because anther team is already working overtime in something else or because some bullshit political 4D chess were they throw us under the bus for their failings or try to make theirs our work.

    Had an annoying day with this things, sorry for dumping this here haha

  • permalink
  • fedilink
  • source
  • parent