I build the operating system for modern engineering.Ibuildtheoperatingsystemformodernengineering.

Before the founder years, I learned how to make progress inside systems that were already moving.

Low-latency trading, legacy refactors, production health checks, release trains, undocumented components - not glamorous work, but the kind that teaches respect for reality.

The pattern stuck: understand the system, find the leverage point, make the next change easier for the next person.

I became a founder before I had much romance about what founders were supposed to be.

Bar & Club Stats, AskDiagnostic, and Office Dispensing Solutions were different markets with the same lesson underneath: the product is never just the software.

You build the thing, then the operating model around the thing. The culture shows up early. So do the cracks.

At Perksy, the work got bigger than what I could build myself.

The job became judgment: which systems deserved polish, which rituals created speed, which decisions needed to be owned in public.

That is where I started caring less about individual heroics and more about the conditions that make high-agency people inevitable.

Enterprise software punishes shortcuts slowly, then all at once.

At Medidata, architecture meant more than clean diagrams. It meant making tradeoffs visible across teams, timelines, and constraints that were bigger than any one codebase.

The best architecture work changed how people made decisions when I was not in the room.

AI did not make engineering easier. It made the old bottlenecks obvious.

The teams that move fastest are not the teams with the most tools. They are the teams willing to change their habits, review loops, taste, and expectations around what one engineer can own.

That is the work now: not prompt tricks, but operating model change.

I am spending this chapter with the teams, tools, and workflows that make software feel different.

The interesting part is not that AI writes code. The interesting part is what a team becomes when every engineer gets more leverage and the culture knows how to absorb it.

The workflow is the product. Culture decides what tools can do. Shipping keeps the story honest.