What Problems to Solve (1966)(genius.cat-v.org)
456 points by jxmorris12 | 54 comments
A 1966 letter from Richard Feynman to former student Koichi Mano advising him that worthwhile problems are ones you can actually solve, hosted on cat-v.org.
First screen, captured .
Looks similar
William Gibson Reads Neuromancer (2004)(bearcave.com)
295 points by exvi | 84 comments
The Humble Programmer (1972)(cs.utexas.edu)
104 points by squircle | 28 comments
Related stories
“Your frustration is the product”(daringfireball.net)
492 points by llm_nerd | 300 comments
A Daring Fireball post by John Gruber linking Shubham Bose's essay on news sites like the NYT loading 49MB and hundreds of requests, criticizing ad-laden web bloat.
Why Haskell?(gtf.io)
387 points by mesaoptimizer | 533 comments
A long personal essay arguing why Haskell is a practical, productive language for building real software like web servers, covering fewer mistakes and easier reasoning.
Feynman’s Razor(defenderofthebasic.substack.com)
327 points by mmoustafa | 117 comments
A Substack essay titled "Feynman's Razor" arguing that if an expert can't understand your explanation, you've dumbed it down too much.
Programming Still Sucks(stvn.sh)
640 points by jeromechoo | 308 comments
A blog essay by Steven Langbroek titled "Programming Still Sucks," an 8-minute read on programming, leadership, and AI.
Writing summaries is more important than reading more books(andreasfragner.com)
350 points by 42point2 | 152 comments
Andreas Fragner's blog post arguing that writing summaries of good books yields more comprehension than reading more books.
Neural networks are clean(already-clean.goodfire.com)
768 points by themgt | 300 comments
An informal research essay by Nick Cammarata at Goodfire arguing polysemanticity stems from fixable issues, not superposition, making neurons interpretable at scale.