If you look at my enterprise telemetry dashboard today, you’ll see a milestone that cost me a lot of sleep, a grueling cross-state drive, and pushed the absolute boundaries of my endurance: 100 consecutive days of architecting, deploying, and pushing code.
From January 29th right up to May 8th, I logged thousands of contributions. The streak never broke. Not during the packing of my servers, not during the long-hour drives to relocate my life, and definitely not during the late nights staring at a terminal, piecing together infrastructure from bare metal up to Agentic AI workflows.
I’ve been so deep in this ecosystem that I am fairly certain my two dogs—who have sat by my side through endless architectural monologues and thousands of hours of video trainings—now understand full English sentences and complex business logic. If I could, I’d list them as my co-founders.
But why push this hard? Why the relentless, 100-day grind?
Because we are living through a massive shift in technology, and I needed an uncompromising proving ground to ensure my architecture could scale.
The Proving Ground: Aura hOS™ and the CMS Mandate
Over the last few months, my primary focus outside of my day-to-day operations has been developing Aura hOS™ under the HumanOS Foundation. I set out to build an application at the highest possible level, with a vision to streamline modern healthcare infrastructure and make it friction-less.
There were moments where I thought I was taking on too much, trying to digitally eradicate the archaic medical clipboard. But right as the architecture was coming together, I learned about the Federal CMS Mandate to "Kill the Clipboard." Seeing that the technology I was building aligned perfectly with a massive federal compliance shift gave me the exact fuel I needed to push even harder. It validated that the infrastructure wasn't just a passion project—it was a solution to an impending industry bottleneck.
But here is the harsh reality of building highly scalable, AI-driven infrastructure from the ground up: it is an absolute trial by fire. Server costs, raw compute power, and enterprise-grade deployments don't configure themselves. You have to understand resource optimization, compliance, and deployment pipelines at a visceral level. Building this forced me to level up in ways a standard, comfortable corporate role never could. It became the ultimate proving ground for my capabilities as a Systems Solution Architect.
Setting Boundaries: The Cognitive Load of an Orchestrator
Achieving this level of deep, sustained focus comes with a personal evolution. When you are shedding an old professional identity to step fully into advanced systems architecture, setting boundaries is a necessity.
It can be difficult for people who have known you forever to understand the shift. I’ve had to draw hard lines, gently declining requests to step back into my old IT roots to reset passwords or troubleshoot local hardware. It isn't arrogance; it is simply about managing cognitive load.
When your brain is actively mapping out secure SSH orchestration, pinging enterprise clusters, and designing Agentic AI loops, context-switching to fix a paper jam is a massive drain on the highly specialized energy required to build complex systems. To operate at an elite level, you have to fiercely protect your focus.
We are moving into an era where we must be Orchestrators—of our complex systems, our data pipelines, and our AI agents. Maximizing these tools and applying them to live enterprise environments requires deep, unbroken dedication.
Proof of Work > Prompt Engineering
The tech job market right now is drowning in fluff. Anyone can generate a generic, AI-written resume packed with the right buzzwords.
But you cannot prompt-engineer the grit it takes to build a live enterprise telemetry dashboard after driving all day.
True self-branding in the era of AI isn't about looking perfect on paper—it’s about verifiable proof of work. My focus right now goes far beyond just "pushing code." It is about understanding the base logic of where technology is taking us and proving that I have the hands-on, architectural capability to build resilient systems at scale.
The Next Chapter: Landing in Denver
I could have stayed where I was, playing the soul-sucking numbers game of hunting for a remote role in a sea of applicants. Instead, I packed up my life, my bare-metal servers, and my incredibly patient dogs, and I moved to Denver, Colorado.
I pushed through the final days of my 100-day streak driving straight through a late-season winter storm on May 5th. Maybe my willingness to brave that weather mirrors my mindset for this current era of tech: we cannot just adapt to the chaos; we must merge with it and build through it.
I didn't move here just for the scenery. I moved here to physically embed myself in Denver’s thriving tech ecosystem and tackle enterprise-scale challenges on-site.
Building my foundation over the last 100 days was just the warmup. Now, I am looking to bring that exact same intensity, orchestration, and enterprise-grade focus to a company here. I am seeking an on-site or hybrid Systems Architecture role where I can serve as the technical engine for a high-performing team.
The terminal is open, the SSH sessions are active, and my personal cluster is returning HEALTHY.
I am officially local to Denver. If you are an engineering leader looking for an Architect who understands the full spectrum of modern infrastructure and has the undeniable proof of work to back it up—let's build.
🔵 Live Enterprise Telemetry & Deployments
🔵 Live Enterprise Telemetry & Deployments
From Bare Metal to Agentic AI