From embedded to SaaS
Why a real-time firmware engineer ended up building web platforms — and what carried over from the silicon.
I didn’t start with the web. I started with microcontrollers — writing real-time C and C++ for medical devices, where a missed deadline isn’t a warning in a console, it’s a failure with consequences. You learn quickly that the machine doesn’t care about your intentions, only about what you actually shipped.
That world leaves a mark. When every byte and every millisecond is accounted for, you stop treating reliability as a feature you add later. It becomes the default. You think about the worst case before the happy path, and you assume things will break — because at 3 a.m., on real hardware, they do.
What carried over
When I moved into building web and mobile products, I expected to leave that mindset behind. I didn’t. If anything, it became my edge.
- Correctness first. A SaaS platform handling other people’s orders and money is a real-time system too — just with different deadlines.
- Own the whole stack. From firmware up to nginx, I’m comfortable everywhere in between. That means fewer hand-offs and fewer places for things to get lost.
- Ship it, then trust it. Hardware taught me to measure instead of guess.
Why I’m writing here
I founded Dropdz and I architect software for a living, but I rarely write any of it down. This is where I’ll start — notes on building products end to end, the messy parts included: embedded, web, infrastructure, and the occasional lesson learned the hard way.
More soon.