‹ BackHN Continuity

Thread

The Normalization of Inexplicable Failures

277 points · 124 comments · pxx

  1. pmarreck · · focus · HN ↗
    I am big on reproducibility (nix aficionado) and determinism (flagging test failures are a red-alert, all-hands-on-deck situation in my world) and correctness.

    I am also big on testing (the correct things). And nine-nines (big on Elixir).

    And... I'm also big on agent-assisted dev. Which requires pretty much every check in the book to stay productive in. And that's fine to me. I've seen bugs that I wouldn't have made myself. And I've also seen my own bugs fixed. They've all gotten fixed in short order. I don't see why this is a problem.

    Raise your personal standards.

    Thing is, the unreliable-software situation was already untenable before agents (in poor hands) made it worse.

    1. joe_the_user · · focus · HN ↗
      Thing is, the unreliable-software situation was already untenable before agents (in poor hands) made it worse.

      Yes but that's the big thing, now isn't it? These are nice tools, used wisely. But their unwise use, oh boy...

      The problem is one needs to be in a situation where the incentive is towards quality rather than speed. But that situation rather rare now - thirty years ago, Microsoft won the office wars with crap that had features. And nothing has fundamentally changed in web development since the LPad crisis.

      The problem is those companies whose incentive is to allow bugs where it's the involuntary users who suffer will bite you no matter what quality you make your own software.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.