DevOps Practices That Actually Ship

DevOps, for us, is disciplined reduction of delivery friction: smaller changes, fast feedback, predictable deploys, fewer 3 AM recovery drills.

We avoid cargo-cult rituals and focus on what measurably improves flow:

Flow & Throughput: Lead time, deployment frequency, change failure rate, MTTR—tracked, trended, acted upon.
Delivery Pipelines: Deterministic build → test → artifact → deploy. No snowflake steps, no hidden manual toggles.
Infrastructure as Code: Versioned, reproducible, reviewable. Terraform, Bicep, GitOps used for clarity not fashion.
Observability: Metrics, logs, traces, user-impact signals. Noise trimmed; action retained.
Security Shift-Left: Dependency hygiene, automated scanning, least privilege in pipelines; security as an engineering constraint.
Platform Engineering: Self-service paved paths so product teams ship without reinventing orchestration.
Resilience: Load, latency, failure injection, rollback rehearsals—practiced before incidents.

Expect opinionated takes on CI/CD anti-patterns, automation theater, flaky test tax, “quick wins” that age badly, and where tooling investment actually burns down operational risk.

If you want fake maturity signals, this isn’t it. If you want sustainable, boring reliability that frees time for features? You’re in the right place.

.NET CLI 10 – Microsoft Finally Realizes DevOps Exists

The .NET CLI? Reliable. Boring. You run dotnet build, dotnet test, dotnet publish, done. Real DevOps work happens in Dockerfiles, CI/CD configs, and specialized tools. The CLI does its job but was never built for actual operational workflows.

.NET 10 changes this. Four additions that sound minor but fix real problems I’ve hit in production pipelines for years: native container publishing, ephemeral tool execution, better cross-platform packaging, and machine-readable schemas. Not flashy. Not keynote material. But they’re the kind of improvements that save hours every week once you’re running them at scale.

Will they replace your current workflow? Depends on what you’re building. Let’s look at what actually changed.

Stop Typing: The .NET CLI Tab Completion You've Been Missing

One command to transform your .NET CLI workflow—tab completion so responsive you’ll wonder how you survived without it Finally, a productivity boost that’s actually worth your time

.NET 10 Testing: Microsoft Finally Fixed the Test Runner (Mostly)

.NET 10 replaces VSTest with Microsoft.Testing.Platform, bringing SDK-integrated testing with faster discovery, consistent behavior across environments, and explicit configuration contracts. But it requires .NET 10, breaks old test adapters, and demands CI pipeline discipline. Here’s what actually changes, who should migrate now, and who should wait.