The Coherent Unconventional Path
“Being right eventually matters more to me than having been right first.”
Early web building & source-code reverse engineering
My background with software began with early web building and source-code reverse engineering. Before formal software engineering frameworks entered my life, I was opening browsers, inspecting source code, and modifying web architectures to see why things broke and how they were held together. That instinct—to look beneath the finished presentation and find the underlying machinery—never went away.
Systems under real-time pressure
Later, I spent years directing high-pressure operations in high-volume hospitality. In tech circles, hospitality is sometimes misunderstood as customer service. In reality, a high-volume hospitality venue is a relentless, real-time distributed system under extreme capacity stress.
It is an environment where:
- —Handoffs cannot fail: Information must transfer cleanly between the kitchen, floor, bar, and management during peak rush without context degradation.
- —Capacity is unforgiving: When throughput surges past limits, you discover immediately where your processes are brittle.
- —Tacit expertise must become repeatable: If an operation only functions when one skilled veteran is on the floor, you don't have a system—you have a crisis waiting to happen.
- —Failure recovery is immediate: You do not get two weeks to plan a retrospective when a shift breaks; you isolate the failure and restore operational stability on the fly.
The convergence with software and AI
When I combined those operational instincts with modern software engineering and agentic AI tooling, the leverage was immediate.
Most failed product initiatives do not fail because of bad code; they fail because the team built the wrong thing, ignored edge cases, or built a system that assumes an idealized human user who never actually shows up.
Because I spent years living in the gap between stated policy and actual human behavior, I design systems that hold up when users are tired, stressed, rushed, or dealing with fragmented data.
“I do not need to be the strongest person in every discipline. I need to recognize the strongest available thinking, know where my own contribution adds leverage, and build a system in which good judgment becomes repeatable.”
This is why I collaborate effectively across technical engineers, executives, designers, and edge operators: I care about the objective integrity of the solution, not about defending personal territory.
Where I am most useful today
I am particularly valuable to early-stage teams, founders, and innovation units when: