Three Lessons as a Developer

Three Lessons in Three Years

JT Earl
5 min readJun 5, 2020

To write this post means that I’ve now spent three years in software development. Time flies and acknowledging that is scary. It feels like the other day when I walked into my first computer science class when it has now been ten years. Each year I’ve told myself I should write one of these “what I’ve learned articles”. Well this is the year, year three. My goal with this series is to revisit this post each year. I plan to add one more lesson I’ve learned with each year. Along with adding a lesson, I will edit any of the existing lessons based on what I’ve learned the past year.

Photo by Wes Hicks on Unsplash

My hope is aspiring devs will use these lessons to build better careers for themselves . Some veterans of the field may even get an inside look at what junior developers might be feeling, although these lessons wont be the same for every developer. Hell, some developers might think the exact opposite from me and that’s okay. Take what you find useful and leave the rest. Here are my three lessons learned three years into my software career.

Lesson 1: I Know What I Don’t Know

This lesson isn’t impostor syndrome, in fact it’s the opposite. I’ve realized that I know almost nothing, but so does everyone else. From that realization comes a sense of calm and confidence. I don’t…

--

--

JT Earl

Programmer Since 17. Currently working in front-end and mid-tier programming for a finance company. Check out my Tech blog @ documentobject.com