I feel like an entire generation of coders now have experienced "reading requirements and checking manuals / StackOverflow to fill them" and no idea at all abou

I feel like an entire generation of coders now have experienced "reading requirements and checking manuals / StackOverflow to fill them" and no idea at all about "studying a problem space and designing software to fit there" .. Early literature was filled with observations of coders as engineers plus computer language users. Not so much today, now it is "who can read the newest AWS service manuals and write microservices to respond to it" .. this conversation about Copilot is constantly in a disconnect between form generators + web client writers + AWS jockeys who want pro-forma solutions cheaper, and domain experts or science implementors. An imperfect analogy comes to mind between textbook authors, and people who write small commercial things under someone's direction. The wailing and outcry here is to protect skilled work from being raided (like a crucial piece of code that solves something difficult or special), or the income of people who do skilled work (authors that are committers to non-trivial libraries), not so much about low-cost javascript writers or in-house forms generation code for business processes.