Planning for Long-Term Success as a Developer

Welcome back for another insight!

This week's piece will be more concise as we pivot from in-depth technical knowledge to explore a philosophical dimension of my journey.

Over the past six years in programming, I’ve made a myriad of mistakes. Each one, however, was a stepping stone on this long and challenging path.

Let's unravel the good, the bad, and the defining decisions that have sculpted my career.

The Language Dilemma

Initially, I was unsure about my coding goals. While my academic background was in finance, I was captivated by the potential of data science. The idea of crafting scripts to manage complex computations fascinated me.

Starting with R—a statistical analysis language—I soon discerned that Python, combined with pandas and NumPy, was superior. Not only did Python match R's capabilities, but it also surpassed them. The plethora of online resources and tutorials available for Python further cemented my inclination to shift.

Despite my excitement with Python, I found myself momentarily swayed by the allure of JavaScript due to some prior experience with HTML and CSS.

However, a serendipitous offer to work on a project using Python pulled me back. This project introduced me to Django and reignited my passion for Python.

The takeaway?

Your initial choice of programming language isn't critical. Whether it's Python, JavaScript, Java, or C++, the key is consistency. Avoid the trap of continuously hopping between languages, a phenomenon I'd dub the "shiny object syndrome."

Extracurricular Learning

Parallel to my coding journey, I served as a tech support engineer for a restaurant POS company. The role, though not directly linked to programming, enriched my foundation in networking and troubleshooting.

Among the early decisions that significantly influenced my career trajectory was delving into the basics of AWS. The sheer potential of mastering a niche that many weren't even aware of was palpable. In two short years, I transitioned from a novice to an AWS Certified Developer Associate.

Coding is invaluable, but comprehending cloud systems is paramount. With most companies migrating to cloud infrastructure, an in-depth understanding of how your software interacts with these systems—especially from a DevOps perspective—is crucial.

Conclusion

Every journey is unique. While I was fortunate to secure a role within a year, others might take longer. It's essential, however, to remain patient and persevere.

Start by understanding your career goals and assessing local market needs. Once you have clarity, remain unwavering in your commitment. Trust in your abilities, your research, and most importantly, in yourself.

You've got this!