I'm Joseph Tracy, an infrastructure engineer in Seattle with over two decades running enterprise systems end to end: scale-out NAS and SAN storage, Linux and Windows Server, virtualization, campus networking, and the identity and collaboration platforms sitting on top of all of it. Most of that time I have worked at the failure end, as the escalation point a hard problem routes to when the frontline is out of moves, which is a different education from building something once and handing it over.
Automation came out of that work rather than alongside it. Bringing hundreds of wireless access points onto a network, or large numbers of IP video cameras into one system, is the kind of job that stops being possible by hand somewhere around the third rack, and the scripts that made those deployments repeatable are the same instinct behind what I build now: the check that should have run before the job started, the snapshot that should have been taken before the config changed, the timing history that turns "it feels slow" into a measurement. Each one ships tested, documented, and with its source.
Everything here is built and tested on my own time, and I take on independent work in storage, infrastructure, automation, and diagnostics. This site is where that work gets done in public.
The shared reliability plumbing extracted from my monitoring scripts: dependency preflight, locking with guaranteed cleanup, temporary directories that cannot leak, structured logging, and retry with backoff. Not a framework. A library with exactly the functions its two consumers earned.
A small, dependency-free alert deliverer for hosts with no mail agent. Callers hand it a subject and body; it delivers to the relay via STARTTLS, and when the relay is unreachable it spools the message to disk atomically and retries on the next flush, because the moment your network is degraded is exactly the moment your alerts must not silently vanish.
The mechanical first hour of incident log review, automated: takes log files from multiple systems, normalizes their timestamps to UTC, corrects known clock drift per source, brackets a window around an anchor time, and emits one merged, time-sorted stream so a human can start reading instead of collating.
A manifest-driven environment checker that runs before real work does: required commands exist, paths are readable or writable, variables are set, disk has room, the clock is synced. Every failure reported at once, in plain language, so a broken environment is a readable report instead of a mid-run mystery.
Why alert fatigue is a design problem before it is a discipline problem, and the six decisions that keep an alerting system trusted: persistence thresholds, alert-once with asymmetric recovery, actionable payloads, a delivery path that fails independently, ruthless triage, and suppression that expires on its own.
The defensive habits that keep pasted commands intact through RDP clipboards, screen-share remote control, and web consoles: deliberate terminators, one-lining on purpose, and knowing when your shell will save you.
Weighted systems need modernization too, just translated for infrastructure that will never be disposable. Five practices that survive the crossing, what each one turns into on the other side, and the failure mode each one carries.
The 2026 observability doctrine wants everything streamed continuously. At the filesystem the physics push back, and scheduled batch collection turns out to be the correct engineering response rather than the un-modernized one.
Deployment frequency is the celebrated metric of the age, so an hour spent on one paragraph of a change plan looks like pathology. Sometimes it is. Sometimes it is the most rational activity in the building, and what separates the two cases is weight rather than maturity.