Megha Bhardwaj

Recently, I came across a Computer Networking session on YouTube by Kunal Kushwaha. He explains Computer Networking and the OSI Model in a very simple and practical way — especially for people getting started with DevOps. In the session, he breaks down concepts like: • What the OSI Model actually means • How data moves across different layers • Real-life networking examples • How systems communicate inside a network What I liked most is that the explanation is very beginner-friendly and visual, which makes complex networking concepts much easier to understand. If you’re starting your DevOps or Cloud journey and networking feels confusing, this session can really help build strong fundamentals. #BuildInPublic

Which operating system is the best choice for coding?

Dear recruiters, if you are looking for: - Go, Python, Bash, Powershell - Kubernetes, Docker, Openshift - GCP, AWS, Azure - Linux & Window system administration - Jenkins, Github Action, Azure Devops - ELK, Prometheus, Grafana, Datadog, splunk - Terraform, CDK, Bicep - Argocd, Flux, Helm - Sonarcube, trivy, and 20 other Devsecops tools That's not a Devops Engineer. That's Devops team for 5 different company.

@LessonsFromProd Exactly, people jump into tools like Kubernetes without understanding the basics. Tools don’t make you fast — clarity does. once fundamentals are strong, picking up tools becomes 10x easier But most people just skip that part.

@TechieMegha Totally agree. seen so many people paralyzed by tool choice when they should be shipping. Learn the fundamentals first, tools follow naturally. The ones who actually move fast? they know one thing deeply before adding the next. kubernetes can wait.

You don’t need 10 tools to start DevOps. You need: • Linux • Networking basics • One scripting language That’s enough to go further than 90% beginners. #BuildInPublic

Docker - builds it, Kubernetes - runs it, Terraform - provisions it. AWS & GCP - host it. This is modern cloud infrastructure.

git reset --hard always sounded dangerous to me. And honestly… it should Imagine you’re working on a dev branch. You make some changes and stage them. Then you realize — you don’t want any of it. You run: git reset --hard B What happens? ❌ Staged changes are gone ❌ Working directory changes are gone ❌ Git goes back to the last commit No undo No recovery Use this command only when you’re absolutely sure you don’t need those changes. Small Git detail, but an important one while learning.

Linux Commands

AWS Learning Roadmap 2025 ☁️ 1️⃣ Start: Learn the basics → EC2 = compute → S3 = storage → IAM = security → RDS = database 2️⃣ Build: Do hands-on projects → Host a site → Deploy an app → Use free-tier services 3️⃣ Certify: 🎓 Cloud Practitioner (CLF-C02) ⚙️ Solutions Architect (SAA-C03) 4️⃣ Deep Dive: Networking • Monitoring • Serverless • Security 5️⃣ Specialize: AI/ML • DevOps • Data • Architect 💡 Don’t just study - build while you learn. 🚀 Grab my Free AWS Certification Roadmap  ⬇️ Comment ROADMAP to get it.

Kubernetes uses YAML Helm uses YAML ArgoCD uses YAML Ansible uses YAML GitHub Actions use YAML GitLab CI uses YAML Azure DevOps uses YAML GCP Cloud Build uses YAML YAML isn’t a programming language, but in DevOps — you can’t work without it.

9 GitHub Repos for DevOps Beginners: 1. Cloud-DevOps Learning Resources github.com/ahmedtariq01/C… 2. System Design Primer github.com/donnemartin/sy… 3. DevOps Exercises github.com/bregman-arie/d… 4. Into the DevOps github.com/NotHarshhaa/in… 5. DevOps Projects github.com/NotHarshhaa/De… 6. Cloud Native Security github.com/Hacking-the-Cl… 7. MLOps Basics github.com/graviraja/MLOp… 8. DevOps Interview Guide github.com/ramanagali/Int… 9. DevOps Roadmap github.com/milanm/DevOps-… Save this. You’ll need it later 🔖

I used to get confused by `git reset --soft`. Sometimes I’d make a commit and then realize — this isn’t what I wanted to commit yet. So I run: git reset --soft HEAD~1 What happens? ✅ The commit is removed ✅ Files stay in staging ✅ Your changes are still safe Nothing is lost. I can fix it and commit again. That’s when git reset --soft started making sense

Most people don’t fail in tech because it’s hard… They fail because they quit too early. They watch tutorials. They take notes. They plan everything perfectly. But they don’t build. No projects. No consistency. No real execution. Meanwhile… Someone with average skills but taking daily action — wins. Not because they’re smarter. But because they show up every day. Start messy. Stay consistent. Build in public. That’s how real growth happens. #BuildInPublic

At first, I thought git reset just fixes small mistakes. Later I realized… it does much more than that. Imagine you’re working on a hotfix branch. You add a few files to the staging area using git add . Then you realize the commit idea is wrong. So you run: git reset ✅ Files are removed from staging ✅ Nothing is deleted — they stay in your working directory ✅ Git just gives you a chance to rethink the commit Once I understood this, `git reset` stopped feeling scary.

Sometimes you’re working on a feature. Code is half done. Things are not ready to merge yet. At the same time, you don’t want to break main. So instead of doing everything on one branch, you create a new one. This is where git branch actually helps. • git branch → see all branches • git branch feature-x → create a new branch • git checkout feature-x → switch to it • work freely without touching main. When I started using branches properly, I stopped worrying about breaking things. #BuildInPublic

Many people think Virtual Machines are just like computers on a cloud. Here’s the reality: A VM shares the host’s resources. It still needs updates. It still needs monitoring. It still needs care. A VM can make scaling easier, but it won’t fix messy architecture or careless setups. If you treat a VM like a magical box, you’ll learn the hard way that real systems need real care.

Which tool is best for beginners starting DevOps? 👇 1️⃣ Docker 2️⃣ Linux 3️⃣ Git & GitHub 4️⃣ Kubernetes

Please learn Linux before DevOps. Please learn Linux before DevOps. Please learn Linux before DevOps. Please learn Linux before DevOps. Please learn Linux before DevOps. Please learn Linux before DevOps.

If you're into tech and not using GitHub yet, start today. GitHub is more than just storing code. It’s your public portfolio. Projects show what you can build. Commits show your consistency. Repositories show your learning journey. In tech, your GitHub can speak louder than your resume. #BuildInPublic

Sometimes you push a commit… everything looks fine. Then suddenly you realize — something is broken. The problem? The commit is already pushed. Other people have already pulled it. You can’t use git reset anymore. This is where git revert actually helps. • git revert → undo a specific commit • Git creates a new commit • Nothing is deleted • History stays safe git revert fixes mistakes without breaking the workflow.

Linux concepts you should learn for DevOps 1. Accessing Linux VMs 2. Linux File System 3. Soft and Hard links 4. Files & Directory permissions(chmod) 5. ACL 6. Text processing commands(awk, sed, cut, grep, sort, uniq, wc) 7. Compressing files: tar, zip/unzip 8. Vi, nano editor 9. User account management 10. Commands for administration: top, ps, kill, df, dmesg.