zlacker

>>strayd+(OP)
I really wonder why nobody is talking about how it is more important to be able to test the code.

9/10 my ai generated code is bad before my verification layers 9/10 its good after.

Claude fights through your rules. And if you code in another language you could use other agents to verify code.

This is the challenge now, effectively verify the code. Whenever I end up with a bad response I ask myself what layers could i set to stop AI as early as possible.

Also things like namings, comments, tree traversal, context engineering, even data-structures, multi-agenting. I know it sounds like buzzword, but these are the topics a software-engineer really should think about. Everything else is frankly cope.

>>jwpapi+ms
I think people attacking "don't read the code" are not considering the status quo - they're comparing to some perfect world where staff engineers are reading every line of code. That's not even close to happening. Test-driven development is something most engineers just won't put up with... AI's will do it, no problem. If I can automate ten different checks for every commit, is my code really getting looked at less?