My story begins in New York, way back, as kids would say today, “in the 1900s.”
When I was about seven, I remember watching my dad, a software developer, type what seemed like endless strings of commands across the black screen of his IBM computer. I had no idea what he was doing, but I was captivated. He could somehow speak to a computer and make it come alive.
That awakened my fascination with technology. Although I still fully intended to be the next Dan Marino.
. . .
A couple of years later, my family moved to Cuenca, Ecuador. On the first day of fifth grade, my dad walked me into a classroom at the rural La Castellana Elementary School and explained the language barrier to my teacher, Luchito. This was a Spanish-speaking school, not a bilingual or international one. My teacher spoke no English.
As it happened, I spoke no Spanish. A trivial complication to the educational process, one might argue.
It felt less like starting at a new school and more like being teleported to another planet, albeit one with the coolest eucalyptus forest playground any kid could ask for. But, I made it off the academic launchpad and a bit further.
By midyear, I was passing exams and chatting with friends. Living in Ecuador would continue influencing my growth in the decades that followed. Many of the material opportunities and comforts familiar to Americans weren’t readily available, but what Ecuador had in spades was people who showed up for one another. Connection wasn’t just a dream. It was how people lived.
At thirteen, back in New York, I finally set my sights on getting my own computer. Just one hurdle: I couldn’t afford one. Thankfully, my dad, my Uncle Norman, and Josh, a family friend and network administrator, helped me corral the necessary parts. With some instruction and a much excitement, I spent days and nights learning how everything worked: processors, memory, master/slave hard disk configurations, jumpers, graphics and sound cards, PCI and ISA slots, BIOS settings, driver installation, and more.
There were no step-by-step videos or online tech communities; Ask Jeeves was just opening shop. Building a computer back then required about 15% knowledge, 80% patience, and 5% peering through one open eye while pressing the power button.
My computer wasn’t powerful. But it was mine, and it fed my voracious appetite for the world of computing.
Fast-forward a few years to tenth grade. My high school offered me an unusual opportunity: double my workload as a junior, complete the educational requirements reserved for seniors, and graduate a year early. The arrangement would come with daily gym class, no lunch period, and heaps of additional homework.
Most irresistible offers don’t include less food, less free time, and more work. Even so, the confidence my parents and the school placed in me made the decision quite easy. By sixteen, I’d graduated from high school and begun my freshman year of college.
Outside school, I was repairing computers and even running and terminating data cabling for business networks. Looking back, allowing a teen, particularly one who looked about twelve, anywhere near production business infrastructure was quite the vote of confidence. Fortunately, there was only one notable catastrophe, and it involved my own hardware.
A full-sized steel computer tower needed to be moved out of my workshop, or what you might call it, my bedroom. While hoisting that boat anchor through the attic, I lost my grip. The nearly fifty-pound rugged case landed squarely on a single toe, sending my promising future as an international foot model right into the side of a mountain.
The computer survived. With a surgeon’s aid, so did the toe.
Misfortune aside, that early consulting work led to my first full-time tech position. At nineteen, I became the one-man IT department for a healthcare company; it even came with a blue numeric pager. The new job also placed me firmly in the IT hot seat. And that seat could get a little warm, in the same way staring at the sun causes a little eye strain.
Healthcare and other regulated sectors are built on layers and layers of interconnected systems, workflows, policies, and regulations. What appears on the surface to be a minor failure can quickly spiral into an operational shutdown, affecting patient safety.
Failure has real consequences. And as any IT veteran will tell you, hardware has a 100% failure rate. The only question is when.
Within five years, and before turning twenty-five, my responsibilities at the company had expanded to directing major technology projects and traveling across several states to guide company mergers.
Writing this still feels surreal.
At the time, I never thought about titles. I was absorbed in the work. Each challenge I solved earned greater trust. The more complex the challenge, the more determined I was to deliver. The trust people place in me has always mattered more than any title or financial incentive, and I’ve never taken it lightly.
Over the decades that followed, my responsibilities crossed cybersecurity, development, compliance, artificial intelligence, the expansion and rebuilding of technical systems, and the work of helping businesses navigate perpetual digital change. I built technical teams where none had existed. I mentored emerging technology leaders as they developed the confidence and determination to assume greater responsibility. I worked with executives spanning industries and time zones, entering situations where the technical challenge was only one part of something much larger.
People change. Technology changes. Markets shift. Business models evolve. Growth places new pressure on old processes. The pieces don’t move at the same speed, and they absolutely don’t organize themselves. My work is to understand how those pieces interact, determine what a successful outcome actually looks like, and get people there.
Perhaps unsurprisingly, my interests never stopped at technology.
One of the more improbable chapters of my life began with an abandoned self-service car wash. After driving past it for months, I became convinced that the long-neglected property could become something valuable to the community. At the beginning, faith was about all I had.
That faith wasn’t supported by any discernible aptitude for mechanical repair. To describe my handyman abilities as scarce would be a compliment. I knew very little about car-wash equipment and had never operated that kind of business. What I did know were processes, disciplined execution, customer experience, and the compounding effect of unyielding attention to detail. I could see what the property might become, even if I couldn’t yet see every step required to get it there.
Shortly before the acquisition closed, my business partner withdrew out of fear of failure. I understood the worry. I was already running an IT company, and walking away from this additional venture was unquestionably the safer choice. Moving forward alone meant stretching my attention even further and taking on considerably more risk.
I chose to continue.
The business grew fast. Customers began arriving from well outside the immediate area. Car shows appeared. Food trucks followed. Before long, a property that had been abandoned and overrun had become a lively gathering place. Less than a year after that first moment of faith, I sold the business at a profit.
So, who am I?
I’m the person people call when they need to make it happen.