Skip to content

Comment on It took longer to get the API key

Comments

The author lives in a world where nothing has stakes. Where deploying without code review is a process optimization, not something that will break your certification on an audit and potentially the law (claude code doesn’t have a PEng cert). Where deploying a failure means that some users are mildly annoyed, rather than equipment loss and endangering lives.

It’s exactly the same high-churn no-regard-for-the-user that is modern “tech”. I would not use this approach on anything more serious than a SaaS, and I hope nobody else does either.

I think their example is a toy example but, a good analogy for what is likely to happen as AI is integrated more and more.

I try :)

I've lived the high stakes life. We can be this crazy passionate about being the HITL but that will eventually change.

Without an approved test harness? Doubtful. The exact viewpoint espoused in the article is that we should be deploying, agentically, into production, without testing, with no gating, and rolling back any failures. This is simply not a reasonable process. Current agentic development works much better with firm requirements and a solid test suite. In the future, we will still need the test suite, that is validated deterministically. Deploying bad software is not harmless.

I believe you may be mischaracterizing the article's position. It didn't advocate for deploying without testing or any of the other items you mention. Rather, it discussed how well and quick AI solved a problem. There's an important distinction between what was actually proposed and the extreme position you're describing.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.