Senior DevOps & Platform Engineer | IIoT Enthusiast | Ex-Dev, New-DevEx
On a lifelong mission to automate anything that moves — and most things that don't.
When I'm not deep in the CI/CD matrix or smoothing out Kubernetes tantrums,
you'll find me sipping cay and whispering sweet nothings to my .bashrc.
If you don't have time to build it right today, you definitely won't have time to fix it when it blows up in production.
MVPs — or should I say Mostly Vulnerable Products — have become the industry's favorite excuse for cutting corners and calling it "iteration." But let's be honest: technical debt doesn't wait politely in your backlog — it accrues like bad interest and bites back at 3 AM. Your users aren't lab rats. Shipping broken things just to "see what happens" isn't agility — it's reckless roulette.
That's why I advocate for MaxVP — Maximum Viable Product — where viability means sustainability, maintainability, and a little bit of pride. Build it like someone's future depends on it — because it probably does.
AWS Solutions Architect - Professional · MCITP: Enterprise Administrator · Microsoft Certified Professional
