Skip to content
MASTERY

THE MAJORITY OF MY EDUCATION
HAPPENED AFTER HOURS.

School gave me a foundation. Work gave me responsibility. Professional training accelerated both. But most of the learning that shaped me happened somewhere quieter—after hours, at home, in private labs, at hackathons, at technical events, and around other builders who wanted to understand how things worked.

When most people were sleeping, I was still learning: programming, configuring networks, building software, connecting systems, reading documentation, testing ideas, breaking environments, fixing them, and starting again.

THE PRIVATE LAB

I BUILT REAL SYSTEMS SO I COULD BREAK THEM, FIX THEM, AND UNDERSTAND THEM.

For years, my garage and home office housed a serious technical lab—servers, network equipment, firewalls, workstations, databases, development environments, and the hardware and software needed to reproduce real-world business networks and systems.

I built networks. Wrote software. Connected servers, applications, data, security, and wireless systems. Then I broke things on purpose, diagnosed the failure, rebuilt the environment, and pushed it further.

I was not always on a payroll. I never stopped doing the work. Most of those hours were unseen, and that was fine. The point was understanding.

BUILDING WITH OTHERS

SOME OF THE BEST CLASSROOMS HAD NO CLASSROOM.

Hackathons, technical events, and late-night sessions with friends became another kind of laboratory. We built software together, connected networks, compared approaches, challenged assumptions, and learned by making things work.

I asked questions everywhere I went. The goal was never to look knowledgeable. The goal was to leave knowing more than I knew when I arrived.

FAILURE AS DATA

NOT EVERYTHING I BUILT WORKED. THE LESSONS STILL DID.

I launched a software-development startup in Los Angeles. It failed.

That experience taught me something technical training cannot: a product can be possible and still fail because timing, positioning, market fit, distribution, capital, or execution are wrong.

I learned to study failure the same way I studied systems—without romance, without excuses, and without wasting the lesson.

THE MOUNTAINS

I STEPPED AWAY FROM CONVENTIONAL EMPLOYMENT. I DID NOT STEP AWAY FROM GROWTH.

For a period, I went deep into hiking, climbing, rock climbing, camping, and exploration while training for years toward a Mount Everest attempt. The mountains became another place to practice preparation, judgment, endurance, and humility.

Then a serious fall changed the plan and led to years of rehabilitation. The objective changed. The discipline did not.

Technology never disappeared. I kept studying for hours at a time—programming, networking, systems, emerging technology, and artificial intelligence—using the same private lab and self-directed discipline that had shaped me from the beginning.

THE JOBS CHANGED. THE LEARNING NEVER STOPPED.
BUILD. BREAK. UNDERSTAND. REBUILD.

MOST OF MY EDUCATION HAPPENED WHEN NOBODY WAS WATCHING.
THAT IS STILL HOW I LEARN TODAY.