|
|
|
|
|
by SadErn
47 days ago
|
|
Every major leap forward triggers Luddism in those prone to histrionics. You have to offload cognition in order to recognize the next abstraction. That's always been how we tackle harder problems. A good explanation is foreplay, not a replacement for the act itself. If people stop there, that's a premature-pedagogy problem, not an AI problem. Somewhere, an AI is summarizing this comment for someone right now, and that person understands the issue better than you do. |
|
But developing the people [who can build great new abstractions or the people who can build those abstractions into ergonomic tooling] involves a lot of cognitive struggle through which these people learn how to push knowledge forward.
Forming the mental models for how things work takes struggle. Debugging errors in your code forces you to figure out the disconnect between your mental model and reality.
Claude can figure out most errors I show to it much faster than I can, but when we're building something I could build from scratch, I regularly find even Opus 4.7 regularly provides vastly overcomplicated and inferior solutions and I have to redirect it. I assume this is also the case when we're building stuff that's new to me and I just can't recognize all of the overcomplicated suboptimal solutions until I get to testing the behaviors I need to be correct. If I got a tool like this at the start of my career or education, I just don't know how I wouldn't end up completely stunted.