News for hackers. Stuff that matters.

A comment on Code Is Clay Now.

Re:Code Is Clay Now by sdevonoes on Thursday October 22, 2026 @09:28AM (#50195034)
> Add some polishing iterations and you have compressed a full product/engineering/QA cycle into one person and thirty minutes.

Depends, I guess. Engineers don’t typically know 100% the business rules (think fintech, payroll, etc.). You typically need to align with domain experts (and no, these people don’t write down their knowledge in confluence pages).

So, unless we are talking about simple software (things that can be broken without too much accountability) then sure

[ Parent | on HN ]
Re:Code Is Clay Now by SketchySeaBeast on Thursday October 22, 2026 @09:39AM (#50195173)
That's what I'm struggling with right now - trying to make sure all the business rules are well documented and accessible in the code so that the LLM won't just go along with whatever the next dev asks, introducing regressions. So often a "bug" is just a misunderstanding of a deliberate decision on a minute details.
[ Parent | on HN ]