Why a Blog?
Most software we build doesn't last. It quickly becomes obsolete, fades away, and is forgotten. Software isn't meant to be permanent; it's meant to solve problems, and problems change over time. Its fleeting nature is precisely what lets us iterate rapidly, experiment freely, and push innovation forward.
When people working on software retire, as investors or founders, there's no factory floor to revisit, no warehouse filled with tangible products to point at and say, "I built that." Our work vanishes quietly, leaving hardly a trace—maybe just a repo1.
But I thought I could share what I discovered along the way—the ideas I explored, the opinions I formed, and the insights I gained from building and investing in those products. I want my kids, family and friends to have a chance to explore these experiences, to understand the journey, and perhaps find something meaningful in what I've learned.
And that's the why behind this blog.
Footnotes
-
"It's funny that software both disappears and leaves behind the most detailed documentation of every line change, every decision and who made it meticulously recorded with git commits." – @raquelbars ↩