The tech world is obsessed with churning out full-stack developers. Build a React app! Deploy with Next.js! Optimize your Lighthouse score! And while that’s all great, I’ve realized something: I don’t just want to make websites—I want to understand how the machine actually works.
That’s why I’m diving into DevOps.
This isn’t some career panic move. It’s a curiosity move. Learning DevOps has been like peeling back the layers of the internet and finding a world of Linux commands, Bash scripts, and infrastructure magic—things that make me feel like I’ve unlocked a secret level in the tech game. Meanwhile, my old life as a web dev mostly involved arguing with CSS and pretending I understood Webpack configurations.
But here’s the thing: For me, coding was never just about landing a job. It’s about figuring stuff out. It’s about that rush when a stubborn server finally obeys your commands, or when your automation script actually works on the first try (okay, maybe the fifth try).
So consider this my public accountability post. It is April 2025—one year from today—I will be a competent DevOps engineer. Maybe I’ll even build something useful. Or at least write a Terraform config that doesn’t give me nightmares.
I’ll leave you with wisdom from the man who inspired this whole journey:
“Talk is cheap. Show me the code."
— Linus Torvalds (the patron saint of grumpy geniuses)
See you in the cloud. ☁️