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
- Teach Yourself Programming in Ten Yearsnorvig.com
- Think real hardbenkuhn.net
- Code, Code, Codedaniel.feldroy.com
- What to learndanluu.com
- Things You Should Never Do, Part I – Joel on Softwarejoelonsoftware.com
- Fantastic Learning Resourcesmatklad.github.io
- Things unlearnedscattered-thoughts.net
- On Leetcodeplanetbanatt.net
- The Most Efficient Way to Read Code Written by Someone Else | Towards Data Sciencetowardsdatascience.com
- how I think when I think about programming - alice mazalicemaz.com
- The First Ten Yearsgregorygundersen.com