I didn’t come from a computer science background.
I spent years in supply chain and logistics — tracking shipments, managing inventory, optimizing warehouse operations. I understood how physical goods moved around the world. Software was something other people built.
Then IBM acquired Red Hat, and my world changed overnight.
Suddenly everyone around me was talking about containers, Kubernetes, and CI/CD pipelines. I was nodding along in meetings while internally having absolutely no idea what any of it meant. My background was in shipping routes and pallets — not pods and deployments.
I had to learn it all from scratch, on the job, often by making mistakes in front of people who’d been doing it for years.
The Mistakes That Taught Me the Most
The day I typed dir on a Linux server.
When I got access to my first cloud environment, I was greeted with a black screen, a blinking cursor, and no Start menu. I typed dir — the Windows command — and got an error. That was my introduction to Linux.
The time I committed to the main branch. Early in my Cloud career, I accidentally committed directly to main and nearly triggered a production deployment. It’s a mistake almost everyone makes once. After that day, I understood why Git branching matters.
The week I spent debugging permissions. I once spent an entire week debugging a containerized application that wouldn’t run. Checked the code, checked the config, checked the image. Turns out it was a Linux file permissions issue. Nine times out of ten in Cloud environments, it’s permissions.
Every one of these moments was embarrassing at the time and invaluable in hindsight. They’re the reason I started writing.
Why Pipeline & Prompts Exists
When I was learning DevOps and Cloud, most content fell into two categories:
- Too shallow — “DevOps is about collaboration!” with no practical details
- Too deep — Written for people who already knew everything, drowning in jargon and assumptions
I wanted something in the middle. Plain English. Real examples from real work. Short enough to read on a lunch break but useful enough to actually learn something.
That’s what this blog is. One guide per week. No jargon. No fluff. Built for people who are smart but new to the field — exactly where I was a few years ago.
Real-World Stories in the Blog
I try to open every article with a story from my actual career — the wins, the failures, and the lessons. Here are a few:
- What is DevOps? — Why the “restaurant kitchen” is the best way to explain DevOps
- Linux Basics for DevOps — The day I realized every server I’d ever touch would run Linux
- Git: The Tool That Saves Your Code — The main branch incident and what I learned from it
- What Are Containers? — How a colleague’s shipping container analogy finally made Docker click for me
- CI/CD Pipelines — The first time I watched a pipeline deploy code without anyone pressing a button
- Kubernetes at Scale — From supply chain logistics to container orchestration
- Infrastructure as Code — The week my colleague spent three days rebuilding an environment from memory
- What is AI? — From selling predictive analytics a decade ago to having AI review my Terraform code
- Generative AI and Agentic AI — From answering questions to taking action
- The Big Picture - DevOps, Cloud, and AI Converge and what it means for you
I’ll keep adding to this list as I publish more articles.
What’s Next for Me
I’m still learning — that never stops in this field. Right now I’m exploring how AI tools are changing DevOps workflows, and I’ll be writing about that on the blog as I go.
If any of this sounds familiar — if you’re switching careers, teaching yourself new skills, or just trying to figure out what a Kubernetes pod actually is — you’re in the right place.