Thread

1. rvz · 1790673575 · focus · HN ↗

   Keep vibe coding and breaking everything.

   This will be the new normal as all human “engineers” from staff to seniors are now down levelled to interns and junior engineers when using AI; unable to understand what they are doing and pushing broken updates like this into production with “agents”.

   Better not blame Claude on this outage.

   1. pranshuchittora · 1790674988 · focus · HN ↗

      No matter who writes the code, the name in the commit is responsible as well as the person who approved / reviewed the PR.

      1. swiftcoder · 1790675380 · focus · HN ↗

         The coding side of this isn't even the problem - that a broken change like this made it to production is an operational failure.

         Why didn't testing catch this? Why was there no canary? How come alarms didn't wake up an on call as soon as the call-volume on the backend dropped? Why was this update rolled out to every customer at once, instead of gradually?

         1. gib444 · 1790676189 · focus · HN ↗

            Why pay for and bother with all of that when you can outsource it to your users?

            Users who will forget about it, and due to inertia stay on your platform.

Unofficial Hacker News client; not affiliated with Y Combinator.