✳flâneur — a map of the web's best reading
In defense of blub studies | benkuhn.net
benkuhn.net · 2,192 words · saved by 4 readers
Why it’s worth it to deeply understand the fiddly, boring-seeming details of the computer systems you use every day.
Sometimes people ask me what they should learn to become a better programmer. I feel like the default recommendation here is usually an obscure programming language or a textbook on some high-powered machinery like ML. So I always feel a little bit embarrassed and boring when I instead suggest going really deep on what you already know: your main programming language, web framework, object-relational mapper, UI library, version control system, database, Unix tools, etc. It's not shiny or esoteric, but for me, building a detailed mental model of those (and how they compare to alternatives) migh
Explore this link on the map →saved by
related reading
- Computers can be understood - Made of Bugsblog.nelhage.com
- Things unlearnedscattered-thoughts.net
- Get better at programming by learning how things workjvns.ca
- how I think when I think about programming - alice mazalicemaz.com
- What to learndanluu.com
- Reflections on 10,000 Hours of Programming | Matt Rickardmatt-rickard.com
- So you want to be a wizardjvns.ca
- How To Learn Stuff Quickly • Josh W. Comeaujoshwcomeau.com
- Teach Yourself Programming in Ten Yearsnorvig.com
- What every computer science major should knowmatt.might.net
- Learnable Programmingworrydream.com
- Introductionthird-bit.com