🛠️ Transitioning into DevOps after 2.9 years in QA & Support. I’ve spent the last 3+ months not just learning, but building and debugging real-world infrastructure. Here’s what I’ve done, where I’m headed, and why you should follow along 👇. #DevOps #100DaysOfDevOps #OpenToWork.

🐳Docker Post 4/n: Multi-Stage Builds 🎯. Cut my Node.js image from 1.2GB to 180MB with this approach:. 1️⃣ Build Stage → all tools + deps.2️⃣ Runtime Stage → only final app. 💡Smaller image = faster deploys + lower costs. #Docker #DevOps #Optimization #100DaysOfDevOps.

Generate videos in just a few seconds. Try Grok Imagine, free for a limited time.

Day 3: 3/3 . 💡Integration Wins:.-Day 2 skill cards now appear on Home page.-Navigation reused across all pages.-Direct URL access, browser back/forward all work flawlessly. 🔮Tomorrow: Mobile nav (hamburger menu), improved UI.#DevOps #NextJS #React #Portfolio #buildinpublic

Day 3: 2/3. 🧠 Key Learnings:. - app/<folder>/page.tsx = automatic route. - Use <Link> for fast, client-side navigation (no reload). - usePathname() + aria-current="page" = accessible active nav state

Day 3: 1/3. ✅ Created routes: /, /about, /projects, /contact.✅ Built <Navigation /> component with active link detection.✅ Implemented clean, responsive hero section on Home. #buildinpublic #React

🧵DevOps Portfolio Project – Day 3/28. Today I moved from a single-page app to a professional 4-page portfolio with Next.js 🚀.Routing, navigation, and more. 🎯Goal: Master file-based routing in Next.js and build a reusable navigation system. #DevOps #NextJS #buildinpublic.

Day 2: 3/4 . 📸 Added first Hero component:.- Minimal content.- Responsive layout from start.- Clean, semantic HTML. 🔐Still keeping repo security tight – no .env files, .gitignore updated. 🔮 Tomorrow:.- Build navigation bar.- Add interactive elements. #DevOps #buildinpublic

Day 2: 2/4. 🧠 Key Learning – Component Thinking:. - Break UI into reusable blocks.- One component = One responsibility.- Style with utility-first classes (Tailwind). 🔄 Iterated small changes & saw them live instantly – priceless feedback loop. #buildinpublic #react #DevOps

🧵 DevOps Portfolio Project – Day 2/28. 🎯 Goal: Build a strong React foundation before diving into complex UI. ✅ Installed & configured:. - Next.js 14 + TypeScript.- Tailwind CSS.- ESLint & Prettier for clean code. #DevOps #NextJS #buildinpublic #Portfolio #100DaysOfCode

💡 Bad module choice kills idempotency: .❌ shell: echo "hello" >> file.txt .✅ lineinfile: line="hello" dest=file.txt . 🧠 Aha moment: Ansible modules are designed for idempotency!.& Idempotency = predictable, repeatable automation. #Ansible #Idempotency #DevOps #Automation.

🐦 Ansible Post 3/n: Idempotency — The "changed=0" Mystery. "Why does my playbook sometimes show changed=0?". That’s Idempotency at work-🔍 Same result every run:. 1st run → File created✅.2nd run → File exists, no change✅.100th run → Still same result ✅. #Ansible #DevOps.

-Bucket Policy = Who can enter. ✅My S3 Rules:.- Enable versioning.- Block public access by default.- Tag everything.- Use lifecycle rules to auto-clean. 💡Treat your bucket like luggage with tags & a lock. Full S3 setup in GitHub.#AWS #S3 #CloudStorage #DevOps #100DaysOfDevOps

🐦AWS Post 3/n – S3 Buckets & The Lost Luggage Story. Ever lost your bag 🎒at the airport?- That’s #AWS #S3 without naming & organizing right (in #DevOps ). - S3 Buckets = Storage rooms (globally unique names).- Objects = Your items.- Versioning = Backup copy of each change.

Ok! GPT-5 thing looks good. Just watched the demo and this thing:. - Loved the conversation thing. - The 3D models/presentation and the game 👍.- Solid overall. Probably makes better coffee ☕️ than me too. Your views? Best feature? Where AI is heading. #GPT5 #OpenAI #Grok

Had a fever today, couldn't code. Then YouTube notification: "GPT-5 IS HERE".-Ahh, Such a Drag!😒. Yesterday to my brother, I was like: "Bro you NEED to learn coding".Today: "Just do something else" 😭.#GPT5 #OpenAI #ChatGPT #Grok #vibecode . What should developers focus on now?.

🎯Decision Matrix:. Small team + GitHub repos → Actions.Enterprise + complex workflows → Jenkins. My suggestion? → Try both |💡Choose based on your project, not the hype. Most successful teams: Master one tool deeply > jump between tools. #CICD #DevOps #Automation.

🔄CI/CD Post 3/n: Jenkins vs GitHub Actions Battle⚔️. 🔵Jenkins.✅Max flexibility.✅Plugin ecosystem.❌Old UI, manual setup. 🔵GitHub Actions.✅Easiest for GitHub repos.✅Clean YAML, zero setup.❌Vendor lock-in, less customizable. Which One? 👇.#Jenkins #GitHubActions #CICD.

Terraform = Architect.AWS Provider = Construction crew. 💡 No provider = No infra!. 🔗 Full example + breakdown: in GitHub:.Analogy and diagram coming soon in Linkedin:. #Terraform #DevOps #IaC #AWS #Cloud #100DaysOfDevOps.

🧱 Terraform Post 3/n: Providers = Contractors 🧱. Terraform itself doesn’t create anything. It tells providers like AWS, Azure, GCP what to build. Think of providers as contractors for each cloud. example:. provider "aws" {. region = "ap-south-1".}. #Terraform #DevOps #AWS.

Day 1: 4/4. 🔮 Tomorrow:. - Start React (Next.js + Tailwind).- Build first component. Follow for daily insights and more hands on projects⬇️. #DevOps #Git #Portfolio #NextJS #buildinpublic #remotejobs.

Day 1: 3/ 4. 🔐 Security matters:.- Branch protection rules.- PRs with review required.- Secret scanning & dependency alerts. Already in place from Day 1 💪.(Previous mistakes and industry experience does help). 📸 Screenshot of my folder structure, git graph, and learning log: