Del metal desnudo a la IA agente

Una carrera de 100 días, una tormenta invernal y la era del orquestador

If you look at my enterprise telemetry dashboard today, you will see a milestone that cost me a lot of sleep, an exhausting cross-state journey, and pushed the absolute limits of my endurance: 100 consecutive days of architecture, deployment, and code.

From January 29 to May 8, I logged thousands of contributions. The streak never broke. Not while packing my servers, not during the long-hour drives to relocate my life, and definitely not during the late nights staring at a terminal — rebuilding infrastructure from bare metal to agentic AI workflows.

I have been so immersed in this ecosystem that I am fairly certain my two dogs, who have sat beside me through endless architectural monologues and thousands of hours of video training, now understand complete sentences in English and complex business logic. If I could, I would list them as 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 guarantee my architecture could scale.

The Proving Ground: Aura hOS™ and the CMS Mandate

For the past several months, my primary focus outside my daily operations has been developing Aura hOS™ under the Humanos Foundation. I set out to build an application at the highest possible standard, with the vision of optimizing modern healthcare infrastructure and making it frictionless.

There were moments when I thought I was taking on too much — trying to digitally eradicate the archaic medical clipboard. But just as the architecture was taking shape, I learned about the Federal CMS Mandate to "Kill the Clipboard." Seeing that the technology I was developing aligned perfectly with a massive federal compliance shift gave me exactly the fuel I needed to push harder. It validated that the infrastructure was not just a passion project — it was a solution to an imminent industry bottleneck.

But here is the hard reality of building highly scalable AI-driven infrastructure from scratch: it is an absolute trial by fire. Server costs, raw computing power, and enterprise-grade deployments do not configure themselves. You must 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 definitive proving ground for my capabilities as a systems solutions architect.

Setting Boundaries: The Cognitive Load of an Orchestrator

Achieving this level of deep, sustained focus comes with personal evolution. When you shed an old professional identity to go all-in on advanced systems architecture, setting boundaries becomes a necessity.

It can be difficult for people who have known you for years to understand the shift. I had to draw hard lines and softly decline requests to return to my old IT roots to reset passwords or troubleshoot local hardware. It is not arrogance — it is simply managing cognitive load.

When your brain is actively mapping secure SSH orchestration, pinging enterprise clusters, and designing agentic AI loops, the context-switch to troubleshoot a paper jam is a massive drain of the highly specialized energy needed to build complex systems. To operate at an elite level, you must fiercely protect your focus.

We are entering 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 real enterprise environments requires deep, uninterrupted dedication.

Proof of Work > Resume Engineering

The tech job market right now is drowning in noise. Anyone can generate a generic AI-written resume stuffed with the right buzzwords.

But you cannot rapidly develop the standing to build a live enterprise telemetry dashboard after driving all day.

Real personal brand in the AI era is not about looking perfect on paper — it is about verifiable proof of work. My focus right now goes far beyond simply "pushing code." It is about understanding the underlying logic of where technology is taking us and demonstrating that I have the practical architectural capacity to build resilient systems at scale.

The Next Chapter: Landing in Denver

I could have stayed where I was, playing the exciting numbers game of hunting a remote role in a sea of applicants. Instead, I packed my life, my bare-metal servers, and my incredibly patient dogs — and moved to Denver, Colorado.

I spent the last days of my 100-day streak driving straight through a late winter storm on May 5th. Perhaps my willingness to face that weather reflects my mindset for this current era of technology: We cannot simply adapt to chaos — we must merge with it and build through it.

I did not move here just for the scenery. I moved here to physically integrate into Denver's thriving tech ecosystem and tackle enterprise-scale challenges on-site.

Building my foundation over the last 100 days was just the warm-up. Now, I am looking to bring that exact same intensity, orchestration, and enterprise-level focus to a company here. I am seeking a hybrid or on-site systems architecture position where I can serve as the technical engine for a high-performance team.

The terminal is open, SSH sessions are live, and my personal cluster is in HEALTH.

I am officially Denver local. If you are an engineering leader looking for an architect who understands the full spectrum of modern infrastructure and has undeniable proof of work to back it up — let's build.