On bad advice
Like many programmers, I'm largely self-taught. I've rarely worked with anyone more experienced than myself, especially early in my career where I spent a lot of time working with other 20-something-year-olds who also had only a few years of experience. So we all learned about how to program from advice we found on the internet, especially posts that were shared via sites like reddit and hacker news.
This post is part of a series, starting at Reflections on a decade of coding . Like many programmers, I'm largely self-taught. I've rarely worked with anyone more experienced than myself, especially early in my career where I spent a lot of time working with other 20-something-year-olds who also had only a few years of experience. So we all learned about how to program from advice we found on the internet, especially posts that were shared via sites like reddit and hacker news. Much of my progress since then has been unlearning all those things. In hindsight, most of the writing and discussion
Explore this link on the map →related reading
- Advice for new software devs who've read all those other advice essays • Buttondownbuttondown.email
- Reflections on 10,000 Hours of Programming | Matt Rickardmatt-rickard.com
- What to learndanluu.com
- 100 Tips for a Better Life — LessWronglesswrong.com
- Some thoughts on writingdanluu.com
- Things unlearnedscattered-thoughts.net
- Choose Boring Technologyboringtechnology.club
- Teach Yourself Programming in Ten Yearsnorvig.com
- Repeat yourself, do more than one thing, and... — programming is terribleprogrammingisterrible.com
- 5 Things I've Learned in 20 Years of Programming - DaedTechdaedtech.com
- GitHub - charlax/professional-programming: A collection of learning resources for curious software engineers · GitHubgithub.com
- The Technium: 101 Additional Adviceskk.org