If you are submitting AI Slop code or overuse AI then you are a liability.
If you don't use AI at all you might be 5 or 10% slower, but quality might well even make up for it.
If you don't use AI at all you might be 5 or 10% slower, but quality might well even make up for it.
If you know them, AI supercharges you. If you don’t, you’re a lost cause no matter what.
That's kind of my point. There are junior engineers how have to go through a learning phase. Also, you may have this insight, but their managers may not.
For instance: my employer seems actively hostile to maintaining human understanding, even before AI. Ownership of apps moved around without sufficient knowledge transition or training. We've migrated Wiki systems 2 or 3 times over my career, and stuff always gets lost. The last migration (to SharePoint) was downright hostile: it was presented as an opportunity to "clean up," the half-ass automated migration deliberately excluded things more than a year old, and your docs got nuked unless someone was paying attention to save them (not a given). Now that SharePoint is in the cloud, its admins are actively scanning for things to delete, because the priority is minimizing their storage costs, not, you know maintaining knowledge of how things work.