01
Make the health check boring
A useful health endpoint answers one narrow question: can this process do its immediate job? Keep readiness separate from liveness, make timeouts explicit, and never turn the probe into a second application.
A small notebook for the useful details
Software should be calm,
legible, and dependable.
Short observations about web infrastructure, protocols, and keeping small systems understandable.
Field notes
Updated occasionally
02
DNS changes need an observation window
Lowering a TTL is preparation, not an instant switch. Check authoritative answers, recursive resolvers, and the actual service path. Keep the old destination alive until the longest relevant cache has expired.
03
Static pages are operationally generous
There is value in a site that can be served from memory, has no database to repair, and needs no client framework to become readable. Fewer moving pieces leave more attention for the parts that matter.