The changelog tells you what shipped. This blog tells you why, how, and what it felt like to get there. Deep dives, launch notes, and honest postmortems from the person building Seaquel.
Why start a blog now?
For the last three months, every meaningful decision I’ve made about Seaquel has lived in private docs, Discord/Bluesky DMs, half-finished drafts, or my whiteboard. That’s a shame, because most of what I think about — query planning, local-first sync, the weird edge cases of drag-and-drop in a table with 50 million rows — is the good stuff.
So I’m opening those notebooks up.
What to expect
Posts will fall into a few rough buckets:
- Engineering deep dives — How I built something, what I tried first, what broke along the way and why.
- Product notes — Why I made a particular decision, what I rejected, and what I’m still unsure about.
- Launches and recaps — When I ship something big enough to warrant more than a changelog section.
- The occasional essay — Opinions about databases, tools, and the craft of making developer software.
What this isn’t
This won’t be SEO bait. It won’t be “10 Tips to Write Better SQL.” It won’t be written by a content team because there isn’t one 😅. Every post comes from Mike, on a laptop, likely at a coffee shop or library.
If that sounds like something you’d like to read, subscribe below. I’ll email you when there’s a new post, usually once a week, sometimes less. No spam, no sales pitches.
And if you’d rather just read product updates, the changelog is where they live.
Thanks for being here. More soon.