I thought this was a good read. From my experience and to my dismay, what is considered a "good" or "bad" engineer/developer can be surprisingly subjective. I completely agree that an engineer should never submit a massive PR and instead break the work down, question, and understand the AI-generated code. I also agree that any reviewer should push back on being asked to review that and request the PR to be divided up. Unfortunately, what I've seen happen is that someone else with more power in the organization might find that PR fine and approve it and management might be raving about how good (fast) said engineer is. Those weird bugs which appear down the road get offloaded to other engineers.
Faced with that situation repeatedly, most people would find it sensible to resign.
Which leads me to another point: if you leave, it will likely be difficult to land another job assuming that companies will impose a ridiculous interview process in fear of a bad hire which will be increasingly expensive as the author argues.
I realize that this is nothing new, but if there are fewer middle-class engineering roles, then I expect that these existing problems to become amplified.
Faced with that situation repeatedly, most people would find it sensible to resign. Which leads me to another point: if you leave, it will likely be difficult to land another job assuming that companies will impose a ridiculous interview process in fear of a bad hire which will be increasingly expensive as the author argues.
I realize that this is nothing new, but if there are fewer middle-class engineering roles, then I expect that these existing problems to become amplified.