It matters
how it’s made.

A thought becomes
a thing.

Computers have fascinated me since I first encountered them as a child in Karachi. I tinkered, explored, and kept finding more to understand. That fascination never really went away.

Software gives us an extraordinary material to work with. You can imagine something, give it structure, and make it real enough for another person to use. An invisible idea becomes part of someone’s day.

I love that. I love the intricacy of it. The moment a difficult problem begins to reveal its shape. The small decision that makes everything around it simpler.

And I care about how it’s made. The parts you see, and the parts you only notice when something changes. The thought behind the structure. The language. The boundaries. The experience of the next person who has to understand it.

For me, this is a craft.

“It works”
leaves so much unsaid.

What frustrates me is seeing software treated as a task to get through. Make the requested thing happen. Close the ticket. Move on.

The screen works. But does the behaviour make sense? Does the structure reflect the problem? Can someone change it without having to untangle everything around it? Has anyone considered what this feels like to use?

Those questions are part of building the thing.

When they’re left unanswered, the cost finds its way to someone else. The person using the product. The developer making the next change. The team trying to understand why something apparently simple has become so difficult.

I don’t expect every decision to be perfect. Constraints are real. A thoughtful shortcut can be exactly the right choice. What matters is the judgement behind it: understanding what we’re choosing, what it will affect, and why it is worth doing.

I want to work with that kind of care.

Stay with it.
Until you understand.

My interest in philosophy and understanding people comes from a similar place. I want to get beneath the explanation we reach for first. To see what is actually producing the difficulty.

In software, it’s tempting to keep adding answers. Another condition. Another abstraction. Another layer to make the last one manageable.

Sometimes the more useful thing is to stop and look again. What is this really trying to do? Which assumption have we carried too far? What would become simpler if we understood the problem more clearly?

That takes patience. It takes taste to recognise what belongs, and judgement to know which details matter here. It takes the willingness to change your mind about something you’ve already built.

This is the work I’m drawn to. Understanding something deeply enough that its complexity can take a simple, coherent form.

You can feel the result. Things belong where you expect them. A change fits naturally. The product seems obvious, even though arriving there was anything but.

More intelligence.
A place for care.

Since 2012, I’ve wanted to build intelligent software that could take an intention and help carry it through. Now the technology is catching up with that ambition.

AI makes it possible to create at an extraordinary pace. The decisions still matter. What are we making? What should it feel like? How should the pieces relate? What are we willing to trade away?

My attention keeps returning to the conditions around the intelligence. The context it can see. The way the work is shaped. How naturally a person can express judgement, question a choice, or refine an idea.

That is why I’m building Expertism.

A place where humans and agents can build together. Where the understanding behind a decision stays with the work. Where human taste and machine capability can meet around a shared intention.

We each bring strengths, and we each have limits. Good collaboration gives us room to help each other. It makes the difficult work clearer, and leaves more of our attention for the thing we want to make.

Software deserves that care. Building it should give us room to offer it.