When I started Inside Open Source, my goal was simple: to share my learnings and research on commercial open source companies through my VC lens.

I have learned I am not great at keeping a steady publishing rhythm, but I have also learned that my curiosity extends well beyond commercial open source into the broader world of dev tools, infrastructure, and data. All the cool stuff that quietly powers the world.

That’s why I’m renaming my blog to stacktrace.

In programming, a stack trace shows the exact sequence of calls that led to a certain point. Developers often encounter them when debugging, but the same concept applies to understanding progress: tracing back through the steps, decisions, and conditions that led to an outcome. Sometimes that outcome is a breakthrough and sometimes it’s a failure. Both are worth studying.

That’s what I will try to do with stacktrace: going deeper than headlines, learning from real world challenges, and shining a light on the formulas behind startup success and failure in the developer world.

If you’ve been following Inside Open Source, thank you. I’m looking forward to continuing the journey with stacktrace.

The first piece will come out in a few days. Its about hiring ‘AI Engineers’ and where to look for them.