The software is the artifact.
The organization is the work.

My career began in large-scale software delivery, where I learned a lesson that has never left me: the quality of an engineering organization is not an accident. It is built — deliberately, patiently, and usually by someone willing to do the unglamorous work of setting standards and holding them.

Early on I was the engineer obsessing over the craft. Over time I realized the highest-leverage work wasn't writing more code — it was building the conditions under which a whole team could do its best work. That shift, from individual craft to organizational craft, is the through-line of everything since.

Across Infosys, Numerify, RedMart, Myntra, and Booking Holdings, I've worked at nearly every scale an engineering organization can have — from scrappy startups proving they deserve to exist, to global platforms where a single decision ripples across thousands of engineers and millions of customers.

eCommerce taught me to respect the physical world and the unforgiving math of peak events. Travel taught me what reliability and experimentation velocity really mean at global scale. SaaS taught me that the customer's trust is the actual product. Different surfaces, same obsession: how do you build an organization that does its best work, repeatedly?

That process is scar tissue, and the goal is to need as little of it as possible. That you cannot inspect quality in at the end — you have to build it in from the start. That culture eats every strategy that ignores it. That the best engineers are rarely the most obvious on paper, and that hiring is the highest-leverage thing a leader does.

And that almost every painful failure I've witnessed traced back to a leadership decision someone avoided making — a standard not set, an underperformer not addressed, a 'why' left unspoken. Leadership is mostly the discipline of making those decisions while they're still cheap.

We are living through the most significant shift in how software gets built since the move to the cloud. AI is not a feature you bolt on; it is a force that reorganizes how engineering works — what we automate, what we measure, what we value in the people we hire.

I've watched organizations treat AI as a toy and produce toys. I've watched others bring real engineering discipline to it and produce advantage. The difference is never the tools. It's the leadership, the operating model, and the willingness to be honest about what's working. That conviction is why I wrote The AI Native Enterprise — and it's what drives the work I do now.

Watching someone I hired or mentored go on to lead better than I did. The quiet satisfaction of a system that just works because a hundred good decisions were made upstream.

I'm in this for the people and the craft, in roughly equal measure. The software is the artifact. The organization is the work.