11–20 of 26 posts
So, I don't think that struggle-based learning is the only way of learning or even the most efficient way of learning.
I think that this idea is more of a social ritual, than an actually useful method.
For me personally, most of skills that I managed to acquire (including coding) came from satisfying my curiosity and messing around with things to see how they work. So, I don't think that struggle-based learning is the only way of learning or even the most efficient way of learning. I think that this idea is more of a social ritual, than an actually useful method.
One can travel from one end to the other.
For me personally, most of skills that I managed to acquire (including coding) came from satisfying my curiosity and messing around with things to see how they work. So, I don't think that struggle-based learning is the only way of learning or even the most efficient way of learning. I think that this idea is more of a social ritual, than an actually useful method.
I found a spectrum - starting from copying and not understanding things through to fully internalising them. One can travel from one end to the other.
I was talking about being curious, how something works and figuring it out and being curious why something is done one way and not the other and figuring it out.
We need to seriously (or at least try to) make changes to our pedagogical processes. Yea, struggling, is one way, but there are others like optimizing for spaced reptition, visualization, etc. The shift should be from "grind these problems so the pain sticks with you", to "create a mini logic board in minecraft to blow up that mountain". Or, "build mini simulations to show how forces work, and tie them to an interact…
The discourse surrounding education is mostly a discourse of spectators. The voices who actually do the work of teaching are the quietest.
There's always struggle. Technology just moves the point at where it starts. Your decision is if you want to venture into those areas or are you content in staying in areas that are comfortable. But that has always been the case. Most people didn't struggle with differential equations, because they never decided to go there.
I have read and heard takes similar to OP's probably 50+ times from different people in the last few months (and years, now), and I agree mostly.
But I can't get over the myopic nature of this perspective. Technological advances often change the nature of work, and therefore change the nature (or location) of the "struggle".
I can imagine some hunter-gatherers probably admonishing early farmers at the dawn of agriculture for losing the "struggle" of hunting and foraging for their own food. It's much easier to drive a car than tame, train, and ride a horse. And so on throughout time.
So now with AI, some things that were hard before are now easy. So we move on to the next hard thing that maybe before was impossible or unimaginable. There is still hard work to be done.
Earlier quoted context omitted.
Doing only interesting things tends to leave students with serious knowledge gaps. Anyone that's an autodidact or has interviewed/trained one will be familiar with this.
Discipline and grit are perhaps the greatest predictors for success. High intelligence and the foresight to know what to work on, per Hamming, will get you much farther, but with discipline and grit alone your chances of failing completely and ending up in the poor house are much reduced.
Earlier quoted context omitted.
I found a spectrum - starting from copying and not understanding things through to fully internalising them. One can travel from one end to the other.
I'm not sure what do you mean by copying. I was talking about being curious, how something works and figuring it out and being curious why something is done one way and not the other and figuring it out.
You can implement a full HTTP server from scratch without learning one bit of the HTTP spec by just asking the AI tool you’re using to correct itself until tests pass. At the end you have an HTTP server, you didn’t grow doing so.
HN front page has a story about Bun being rewritten to Rust. How much of rust did the author of that PR learn by doing that process? I would say very little. If they were doing that process without AI they would very likely be Rust expert once done given the complexity and size of the codebase
As an ancient one (graduated college 1981), my use of AI is very conservative: look things up. Generate code I can read and understand in less than 30 minutes. This is working well for me, because when the AI botches the answer, I know quickly. It either works or fails fast: there's no importable function by that name, that keyword isn't in the language, that only works in a different version of the OS. I never ask i…