Why I chose Python

Why am I learning Python?

I have had many interests over the last few years. That is, a mix of knowledge I wanted to absorb and skills I wanted to learn. Examples include data science, web development, copywriting, content creation, cybersecurity, technical writing, digital marketing, world history, robotics, systems engineering, and so on.

The process usually goes like this: I begin to learn a new skill or concept. I spend a week obsessing over it. And then another skill or concept seduces me and I move on to learn that.

This happened recently. Around Christmans, I decided to learn programming again. Since I wanted to do build something fast, I chose the most basic frontend stack (HTML/CSS/JavaScript). After spending two weeks trying to rebuild this site from scratch, I lost interest. Python was calling my name. So, I spent the next three to four weeks automating tasks with Python and reminiscing about the good old OOP ways. And now, I write this post because, once more, I want to pivot directions.

Here’s what happened…

At my day job, I spend a lot of time supporting one of my company’s development teams. I manage the database their application uses, build data models for new projects, and run tests in lower environment to ensure backend processses properly interact with the database. I enjoy this work a lot. And being involved in the SDLC for some time makes me realize that I can build cool backend applications, too. This, in fact, is what inspired me to choose a frontend stack in the first place. I figured that, after learning how to build the frontend of a website, I could learn how to build backends like the developers I work with. But, I quickly discovered I didn’t enjoy building frontends. At least not from the two weeks I spent doing it. Instead, I want to work on backend processes and applications.

This brings me to my next pivot.

Since my current understanding of backend engineering is high level, I have to learn the fundamentals and comprehend them at a more profound level. While Python has the ability to build an application’s backend, it’s usually not the preferred language—especially if you need high performance or low latency. So, I figured I should ditch Python and switch to what seemed like a “real” backend language. Such as C++, C#, Rust, Go or TypeScript.

But guess what? The language I choose doesn’t really matter.

I’m not ready to build a high performing application yet because I still don’t know what goes into building something like that. So, rather than focusing on picking the perfect language, I will instead focus on mastering the foundational backend development concepts. Topics like API Development, Security/Authentication, and Caching, amongst others, can be done in any language. Yes, some languages more efficient or optimal to perform these processes. But if I have never built anything in the past, why overcomplicate task. I’m familiar with Python and already have a strong foundation with it, so that’s where I’ll begin.

Once I understand enough of the foundations and have built some basic projects with Python, I’ll have the option to pivot.

Three things could happen. The first is that I fall in love with backend development and decide to build higher performing application. In this case, I’ll choose a better backend language and continue my journey there. The second is that I fall in love with backend development and with Python specifically. Even though Python is not optimal in most scenarios, it’s still heavily used in companies today. So, if this scenario occurs, I’ll continue with Python and evolve my skills. Or the third thing that could happen is me realizing I don’t actually enjoy backened development. Perhaps, I only like the idea of building instead of the act of building. If this happens, I’ll move on and pursue my next passion. Let’s hope the third one doesn’t occur, however.

So, to answer the question of why I chose Python, here’s the simplest way to put it:

1. I have experience working with it in the past, so I can focus on learning backend development as opposed to trying to understand a new language’s syntax and intricacies.
2. What I didn’t mention yet is that I’m not in a rush. I’m not learning all of this to become a high paying SWE within the next 3-6 months. I’m doing it because I enjoy building things from scratch and think it’ll be fun to develop applications that’ll make my own life easier. So, I can afford to spend time working with Python before moving on to a more complex language (if it’s even needed).
3. Due to my tendency to pivot from technology to technology often, I want to stick with one language for some time. And since Python is what I’m currently learning, it’s best I continue on with it.