Why I build in public

So far I've shipped a product to production with real users (Sofia), landed a grant, delivered a paid mission for a DAO, and started several projects. The tempting move would be to inflate that into "expertise." I'd rather do the opposite.

The posture: exploration, not expertise

A developer profile that claims to have mastered everything rings false, and people feel it. What's true, and more interesting, is the learning speed and the ability to turn an idea into something that runs.

So here I document:

• what I'm building and why,
• what works,
• what gets stuck (and there's plenty of that),
• what I learn along the way.

What this site is not

It's not a frozen résumé. It's a logbook. The projects page shows the real state of things; the now page says what I'm on today; the activity feed proves it's moving, without me having to claim it.

What's next

More products, in the open. New bets, and honest write-ups when they work and when they don't. All of it gets told here, as it happens.