To me, this is no different than the c/c++ crowd screaming "But you need to understand types and memory management" to the Type-safe Managed Memory Language crowd.
Problem solving remains the primary skill. You're just working in a different medium. Instead of code, it's design and specification (which you should have been doing in the first place instead of firing it out on demand as fast as your fingers move and insisting your teammates get in the groove).
If you're worried that you won't be able to understand why generated code isn't behaving properly, pro tip: Ask mode > ask the LLM to map possible reasons why the code does this when it should be doing that. Your ability to target the 'right' problem area earlier vs later is a matter of experience, as it always has been.
And you have to spend more time being intentional about setting up context / rules to define your application-specific design patterns.
For the young-uns, they need to learn their own way to leap frog over the paradigms we were trained on. We should be honest with them and ourselves that those paradigms are obsolete. As is winding core memory by hand. As Musk has said, one day there will be no apps, just a model. We're not there yet but this is the future.
> AI-assisted coding is accelerating skill atrophy for developers who haven't built the foundations yet
I'd argue that this is true also for seasoned developers.
One thing I noticed (and annoys me a lot) after almost 1 year of ai-assisted coding on daily basis is that it's incredibly tiring to do the job yourself if the tool doesn't do what you want or how you want.
Problem solving remains the primary skill. You're just working in a different medium. Instead of code, it's design and specification (which you should have been doing in the first place instead of firing it out on demand as fast as your fingers move and insisting your teammates get in the groove).
If you're worried that you won't be able to understand why generated code isn't behaving properly, pro tip: Ask mode > ask the LLM to map possible reasons why the code does this when it should be doing that. Your ability to target the 'right' problem area earlier vs later is a matter of experience, as it always has been.
And you have to spend more time being intentional about setting up context / rules to define your application-specific design patterns.
For the young-uns, they need to learn their own way to leap frog over the paradigms we were trained on. We should be honest with them and ourselves that those paradigms are obsolete. As is winding core memory by hand. As Musk has said, one day there will be no apps, just a model. We're not there yet but this is the future.