🚀 Venturing Into DevOps as a Beginner? Here’s What I Wish I Knew First..

Starting DevOps as a beginner can feel brutal. 😭

A month ago, I barely understood what a subnet was. Now I’ve built a complete deployment pipeline: Terraform provisioning Azure infrastructure, a Dockerized Flask app running on AKS, GitHub Actions automatically redeploying it on every push, and monitoring that emails me when something breaks.

And yes, I broke things. A lot. 😂

If you’re just starting DevOps, here are 10 things I wish someone had explained to me first.

1. Cloud is still just computers
   Behind all those fancy services are computers, networks, IP addresses, ports and security rules.
   Understand that mental model and cloud becomes much less intimidating.


2. Learn networking before Kubernetes
   Don't rush into Kubernetes because it sounds cool.
   Understand VNets, subnets, IP addresses, ports, DNS and security groups/NSGs first. When your application becomes unreachable, networking is often where the answer is hiding.


3. Infrastructure as Code is a superpower
   Stop relying on clicking through cloud dashboards.
   With Terraform, your infrastructure becomes code that you can version, review, reproduce and destroy.
   And if your goal is multi-cloud, Terraform gives you a consistent mental model across Azure and AWS.


4. Terraform State matters
   Terraform doesn't magically know everything in your cloud account. Its state file keeps track of what it manages.
   Learn terraform plan before blindly running terraform apply.


5. Docker fixes “works on my machine”
   Package your application and its dependencies into a container so it behaves consistently across environments.
   That's the core idea. Don't let the terminology scare you.


6. Kubernetes keeps your containers alive
   At its simplest, Kubernetes answers:
   “What happens when my application crashes?”
   Deployments maintain your pods. Services give them stable networking. Everything else builds on that foundation.


7. CI/CD starts fresh
   A GitHub Actions runner is usually a fresh environment.
   Your pipeline needs to install dependencies, build, test and deploy instead of assuming anything from your previous run.


8. Don't hardcode secrets
   Passwords and credentials shouldn't be sitting inside your code or GitHub repository.
   Learn managed identities, service principals, secrets management and least-privilege access early.


9. Learn observability
   Once your application is distributed across containers and cloud services, “SSH in and check” isn't enough.
   You need logs, metrics and alerts that tell you when something is wrong.


10. Learn to read errors
    This might be the most important DevOps skill.
    I encountered DNS issues, Git Bash path problems, Terraform/Azure state drift, blocked ports and even accidentally pushed a 53MB file because I forgot .gitignore. 😭😂
    The solution wasn't memorizing another command.
    It was reading the error carefully and debugging one problem at a time.
    🛠️ My Beginner DevOps Capstone
    I put all of this into one practical project:
    Flask API → Docker → Terraform → Azure VNet/Subnet/NSG → ACR → AKS → GitHub Actions → Monitoring & Alerts
    I first deployed everything manually to understand what was happening, then automated the deployment with GitHub Actions.
    》》Full github repo + step-by-step README: 👉devops beginner friendly capstone...
    I'm currently working toward AWS next, with the goal of building a genuine multi-cloud foundation using Terraform, I will keep updates here for every errors and resurfacing challenges I find for the next beginners, so stay tunned.😉👍