Bridging the Gap Between Dev and Ops
Developing DevOps Abilities: Starting from Zero
DevOps & Cloud learner, currently in the deep end with Linux, Git, and AWS. BTech CSE student breaking things on purpose (and learning how to fix them). Exploring real infrastructure, automation, and the tools that keep modern systems running.
What This Blog Is About
This isn’t a “how to learn DevOps” guide. It’s not a roadmap for others to follow.
It’s not a tutorial blog.
It’s not polished.
It’s a log of what I’m learning — hands-on, command-by-command, mistake-by-mistake.
This is my notebook, but public. That means you’ll see the rough edges:
wrong turns, broken configs, fixes that finally work, and notes for my future self.
If you’re figuring out DevOps too, you might relate.
If you’re ahead of me, maybe this reminds you how far you've come.
Either way — this blog is where I show up and build.
Why I’m Doing This
I’ve been around tech long enough to know when I’m just copy-pasting my way through something. I’ve written code, pushed to GitHub, deployed a few things — but when stuff breaks, I often don’t know why. That gap is exactly what I want to close.
This journey is about understanding what’s happening under the hood — not just running commands, but knowing why they work, when they fail, and how to fix things without guesswork.
What is DevOps?
DevOps isn’t a job title. It’s not some magical CI/CD pipeline either.
It’s a way of working — where development and operations stop throwing things over the wall and start building, shipping, and fixing together.
The goal?
Faster delivery. Fewer surprises. Tighter feedback loops. More ownership, less blame.
You write code, you test it, you ship it, you monitor it — and when it breaks, you fix it. DevOps makes that possible with automation, collaboration, and visibility baked in.
Why Cloud + DevOps?
DevOps isn’t just a stack of tools.
It’s a shift in how teams think, build, test, deploy, monitor, and fix things.
It sits at the intersection of development, operations, automation, and cloud infrastructure.
And that’s exactly where I want to be as an engineer — someone who owns the entire lifecycle.
I’m not doing this because it’s trendy.
I’m doing it because I want to be someone who can:
Build scalable, production-ready systems
Automate repetitive chaos
Understand infrastructure inside out
Own production — not avoid it
But here’s the truth:
Code alone isn’t enough.
You can’t build modern systems without understanding where that code runs — the cloud.
Whether it’s AWS, GCP, or Azure, the fundamentals don’t change:
How you spin up servers
Manage secrets
Route traffic
Scale up
Recover from failure
Cloud is the new normal. If you can’t operate there, you’re replaceable.
And DevOps?
It’s how you bring order to that complexity.
Without DevOps, cloud becomes spaghetti infrastructure, manual chaos, and 3AM on-call nightmares.
Cloud + DevOps isn’t just a tech stack — it’s survival.
The Methodology: SDLC + The 12-Factor App
SDLC — But Evolved
Old-school Software Development Life Cycle (SDLC) had clear phases:
Plan → Build → Test → Release → Maintain
But each phase lived in its own silo. Slow. Rigid. Lots of “It works on my machine.”
DevOps flips that into a continuous loop:
Plan → Code → Build → Test → Release → Deploy → Operate → Monitor
And then back again. Fast. Automated. Feedback-driven.
No more waterfall. Everything is connected. Everyone is responsible.
The 12-Factor App — Build for the Real World
If DevOps is the engine, the 12-Factor App is the blueprint.
The 12-Factor App is how you build apps that survive production. It’s not a checklist — it’s hard-learned rules:
One repo per codebase
Dependencies must be declared
Config lives in env vars
Logs are streams
DBs are treated as disposable resources
What I’ll Be Covering
This isn’t a fixed roadmap — I’ll keep updating as I go. But here’s the core tech I’m focusing on (but not limited to):
Foundations
The core building blocks — without these, everything else falls apart.
Linux – Mastering the terminal, permissions, scripting, services, and crons
Git – Branching, rebasing, conflict resolution, recovery, and clean history
AWS – IAM, EC2, S3, networking — understanding cloud building blocks
Ops + Automation
Where Dev meets Ops — packaging, shipping, scaling, and maintaining systems.
Docker – Containerization, images, Dockerfiles, and local dev environments
Kubernetes – Orchestration, pods, services, Helm charts, real-world clusters
CI/CD (Jenkins) – Automating builds, tests, deployments with GitHub integration
Terraform – Infrastructure as Code, AWS provisioning, modular infra
Ansible – Config management, remote automation, provisioning
Monitoring – Prometheus, Grafana, basic observability and alerting
Resources I'm Using
These are the platforms and mentors I’m learning from as I build through this journey. Not everything at once — I’ll be coming back to these as I go deeper.
Platforms
KodeKloud — Hands-on labs for Linux, Docker, K8s, Jenkins, Terraform, and more
ACloudGuru (via Pluralsight) — For structured AWS training and certification prep
Linux Upskill Challenge — A free, daily hands-on guide to Linux server basics
YouTube Mentors (Free, high-signal content worth following)
TrainWithShubham – Shubham Londhe — Practical DevOps projects, 90-day challenge inspiration
Savinder Puri — Deep dives into DevOps tools, real-world scenarios
Tech Tutorials with Piyush — Linux and AWS essentials explained clearly
Paras Thakur — Clear, beginner-friendly explanations of DevOps and cloud concepts with practical demos