It certainly makes it all the easier for people predisposed to this quality of work.

I have learned the hard way that "corpo code" is ephemeral. I spent at least 2 man-years on Ruby/Rails code for Desk.com, once spending an entire month to solve a really bad and intermittent session-logout issue that stumped 8 developers before me (I could tell because they left a bunch of commented-out debug code and I had the git-blame lines), and after I left, that whole stack got retired and its clients moved to some garbage Salesforce offering as part of their crufty Java monolith. (Sorry, SFDC.)

So if we move from "bespoke handcrafted code" to "roughly-engineered, unstylish but still quite working LLM-generated code" in that space, there is LITERALLY no love lost.

Spend your handcrafted love-energy on open-source or library code that will stick around. Leave the corpo code to the LLMs, I say, especially if you don't own it.

Way too many people like to reach for the easiest path. They will often assume or have blind faith that the AI or online answer is correct. Coming up with the solution themselves or taking time to understand why something might be the correct answer, can be just too much work to be bothered with.