For a while now, I've been heads down and building Browserflow without spending much time on sharing what I'm learning. Doing that was one of the motivations behind starting this journal, and I keep falling into the trap of thinking, "Oh, I'll do a write-up once I get to a good spot in the product."

Newsflash: I'll never get to that spot, and if I want to devote time to sharing and teaching, I'll need to deliberately make time for it. I've developed a ton of useful libraries and patterns while building Browserflow, and I want to share it so that other people can learn from my hours of suffering — plus, it'd be great way to attract the developers who'd get the most out of using Browserflow.

I could see Browserflow being a way for browser extension developers to prototype their ideas rapidly without having to write a bunch of boilerplate code. I'm not quite ready to make the transition to sharing (ideally, I'd be able to both build and share, but I'm a one-thing-at-a-time kind of guy), but I want to step out of my coding hermit mode sometime soon.

<aside> 👋 You're reading Road to Ramen, where I think aloud and share everything I learn in exploring the question: Can I make a living building things I love?

by DK the Human (@dk_the_human)

</aside>