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. pranshuchittora · 1790675518 · focus · HN ↗

            I think verification is still a grey area in the agentic software dev. QA and ppl testing it often resort to coding agents for the QA work, and we all know how good agents are at convincing themselves.

            1. pranshuchittora · 1790675551 · focus · HN ↗

               -

               1. 2muchcoffeeman · 1790676855 · focus · HN ↗

                  The solution is testing it yourself, not more AI
         2. 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.

      2. lelanthran · 1790677098 · focus · HN ↗

         No matter how many times this is said, the reality is that it is not true: no one will get blamed if the AI can be blamed.

         1. darkwater · 1790678221 · focus · HN ↗

            Wrong. They will be totally blamed. And the pushback will be that management forced me to use AI and go fast. Then, management will be the one NOT being blamed for this.
      3. Macha · 1790677699 · focus · HN ↗

         And in many companies, if they move at a responsible speed (rather than the speed the AI vendors promise, if you let their tools work in yolo mode), that person will get replaced by someone who will just yolo it
      4. fernandotakai · 1790680323 · focus · HN ↗

         there's a LOT of push from vibecoders to stop with PR reviews.

         i've also heard "the prompt is the only thing that should be reviewed"

      5. PunchyHamster · 1790681581 · focus · HN ↗

         Just blaming AI seems to be the norm now, we have companies literally hacking other companies by "rogue LLM" and not getting any responsibility for it
   2. phoghed · 1790679220 · focus · HN ↗

      <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=23097459">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=23097459

      1. rvz · 1790682197 · focus · HN ↗

         So we have not learned anything since then, on both sides from the SDK builder side and the client side.

         Why is it that iOS is crashing but not Android?

         Google should know better to not have such an incident like this as the Firebase SDK runs on millions of apps.

         If you did not implement a fall back mechanism, perhaps you based your testing assumptions on that “Firebase could never crash my app” which is now false.

Unofficial Hacker News client; not affiliated with Y Combinator.