For junior developers, I absolutely agree that's a major risk, and it's something I'm deeply worried about as these tools take over the industry, as understanding those details helps inform why a given architecture is needed.
For someone who's been around the block a few times, there's little new under the sun. Coming up with good architecture for a problem space and having the LLM fill in the details is incredibly effective as a pattern.
That said, tbh I'm not sure why we keep exchanging messages. Your other comment about coding with AI assistance as being akin to buying a statue tells me you have either never coded with an agent, and so think it's a simple matter of saying "build me a to-do app" and then calling it a day, or you're experienced with these tools and deliberately misrepresenting the process.
If it's the former, then we don't share enough understanding to have a healthy conversation, and if it's the latter then there's little point in arguing with someone who insists in doing so in bad faith.
For someone who's been around the block a few times, there's little new under the sun. Coming up with good architecture for a problem space and having the LLM fill in the details is incredibly effective as a pattern.
That said, tbh I'm not sure why we keep exchanging messages. Your other comment about coding with AI assistance as being akin to buying a statue tells me you have either never coded with an agent, and so think it's a simple matter of saying "build me a to-do app" and then calling it a day, or you're experienced with these tools and deliberately misrepresenting the process.
If it's the former, then we don't share enough understanding to have a healthy conversation, and if it's the latter then there's little point in arguing with someone who insists in doing so in bad faith.