Notes from the studio.
Why an independent product studio writes in public, what to expect here, and what we will not turn this corner of the site into.
We have shipped a handful of products since 2016. Most of what we learned doing it has lived in private notes, in Slack threads, in code review comments. We are starting to write more of it down in public, and this page is where those notes will land.
There are two reasons we are doing this.
The first reason is selfish. Writing forces a discipline that arguing with yourself in your head does not. When we sit down to explain why we picked Postgres over a managed BaaS, or why we killed a product after eighteen months, or why we keep one weekend a quarter for nothing but maintenance, we usually find at least one assumption we cannot defend. That is the assumption we needed to surface. The post is a side effect.
The second reason is practical. Most studio blogs we like have a similar shape. Short, dated, infrequent. They read like a captain's log, not a content marketing engine. We have learned more from a handful of those than we have from a thousand thinkpieces with optimized headlines. We would like to be that kind of useful for someone else.
Here is what to expect.
Posts will mostly cover three things. The trade-offs behind a build decision we made in one of our products. The mechanics of running a small studio that ships and operates, not just ships. And the occasional reflection on a tool, a workflow, or a habit that meaningfully changed how we work. Some posts will be 300 words. Some will be 3,000. None will pad.
Here is what to not expect.
We are not going to chase trends. We are not going to publish a take on every framework release or model launch. We are not going to write listicles, or "ultimate guides", or anything that exists because the keyword research said it would rank. If a post does not earn its place by being useful to a working builder, it does not go up.
The cadence will be irregular. We aim for one or two posts a month, sometimes more when a launch generates real material, sometimes less when the products need our full attention. The archive will grow slowly on purpose.
If you want to follow along, the RSS feed lives at /rss.xml. Otherwise, check back when you remember to. Either is fine.
Thanks for reading.