How to become a dramatically better programmer
Edit: The average piece of code is written once and read hundreds to thousands of times by people. It's not unreasonable to think of code as a read-oriented activity, not a write-oriented activity.
There's one piece of advice specific to programming which is missing from this listing: Read lots of code in lots of different languages. Aim to read, as a general rule, about twice as much code as you write, and to be able to read twice as many languages as you write in typically. Edit: The average piece of code is written once and read hundreds to thousands of times by people. It's not unreasonable to think of code as a read-oriented activity, not a write-oriented activity. This is a suggestion I see given a lot, but something that falls flat to me personally. The analogy I would put…
related reading
- Reflections on 10,000 Hours of Programming | Matt Rickardmatt-rickard.com
- Cognitive load is what mattersminds.md
- Get better at programming by learning how things workjvns.ca
- how I think when I think about programming - alice mazalicemaz.com
- How to read a codeiamjonas.me
- Essays on programming I think about a lot | benkuhn.netbenkuhn.net
- Some thoughts on writingdanluu.com
- What to learndanluu.com
- Things unlearnedscattered-thoughts.net
- Teach Yourself Programming in Ten Yearsnorvig.com
- Repeat yourself, do more than one thing, and... — programming is terribleprogrammingisterrible.com
- A Bunch of Programming Advice I'd Give To Myself 15 Years Ago | Marcus' Blogmbuffett.com