I'm simultaneously frustrated and I see a business opportunity - I now know that we senior folks are very far from replaceable - and soon there might be consulting to fix big problems. No one will say it's AI's fault necessarily - you'll just be living with painful complexity that works for a startup or an individual entrepreneur but not in an enterprise environment. To wit:
>The person adding Kafka should have been able to explain exactly why it was needed.
Here it is. People who don't know what they are doing are adding infrastructure layers they don't understand, can't envisage operationally in the future, and missing scalability. I'm seeing this. In fact I'm spending hours a week fighting it. I had to set up a call with a senior developer recently to explain why his prescriptive attempt to make infrastructure changes in his project can't be done with Claude like he did it.
It's playing wack-a-mole as the "velocity" has gone up of changes, and it's promulgated by every manner of product manager and senior developer under an attempt to please the brass.
>The person who built the feature should have been able to explain where the data came from without sending a link to a Claude conversation.
And they won't - because it's too embarrassing when you see what Claude responded with and someone failed to question.
We're in a new era, that's for sure.