DevOpsNess — Technical Blog at Scale
A self-initiated technical blog I built and run — live at devopsness.com. 422 articles across 36 archive pages covering AI, DevOps, Cloud, and Linux: weekly deep dives, implementation patterns, and reliability-focused playbooks aimed at engineering teams.
Scope: Solo build: content system, archive, topic taxonomy, RSS, newsletter, every article.
Most engineering blogs die in two trap doors: hot-takes that age in a week, or listicles nobody reads twice. DevOpsNess does the opposite — long-form, opinionated, weekly.
0
Articles published
0+
Topic clusters
0
Archive pages
Live counts from devopsness.com · weekly cadence sustained
The live homepage — featured post and topic clusters
Screenshots from the live publication. Click anywhere to open the real site.
Top topic coverage
live post counts per tagWhat it ships with
5 surfaces from the live siteRecent deep dives
See all 422- Infrastructure
Database Backups — Testing Restores, Not Just Taking Them
8 min
- DevOps
Helm Chart Anti-Patterns We've Stopped Using
7 min
- Cloud
CDN Cache Invalidation — Strategies That Don't Break in Production
7 min
- AI
Embeddings Drift Detection — When "Similar Enough" Stops Being Similar
7 min
- Linux
systemd Timers vs Cron — What We Learned Switching
7 min
- Cloud
AWS Step Functions for Workflow Orchestration
7 min
Weekly deep dives · AI, DevOps, Cloud, Linux · long-form, opinionated, anchored to real production lessons
The Challenge
Engineering blogs fall into two trap doors: hot-takes that age in a week, or 'best practices' listicles nobody re-reads. The opening was a blog that did the opposite — long-form, opinionated, weekly. Constraints: 400+ articles across 10+ topic clusters, archive UX that stays scannable past 30 pages, content system flexible enough for code, diagrams, and callouts without CMS bloat.
The Solution
Next.js + MDX — every post is a typed React component, so callouts and code blocks compose without a CMS. Paginated archive (Page 1 of 36 · 422 posts), topic clusters surfaced on the home page with live post counts, per-post TOC / breadcrumbs / related articles / reading time generated at build. Cover gradients are ~1 KB SVGs. RSS + newsletter via Resend on the same content pipeline. Dark-first, system-theme aware, tuned for 1am reading.
Client
Kiril Urbonas
“I started DevOpsNess because I kept rewriting the same Slack messages explaining how Terraform / Kubernetes / observability decisions actually go wrong in production. The blog is the long-form version of that — 422 posts in, it doubles as a portfolio of how I think about systems. The same publishing pipeline, content rigour, and dark-mode-first UX are what I bring to client engagements.”
Kiril Urbonas
Author & Engineer, DevOpsNess
devopsness.com
Key Results
Articles published & live
Topic clusters covered weekly
Publishing cadence sustained
Before → After
Articles Published
Topic Clusters
Timeline
Ongoing — live and updated weekly · 2025
Completed 2025
Scope: Solo build: content system, archive, topic taxonomy, RSS, newsletter, every article.
More case studies
Want results like these for your business?
I'll map out a clear plan, timeline, and realistic results for your project — no obligation.