About Me

My path into software engineering didn’t begin with computers. It began on the open road.

Before college, I spent years driving a tractor-trailer across the country. It was a job built on movement, but it taught me to slow down and notice things— patterns, inconsistencies, systems that worked and systems that didn’t.

I learned quickly that success depended on planning, awareness, and the ability to adapt when the real world didn’t behave the way the map said it would.

Learning Through People and Patterns

My understanding of systems didn’t come from theory alone—it came from proximity to people who lived inside the consequences of those systems every day.

Some of the most formative lessons didn’t happen in classrooms or design reviews, but in conversations that revealed why things broke under pressure.

A mechanic once showed me how to lift an axle using air suspension instead of a jack—not because it was better in theory, but because the jack wasn’t working. Rather than halt the entire process to retrieve another jack, he adapted to the constraint and kept the system moving.

A machinist walked me through a CNC setup at three in the morning, explaining how small parameter changes could ripple into hours of lost production if upstream assumptions were wrong.

One of the most revealing moments came during a discussion with a terminal manager, the regional VP, and the Southeast district manager, as they explained why a critical reporting process consistently jammed during peak operational hours.

On the surface, it looked like a software download issue. But as the conversation unfolded, it became clear that the problem wasn’t owned by any single system or team. It was the result of timing pressures, infrastructure realities, operational priorities, and assumptions made far upstream—converging in a place where failure was unavoidable.

What stood out wasn’t the problem itself—it was how clearly each leader understood a different slice of the same failure. No one had the full picture alone. That experience taught me something I still rely on today: systems don’t fail in isolation, and insight rarely lives at a single level of the organization.

Education as a Systems Lens

I completed my bachelor’s degree, then earned my master’s in Software Engineering & Project Management— an experience that strengthened my systems perspective and deepened my understanding of organizational complexity.

And now, I’m expanding that journey even further by pursuing an MBA. For me, this isn’t about credentials—it’s about gaining the business insight needed to fully understand stakeholders’ daily pressures, constraints, and decision-making environments.

The Principle That Guides Me

You can’t design the right solution if you’re solving the wrong problem.

That belief shapes how I work with stakeholders. I don’t tell people what they need. I reframe the problem so the real need becomes visible—to them, not just to me. Solutions stick when people see their own insight reflected back in them.

• Curiosity: Asking the questions others overlook.
• Constraints: Designing honestly within real limits.
• Clarity: Making complex systems understandable.
• Alignment: Keeping intent and execution in sync.

Where the Questions Led

My journey has included long nights, steep learning curves, unexpected mentors, and a constant stream of questions that refused to leave me alone.

Those questions eventually led me into deeper research about hardware-software interaction, systems design, and the assumptions buried in modern computing. That exploration became the seed of BitGrid—a conceptual architecture rooted in curiosity, clarity, and the courage to follow unconventional questions.

Gratitude and the Next Mile

But at the heart of everything I do is something simple: I’m grateful for the people who took the time to teach me things I didn’t know I needed to learn. Their generosity shaped my perspective, my work, and the engineer I’ve become.

I’m still learning every day. And I still believe the best way forward begins with asking the right questions.