Mikael Siidorow

Mikael Siidorow

@siidorow.dev

Builder & product engineer. Wrote my MSc thesis on sync engine adoption. Local-first curious. #buildinpublic

94 followers132 following27 posts

Building good UI is really hard. Chat buys time to figure out what it actually needs to be. Not the end state, but way better than rushing dashboards nobody wants to use #buildinpublic #webdev

I moved all my personal projects off Vercel to a self-hosted Hetzner server Free tiers are great for hobby projects. But the moment you need long-running processes, you're paying. A sync engine, a 24/7 data collector, Postgres. These aren't serverless workloads. #buildinpublic #selfhosting #webdev

View full thread

NixOS and Kubernetes configs were mostly vibe coded with Claude. Took a weekend. Now I modify my infra from my phone. Prompt Claude, it opens a PR, I preview, I merge. No dashboards. Vibe infrastructure. And the cost stays at 8€ no matter how much I deploy.

My server is in Finland, run by a German company. No US jurisdiction over my data. That wasn't why I moved, but it's something I've started paying more attention to. Anyone else self-hosting? Where do you draw the line between convenience and control?

I moved all my personal projects off Vercel to a self-hosted Hetzner server Free tiers are great for hobby projects. But the moment you need long-running processes, you're paying. A sync engine, a 24/7 data collector, Postgres. These aren't serverless workloads. #buildinpublic #selfhosting #webdev

On Fly.io, Render, or Railway a single always-on service runs roughly 5-7€. But a real app is never one container. My sync engine powered app needs the app, a sync server, and Postgres. Three services, 15-20€ for one project. I run all that plus other apps on Hetzner for 8€ total.

View full thread

I've been interviewing practitioners across the space: engine builders, engineers using sync engines in production, and teams that built custom

Still looking for more interviews across all three groups. If this sounds like you, DM me - or just reply with what you're building, I'd love to hear about it #buildinpublic

This has been really helpful for my MSc thesis research at Aalto University (@aalto.fi). I'm exploring sync engine architectures: when off-the-shelf sync works well and when teams end up building custom #localfirst #webdev

Our caching strategy is "hope two people don't edit the same thing at once." Low concurrency has been carrying the entire stack for years. Now more users and larger orgs are jumping in and the cracks are starting to show.

I just built a toy version of my Gmail client for mysidequest.xyz Week 3! It has working OAuth and connection to the Gmail API. Only text render at this point, but I learned a lot about parsing the email format. I even got åöä to work properly 🙌 #webdev #sidequest #buildinpublic

I used @tanstack.com Query with indexeddb to make the app fast as heck. Next steps to figure out a smart way to prefetch the emails since the Gmail listing API only has IDs by default. If it even makes sense to do this without any server storage... #svelte #typescript #webdev

No public link yet, since the Google app would require verification for that. I could grant access to specific test user emails at a later stage if people want to try it out!

I am building a side project with mysidequest.xyz! My goal for the program is to have a functioning email client that I can personally use instead of sluggish Gmail by the end of 6 weeks. Planning to post progress updates here every week! #svelte #local-first #gmail

You are up to date.