Skip to content

Following are my personal thoughts on tech, AI, startups and adoption of AI in Health-Care. You could read more about me here

Subscribe on Substack


Blog / Thoughts

Open Sourcing Superhuman, on Top of Gmail

I paid for Superhuman for years. If I am honest about what I actually used, it was keyboard shortcuts, the command palette, and split inbox. That is it. Thirty dollars a month for muscle memory.

Nothing against Superhuman. It taught me how fast email can feel. But after the Grammarly acquisition, the innovation slowed down. They tried to make AI the story, and meanwhile Gmail quietly shipped the same features natively: summaries, drafting, smart search. All of that lives inside Gmail now, for free, and it works better because Google owns the data.

So the calculus flipped. I did not need a replacement email client. I needed the ten features I loved, on top of the Gmail that already won.

I built Inbox Keys. It is open source, and it is on the Chrome Web Store.

The LLM Router Era Starts with Fable 5

Fable 5 is the most incredible model I have used. Not a nicer version of the last one. Another level of increment in capability.

But that is not the part that stuck with me. After days of heavy use, the thing I keep noticing is not what Fable does. It is what Fable chooses not to do itself.

It delegates. And it is good at it. That is the first real glimpse of something I have been waiting for: the LLM router era.

Agent Workflows & Loops

Episode 1 was about using agents to ship faster. Episode 2 is about the part agents still have not solved: production follow-through.

Writing code by hand is mostly automated now. Shipping to production is not, and shipping means more than getting a PR merged. It is testing the feature live, telling your team and your customers how it works, watching logs and analytics for a few days, and iterating on what you learn. Loops are what finally help with that.

A workflow is not just a clever prompt. It is the shape around the agent. What does it read? What does it ignore? When does it fork? When does it stop? When does it wake you up?

That is the difference between a useful long running agent and an expensive tab that slowly drifts away from reality.

Your Claude + Codex Setup, and Why You Shouldn't Fear the CLI

This is the first episode of Build with Agents, where I record my coding agent setup, the ergonomics and developer tools I have wired up locally to stay productive. I will keep these short and ship them often, because my setup keeps changing and I would rather share what I have now than wait for it to be perfect.

Open Sourcing Byaan, Your Company's AI Data Analyst

Today I am open sourcing Byaan, a small AI data analyst that runs close to your database and answers the long tail of "can you pull this real quick?" questions that pile up at every startup.

About ten startups are already using it day to day. I quietly shared it with founder friends over the last few months, and the same pattern kept showing up: their customer success and ops teams stopped pinging engineering for one-off data questions, and engineering got hours back every week.

I Built My Own Personal Finance App, and Now I Want More Personal Software

I do not think AI will replace every app with one giant productivity blob.

I do think AI changes something more interesting: it makes small, personal software worth building again.

There are places where I still want real software. Finance, healthcare, taxes, legal work, anything with consequences. I do not want a loose chat interface guessing its way through that. I want software with a database, a model of the domain, boring reliability, and a clear relationship with the data.

AI is useful there, but only when it sits on top of a system I trust.

That is why I built Fino, a local-first personal finance app that lets me connect my bank accounts, import the accounts Plaid misses, and then talk to my money from Claude.

Not "chat with a spreadsheet" as a demo. More like: "why did our spending feel weird this month?" and then getting an answer from my actual transactions, local rules, savings goals, recurring subscriptions, and financial memory.

Claude Writes the Code. You Run the Loop.

I have been building a lot with Claude recently. Obviously, you can ship code very quickly now. But how do you plan large features, understand UX, brainstorm different patterns, and then ship across 3 repos in an established codebase without breaking things?

The goal is to put large features in front of customers in weeks, not months. Test your assumptions and iterate on top of real feedback.