

First, I don’t understand why processors give a fuck. Do they imagine people are going to just stop using credit in protest of how other people spend their money? Tell me another fucking joke.
Second, I’m not a game developer, but I suddenly want to make a horror game that includes graphic, exploitive, gratuitous depictions of everything they complain about. And name the game Collective Shriek.
In a similar situation. I’m even an AI proponent. I think it’s a great tool when used properly. I’ve had great success solving basically trivial problems with small scripts. And code review is helpful. Code complete is helpful. It makes me faster, but you have to know when and how to leverage it.
Even on tasks it isn’t good at, it often helps me frame my own thoughts. It can identify issues better than it can fix them. So if I say here is the current architecture, what is the best way to implement <feature> and explain why, it will give a plan. It may not be a great plan, but as it explains it, I can easily identify the stuff it has wrong. Sometimes it’s close to a workable plan. Other times it’s not. Other times it will confidently lead you down a rabbit hole. That’s the real time waster.
“Why won’t the context load for this unit test?”
You’re missing this annotation.
“Yeah that didn’t do it. What else.”
You need this plugin.
“Yeah it’s already there.”
You need this other annotation.
“Okay that got a different error message.”
You need another annotation
“That didn’t work either. You don’t actually know what the problem is do you?”
Sad computer beeps.
To just take the output and run with it is inviting disaster. It’ll bite you every time and the harder the code the worse it performs.