After more than seven years in DevOps and platform engineering, I have a backlog of small lessons that never made it into a document. This blog is where they go.
The problem with "small" problems
Most of the work I have done was not about big architecture decisions. It was about the things in between: a pipeline that takes twelve minutes when it should take four, a Kubernetes error that means nothing to the developer reading it, a deploy process that everyone has quietly learned to work around.
None of these are outages. Nobody writes a postmortem for them. But they are what a developer's day actually feels like, and they decide whether a team ships confidently or nervously.
What I plan to write about
- CI/CD – what makes a pipeline something developers trust, and what quietly breaks that trust.
- Kubernetes – the parts that are hard to explain to people who just want to deploy their service.
- Platform engineering – what "self-service" really requires, and where internal platforms fall short of the slide deck.
- Developer experience in general – the friction that is too small to name and too expensive to ignore.
What to expect
Short posts, written from experience, with the failures left in. I will update posts when I learn something new, and the last-updated date will show that.
If you disagree with something, or have seen the same problem solved better, I would genuinely like to hear about it. The GitHub repository for this site accepts issues.
Originally published at https://vivek-itp.github.io/mydevexblog/blog/2026/09/05/why-this-blog-exists/.
Top comments (0)