git commit -m 'New portfolio live' - CLI-themed DevOps portfolio
MOJAHID UL HAQUE
DevOps Engineer
$ git commit -m "New portfolio live."
I wanted a portfolio that actually reflects my day-to-day work, so I built a CLI-themed portfolio to showcase my DevOps projects.
It was built using Replit AI, the fastest way I've found to turn a rough idea into a live website, with a bit of vibe coding along the way.
Originally posted on LinkedIn
View original postRelated Posts
DevOps is a Piece of Cake? Think Again!
DevOps is a Piece of Cake? Think Again! Hold my coffee... Ah, DevOps. The magical land where code deploys itself, pipelines never fail, and production is always stable. Right? WRONG. Let's be real about what DevOps actually involves.
Director's Award - Behind the Scenes Hero
Honored to receive the Director's Award - Behind the Scenes Hero. In DevOps, you don't usually get noticed for things not breaking. You build systems that recover before anyone even knows there was a problem. You patch, tune, automate, and quietly carry the load so everything else can move fast and stay stable. Big thanks to Prince Joal and Tarun Gupta. Not just managers, but the kind of leaders who've had our backs through fire drills, long nights, and invisible wins. The kind of support you don't have to ask for — it's just there. Always. One line from my boss Prince Joal, really stayed with me: "Some contributions happen behind the spotlight, but their impact lights up the whole system. Adil's work may not always be seen, but it's the reason things don't fall apart." That one sentence says everything I try to be. If you've ever pulled a weekend deployment, stayed up debugging a flaky pipeline, or built tooling no one sees but everyone relies on, I see you. And I'm proud to be one of you.
What 2.5 Years of DevOps Incidents Taught Me (The Hard Way)
What 2.5 Years of DevOps Incidents Taught Me (The Hard Way): The simplest explanation is usually right… Unless you're trying to explain it to management, then good luck. Logs lie less than dashboards. Dashboards smile while everything burns in the background. Logs are the friend who bluntly tells you your code sucks. Your backup strategy only works when you don't need it. Real test? When everything crashes, and all you have left is a prayer and that old backup. "Quick fix" = 4 hours of pain + 2 sleepless nights + one existential crisis. And yes, we still called it a "hotfix" in the changelog. Documentation written at 3AM is brutally honest. None of that corporate fluff — just raw, chaotic truth like: "I don't know why this works. Don't touch it." Success teaches nothing. Failure gives you character... and gray hair. Embrace the postmortems. They're just therapy sessions with charts. DevOps isn't a job title. It's a mindset — and a chaotic symphony of creativity, duct tape, and caffeine. You don't do DevOps. You live it. (And sometimes cry in a cloud console.)