Land of Moore / Personal Site
In 1986 I built a telescope. In 2026 I'll continue to build my dreams.
Solutions architect by the work, not by the title. I build systems that survive the job, the field, the warehouse, and my home.
Thirty years of working labor in both unionized and non-unionized environments has taught me a fundamental truth; Efficiency cannot be the only metric. As long as humans are the ones bearing the burden of the labor, it is absolutely critical to factor the human element into the engineering. When we design technology solely for corporate optimization without the consideration for the human element, we cause institutional friction. The critical question must be struck: at what point does efficiency begin to affect dignity? Sam Moore, on building for the people doing the work, using the tools
About this site
AI commoditized the syntax. It did not commoditize the context. Thirty years inside unionized and non-unionized operations taught me how systems break in the field, which is the input nobody trained a model on. No 30 year Systems Developer has the field experience I've experienced. This page records some of what I have built and what I am building next, mostly in a basement, mostly on weekends, mostly because somebody needed the thing and nobody was going to deliver.
The work
Live projects. Picked to showcase how I think, not to pad a list. With Real users.
Many carrier tools are paywalled and look like they were designed in 2004. I built the one I wished I had on my route, and other carriers started asking for updates the same week I shipped them: grievance calendar math, route forward tracking, per-carrier color themes, because real accessibility requests came in, a verifiable privacy mode I can screenshot.
Built with experience guiding design, every feature is driven by someone at a case who told me what they needed.
Route knowledge walks out the door with every retirement. Decades of which box sits behind which bush, which dog is on which porch, which nuance data point. Retainment of new people is at an all time low. I built a wiki the older carriers are not afraid to touch and the new hires can actually search.
It is also the precursor to doing anything useful with a local LLM later. A real database is a prerequisite for retrieval augmented anything.
Off-the-shelf controllers did not fit the room, and the ones that came close wanted a subscription to tell me the temperature. So I engineered the bridge myself. Redundant sensors feeding an aggregator that ignores the offline one. Cron for what happens on a schedule. Dynamic thresholds for what does not. Time series out to a dashboard so I can see when the room is lying to me.
Normalization across redundant sensors prevents a single hardware failure from cascading into bad decisions downstream. Low-tech insight. Cost almost nothing.
My in-laws are aging into technology they cannot troubleshoot. I am building a hardened appliance I can remote into, patch, and reason about from my own house. Motion, contact, environmental, and eventual glass-break sensors. Home Assistant as the orchestration layer. Tailscale tunnel so there are no open inbound ports at their place.
The final shape lives in industrial enclosures. It should look like it belongs in a utility closet, not a college dorm. The goal is their autonomy and my peace of mind. Those two metrics matter more than any efficiency gain.
In the shop
Not yet live. Honest about it.
Get in touch
Looking for a solutions architect, technical operations specialist, or AI integration consultant who can translate between the people doing the work and the people buying the software. Open to conversations in GovTech, logistics, local MSPs, and B2B enterprise architecture.