> So sorry. That's just it. There are nothing but a lot of apologies but your apology for bad stuff doesn't make it better, it just makes me more sad that you know it's bad and you don't care because it makes _you_ feel better. that's where we're at now and it's what makes it so frustrating that the most talked about topic in software development _right now_ is agentic work with overwhelming admissions of "no team of humans could possibly review the amount of code produced" Which is arguable identical to an apology if you don't mind me stretching. Sorry it's bad but progress is progress my dude, what am I supposed to do?

Replies (1)

Hold on. I don't know that it is bad. I have standards and I am not going to push out slop for the sake of it. But I also think certain models are going to be a better coder than I ever was un short order. When I find the edge of their capabilities I back off and start that part over. My only point is that if AI can help accomplish something I think is important that I was failing to finish on my own then I am going to use that tool. But if the tool gives me crap then it hasn't accomplished the task. What I refuse is the purist standpoint that AI can't do good work. Luckily in my case, I can judge the output because I've been working on it for 10 years and have coded about 4 iterations myself. I immediately recognize all the patterns the AI is using. If it does something else it had better be able to explain why. Again the code itself is only proof of the spec. I may use it myself. But I don't want to even call it a reference implementation. It is a test implementation only.
↑