Thinking
out loud.
Notes from the studio. Technical perspective, product thinking, and occasional opinions on how software should be made.
Why your MVP is failing: the wrong kind of fast
Most 'move fast' advice was written for funded startups with engineering teams. For early products, speed in the wrong direction is just a faster way to build the wrong thing. This piece argues for a different definition of speed: shipping fewer things with higher fidelity, and why that produces better feedback loops.
React Native in 2025: what we actually use it for (and what we don't)
A practical, honest breakdown of where React Native wins and where it doesn't — based on real production apps, not benchmarks. Includes our internal framework for deciding RN vs native vs web-first for new mobile projects.
Self-hosting analytics: what we learned building Reebot Analytics
A behind-the-scenes look at why we built our own session recording and analytics infrastructure instead of using a third-party tool. Covers the architectural decisions, the tradeoffs, and what we'd do differently.
The real cost of a design system for a 3-person team
Design systems are sold as a long-term investment, but for small teams the upfront cost is real and the maintenance burden is underestimated. This piece shares how we approach visual consistency at Reebot without the overhead — and when we recommend building one anyway.
What a good engineering retainer actually looks like
Most agencies either do project work or staff augmentation. The retainer model sits in between and is often misunderstood by both sides. This piece describes how we structure ongoing engineering partnerships, what works, what doesn't, and how to tell if your engagement model is healthy.
Deploying mobile apps for clients without losing your mind: how Reebot Dist was born
Managing App Store and Play Store deployments across multiple clients is a surprisingly painful, manual process. This is the story of how we built Reebot Dist to solve it — what the problem looked like before, the architecture we landed on, and the unexpected use cases that emerged.
Most of our thinking happens over email.
Join the list — infrequent, useful, no filler. We write when we have something worth saying.
Subscribe