Remix.run Logo
▲ lkjdsklf 3 hours ago

You're not wrong, but even if you were, no... reading documentation, even good documentation, is not enough to prevent skill atrophy.

There is literally decades of research into this at all levels of education. You absolutely "lose" skills that you don't practice and reading documentation is not the same skill as writing/reviewing code. Active learning vs passive learning.

It's the reason "note taking" was invented and we don't just sit there and listen to lectures.

It's pretty shocking how many supposedly smart people are just forgetting very basic things that are literally things you learn in middle school.

▲seanw444 2 hours ago | parent [-]

The note taking analogy is the best one I can think of. It's directly analogous. Plenty of people have heard of "writing notes by hand builds stronger links in your brain" in the context of schooling, but when it comes to programming, they can't draw the painfully obvious parallel.

Really the goal is to have these models completely replace software engineers altogether. Skill atrophy isn't a concern when you don't employee devs whose skills need to be prevented from atrophying. A lot of devs also can't draw this obvious conclusion.

It's weird feeling like the odd man out with these two conclusions on the matter. But software devs are stuck in the fantasy of "this makes me a 1000x engineer and it's a tool that works for me, for my benefit". Which, sure, when you use it as a research tool, I can agree. Agentic code generation, if it doesn't outright replace engineers, will be seen as the tiktokification of programming, and its effects will become obvious, hopefully in the not-too-distant future.