Moving faster
Early on I definitely cared more about writing 'elegant' code or using fashionable tools than I did about actually solving problems. Maybe not as an explicit belief, but those priorities were clear from my actions.
This post is part of a series, starting at Reflections on a decade of coding . I don't think I'm very fast in an absolute sense, but I'm much much faster than I was 5 years ago. These are the things that I think made the most impact. Care The main thing that helped is actually wanting to be faster. Early on I definitely cared more about writing 'elegant' code or using fashionable tools than I did about actually solving problems. Maybe not as an explicit belief, but those priorities were clear from my actions. I probably also wasn't aware how much faster it was possible to be. I spent my early
related reading
- A Bunch of Programming Advice I'd Give To Myself 15 Years Ago | Marcus' Blogmbuffett.com
- Speed matters: Why working quickly is more important than it seems << the jsomers.net blogjsomers.net
- Emotional managementscattered-thoughts.net
- No one can teach you to have conviction | benkuhn.netbenkuhn.net
- How I've run major projects | benkuhn.netbenkuhn.net
- Be impatient | benkuhn.netbenkuhn.net
- Things unlearnedscattered-thoughts.net
- Reflections on a decade of codingscattered-thoughts.net
- How To Do Lessalexturek.com
- Some reasons to work on productivity and velocitydanluu.com
- Reflections on 10,000 Hours of Programming | Matt Rickardmatt-rickard.com
- Shipping at Inference-Speed | Peter Steinbergersteipete.me