Posted by craigmart 8 hours ago
https://github.com/gregwebs/skills-sdlc/blob/main/skills/ver...
The implementation process that I am using also looks for verifications during planning and reviewing and makes sure they are completed. It does use a lot more time and AI spend than just asking AI to do something. I still do the latter for simple or noncritical changes. I had to switch to using DeepSeek as my workhorse to keep down my spend.
https://github.com/gregwebs/skills-sdlc/blob/main/skills/imp...
They won’t even do all this verification nonsense and their end product will be of superior quality.
Who ever had the time and will to write unit tests that mock every single function/class being called, checks the strings of thrown errors, etc., for every single function, for several tests per function?
The instant you change the implementation the tests break because it's testing how many times each method has been called of an object that was passed as argument.
That's just an insane way of writing tests. But for AI that's normal for some reason.
It feels like it's making unit tests the "textbook" way that in practice you wouldn't do because in practice half the things it's testing are inconsequential.