While I think this is silly, the constant criticism and put down of AI is beyond laughable. Just this week I was able to do an extremely difficult code refactor and movement from one app to another by making it a package. Something I have done many times before and takes WEEKS of work... in under a few hours with Claude. I have easily 5x my productivity and greatly improved our app security and reliability by running local AI to run tests, checks, etc at night to find issues we may have missed.
I hear you, and I am familiar with the corporate pressure to "
use AI" that devs are under right now, but I wouldn't call it "laughable" quite yet. If anything, I find the voluntary de-skilling of devs quite concerning.
Early in my career - decades ago - I contributed many months of unpaid overtime (late nights, weekends) refactoring buggy legacy code that nobody wanted to fix. I did it because the old codebase was so unpredictable and often created production/operational
emergencies that needed the entire dev team (including me) to put their life on hold to fix. These sporadic, emergency production bug-fixes were characterized as doing the "right thing" for our customers but - to be brutally honest - it was forced on us because the customers were refusing to pay their bills. Money talks!
Anyway, I was tired of that stupid nonsense, so I gradually refactored and extensively hand-tested the entire application code base before it even went to QA. I probably spent 80% of my effort testing and trying to break my code because I wanted to refactor
once and be done. After refactoring, I owned it. Anything wrong was mine to fix. I was good with that.
Fast forward to today: When all these labor-saving "AI refactors" start failing in unanticipated production edge cases, who
owns fixing it? Or is everyone going to be pointing fingers at AI and job-hopping?
What about the customers and end-users caught up in this?