Live data from Hacker News

The Struggle Is Gone

dogdogfish.com

21–26 of 26 posts

Re: The Struggle Is Gone

#21

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.

Curious and fun intellectual exploration is my modus operandi too, but there is something to be said about struggling for weeks on a single idea and experiencing an Aha! moment which surely elevates your intellect in a way fun exploration does not.

Re: The Struggle Is Gone

#23
post #6

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…

> grind these problems so the pain sticks with you

The reason you grind on a problem is because it is difficult and requires you to learn and bridge knowledge. You're not grinding through many problems for the sake of it you're doing it because they're challenging and slightly different each time.

Re: The Struggle Is Gone

#24
post #9

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…

My experience as well (30+ years developing software for a living).

I have tried everything from generating a complete, detailed spec using AI and then one-shot generating the code, to generating code one step at a time with me reviewing each result.

The speed is pretty much the same. But generating code one step at a time is IMHO vastly superior because I deeply understand the code and can easily fix issues that the AI get stuck trying to fix.

Re: The Struggle Is Gone

#25
post #9

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…

I feel like there is room for a "Slow Movement" in the age of AI/online these days.

https://en.wikipedia.org/wiki/Slow_movement_(culture)

Post reply on HN