A recent essay reminded me how the anxieties that pushed me to become a better developer are often drowning me instead.
I missed a key realization looking back at 2019 - being driven by numbers had put a lid on my curiosity.
In an early job I skipped writing tests, thinking it would make my code more flexible and maintainable. I slowly found it did the exact opposite.
In 2019 I focused on numbers for doing better in work and play. That focus caused most of my past year's regrets, and I plan to take a much different approach for 2020.
Find the approach to taking consistent notes on books and articles to accelerate your learning.
Being insecure about my career and skills likely won't change anytime soon. Finding the positives is something I can do now.
My journalism background taught me many things that still help me as a programmer. They cover workplace conversations, managing knowledge, making well-informed decisions, and the benefits of sprinting across campus in a blind panic.
This week was learning about balance - balance of work and play, and balance of explore and exploit.
My first (of hopefully many) weekly lessons learned covers brittle tests, complex components, stupid questions, and existential emotions.
Seeing so many professional writers emerge on Dev.To has helped me see, and accept, my casual blogger habits.
Asking for help is important, but so is learning how to give problems your best shot beforehand.
When getting feedback from coworkers about your code, don't let your ego stop you from doing better.
Two months after redesigning my site, a big event makes me do it all over again.
With so much to keep learning as a junior dev, I've remembered not to trust my brain to hold onto all the new info.
Part of being a junior dev is controlling the overwhelming pressure I put on myself to learn as much as possible.