Micro-wins in configuration that compound

Small stack habits—DNS, TLS, backups, naming—that look trivial until they save a week.

Big architecture diagrams get likes; micro-wins keep you sleeping. These are the configuration choices that look boring in a blog post and magical at 11pm when something misbehaves.

A starter set

• Canonical hostnames: pick www or apex and redirect the other—search engines and humans both like clarity.
• Explicit internal DNS: LAN clients should resolve internal names to the right hop, usually your proxy.
• One Git remote of record: ambiguity about “where main lives” is interest on a loan you will pay in incidents.
• Restore drills: backups you have not tested are wishes.

Mozilla’s foundational HTTP documentation on MDN is still the best quick reference when you are reasoning about redirects, caching, and headers at the edge.

Calm stacks are mostly good habits, written down.

How I help

I like turning “we know what we should do” into small, merged changes with clear rollback. If that sounds useful, you know where to find me.