alt Hacker NewsI think we're going to agree to disagree. Not that I find fault in your argument (we're both debating our opinions), but I'm concerned about reliability of the tool first.
My workflow is centered about a correct output, not speed or efficiency. But what makes it easy to get correct result makes it easy to be fast and be economical in resource consumption too. Except that you need to average over the usual period of times you need to support a project (months or years). Nice tricks like slinging a PR over the wall in a day don't matter if it's not sustainable.
Things like writing code that's been written over and over again also don't matter. It's either I know how to do it (or at least the general pattern). And then it will be a walk in the park (some relax period even, like walking between bouts of running when jogging). Or I don't know the pattern and I need to be careful to get it right.
So what saves me time ultimately the reliability of my software. When I'm not busy fixing stuff right and left and can be fairly confident when releasing. I've not found any methodology that helps with that with AI tooling being actually helpful in that regards.
I don’t know anything about your work so I can’t speak to that. What I do know is that intentionally pushing my use of AI (to the point that at times it was clearly a detriment) taught me a lot about how I can use it effectively, how I cannot, and sometimes where I still need to invest to be more effective with it. AI is not magic but it has proven very useful in many cases (not all cases) for me.
But yes, agree to disagree. I’m not here to evangelize AI and I hope you have success regardless of whether you use AI coding.