Then think about whether there are other, better ways, to accomplish those goals, assuming you still want to reach those goals. That can inform how you modify your SDLC.
Does it use dependency injection as we set it up? Are domain/data/presentation classes in correct modules? Is the data flow hierarchy correct according to clean arch? Are unit tests written, is the code coverage better or at least the same? Are classes doing specific things named according to patterns how we name them? Is everything generally following the same pattern as the rest of the project?
Code is mostly about patterns, and if you know the pattern, making sure the AI agent follows it gives you the peace of mind that you can also manually check and understand it later. Everything else is a fine detail, and at the moment, this is something that I don't think is that important unless you have specific bottlenecks or issues, which again... you fix with a new prompt...
Seems like a bad practice. I recently worked through a major security regression with OpenCode that requires understanding more details. Then their platform got hacked a couple days back. Too much eyes / brain free coding will come back to bite you.
It's cheaper to create than it is to understand, so if you have no understanding in your SDLC, you can't expect to have it on incidents.
This is going to lead to more hacking incidents and give the entire industry a bad rap, which will invite more intense regulation. Do you want HIPAA for all of software development? We'd best not be so cavalier or we earn what society legislates on us
I disagree, humans are social creatures, we have many constructs developed over millennia to lean on. This is where social media borks us, but we can step back from that as well and return to more IRL interaction. It's already started, more people are giving up or reducing social media time.