The Struggle Is Gone
matthewsharpe3
28 points
8 comments
May 10, 2026
Related Discussions
Found 5 related stories in 90.1ms across 8,303 title embeddings via pgvector HNSW
- Uncle Bob: It's Over lopespm · 57 pts · May 03, 2026 · 44% similar
- Struggle Against the Gods marcofloriano · 52 pts · April 08, 2026 · 44% similar
- Gone but Not Forgotten: Recovering the Dead Web bookofjoe · 11 pts · April 30, 2026 · 43% similar
- Dynamics of (Not) Being Perceived: Grief and Relief After Leaving Social Media glovink · 21 pts · April 05, 2026 · 43% similar
- The Death of Scrum – Built for a slower world, performed by those who left mantyx · 36 pts · May 03, 2026 · 42% similar
Discussion Highlights (6 comments)
Ancalagon
Very realistic and grounded take and I totally agree. And the ride just seems to keep moving faster.
nelsonfigueroa
> "But I do think it has become increasingly difficult to struggle for prolonged periods of time on a problem, now that we know the answer is often a few keystrokes away." Yeah this has been my experience too.
ares623
I'd be curious on the author's views of their own child's education. I wonder how "along for the ride" he actually is.
preommr
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 interactive applet".
eggplantemoji69
Think ‘all is well’ now while ‘struggling’ generations are still alive and working. When they go away I’m more concerned. We may have to intentionally suppress tool access in education eg like certain levels of calculators being permitted for math classes, limit llm assistance similarly.
thyrsus
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 it to do something I couldn't do myself in 10x the time (spent fixing typos or missing punctuation). If I ask it to do something I don't know how to do, I create tests - usually informal - to ensure that I understand what the code is doing. If the syntax is unfamiliar, I make it explain what it's doing, and then I informally test that explanation (usually toy examples at the command line). You must learn to do these things regardless of where the answers come from - the Internet, a journal, a book, a colleague. Otherwise >>when<< it fails, you will not be able to reason about the causes for the failure and how to find a correction.