Day 201: Time Blur

My first commit for Browserflow:

That’s nearly exactly 2 months ago now. Wow, it’s hard to believe that I’ve just been building this one project for so long without launching. I’m just barely starting to have other people try it (one of my best friends became the first user yesterday) despite declaring it “ready” about a month and a half ago and talking about how I want to get people onboarded.

What took so long? Well, there was the grueling refactor and for the past few weeks, I feel like I’m moving more slowly than I was before (but then again, I was working A TON before so I’m not going to put too much weight on this).

While building for two months without shipping feels like a long time, I feel fine with it. For me, the reason why I like to move quickly and get things out there is to avoid the trap of working on something forever and then not launching at all. In this case, the extra time was spent adding much needed support to reliability, performance, and usability, and I have no concerns about getting stuck in a rut where I never ship.

The weeks are all blurring together now, and it’s especially obvious when I look at the Road to Ramen posts I wrote over a month ago and am surprised because they feel like a post from a few days ago.

There are still a few major pieces to build before Browserflow will be ready for a larger user base (my plan right now is to do a very, very slow rollout so that I can make significant changes before people start relying on their flows), but it feels quite close. I’m excited for the transition from building Browserflow to building cool demos using Browserflow and sharing them with people.