“The Accidental Yet Totally Intentional Tech Stack”

Like every developer, I started my journey thinking, “I’ll learn one language and be done.” Oh, how naive I was. Fast forward a bit, and here I am—wrangling Python, Go, and TypeScript like a circus performer who didn’t read the safety manual. But there’s a reason I picked these, and it all started with a series of highly questionable life choices.

The One That Just Makes Sense

At some point, I realized that web backend, automation, and data science weren’t just buzzwords—they were actual skills that made life easier (or at least more interesting). Enter Python, the language that promised simplicity and then tricked me into writing complex architectures. I dove into Odoo ERP, automated things I was too lazy to do manually, and even dabbled in data science—because why not let pandas and NumPy do the thinking for me?

Because I Needed Speed, Not Excuses

Then came CI/CD. I needed something that wouldn’t break every time I blinked, something fast, efficient, and not prone to existential crises (cough dynamic typing cough). That’s when I met Go—a language that compiles faster than I make bad decisions. The lack of exceptions slapped me in the face, but hey, error handling builds character, right?

The One I Didn’t Want, But Needed

I tried ignoring frontend development. I really did. But the day came when I had to build my own frontend, and JavaScript greeted me with a smug “Hello, undefined is not a function.” That’s when I caved and picked TypeScript—because if I had to do frontend, I was at least going to force it to behave. Now, I use it only when absolutely necessary, like assembling IKEA furniture: not my favorite activity, but sometimes you just need a functional table.

I didn’t choose these languages because they were trendy—I chose them because they actually help me get things done. Python makes things easy, Go makes things fast, and TypeScript makes sure I don’t rage-quit halfway through frontend work. Together, they form my perfect little chaotic yet effective stack.

And if there’s one thing I’ve learned? No matter what you choose, debugging will always find you. 😆