Every developer blog starts with one of these. Here's mine.
The messy beginning
I didn't start with a plan. I started with PHP — badly, chaotically, self-taught from random tutorials. I never even got to OOP before I dropped it. Looking back, that's not embarrassing. That's just how it goes when you're teaching yourself something with no roadmap and no one to ask.
From PHP I moved to Python. This time I actually committed. I worked through proper courses, built things, understood what I was doing. Python stuck.
The frontend detour
At some point I decided I needed to understand the web. So: HTML, CSS. Then Tailwind CSS came out right around that time and I jumped on it immediately — because writing utility classes felt like what CSS always should have been. Raw CSS takes forever. Tailwind made me fast.
Then JavaScript. Then TypeScript, which felt like JavaScript but with a conscience. Then React. Then Next.js — though I never went deep on it, because I kept asking myself: if I just want to ship a simple site fast, is Next.js really the right tool? Usually the answer was no.
That's when I found Vue.js and Nuxt. Nuxt had rough edges, but for straightforward websites it was exactly what I needed. I got good at it. This site runs on it.
Almost Rust
After Nuxt, I wanted something lower-level. Rust was the obvious next step — everyone I respected seemed to love it. But coming from Python and TypeScript, Rust was a wall. The borrow checker doesn't care how motivated you are. I kept running into it and bouncing off.
I didn't give up on Rust. I just admitted it wasn't the right time.
Why Go
My actual interests were always DevOps and QA automation — writing tools that make systems more observable, more reliable, easier to operate. I did some research and Go kept coming up.
It made sense: Go has genuine traction in the DevOps space (Docker, Kubernetes, Terraform — all Go). It compiles to a single static binary. It's opinionated enough that there aren't seventeen ways to do the same thing. And compared to Rust, it was learnable — a reasonable bridge between the TypeScript world I knew and the systems world I wanted to reach.
So I learned Go. And it clicked in a way that nothing had since Python.
What this blog is
Notes from the road. I'll write about Go, CLI tooling, DevOps automation, and whatever else I'm figuring out. Not tutorials from an expert — honest writing from someone who's still learning, still building, still getting things wrong.
The first real thing I'm building is an endpoint monitoring CLI in Go. It's not published yet. When it is, it'll be here.
That's enough for a first post. Welcome.