‹ BackHN Continuity

Thread

The Four Horsemen of Agentic Coding

114 points · 89 comments · haute_cuisine

  1. headcanon · · focus · HN ↗
    I feel like I'm living in an alternate universe - my company has fully adopted agentic coding, we're working with:

    - large codebases

    - business critical software for clients that don't tolerate downtime

    - agentic and classical features

    We still collaborate well, we still care about quality, we still have good knowledge of the codebase, but I haven't written a single line of code myself in over a year.

    We have not had a single incident that I'm aware of where we shipped a slop and it created downtime.

    We're building a "software factory" that is currently handling low-level chore tickets and merging about 1/3rd of our PRs. A year from now I imagine it will be doing significantly more, and I don't think anyone is going to get fired because of it (if anything we'll keep hiring more).

    I don't see this as an either/or thing. If there is some hidden ocean of slop that we're bound to fall into I don't see it anywhere. Where is the disparity?

    1. distantprovince · · focus · HN ↗
      Hey, author here. You should definitely share your experience!! We really need to study more success stories so we could figure out what makes them successful.

      If it's possible I would highly encourage your company to publish something about how you work and what you think you're doing right.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.