Short essays and reflections at the intersection of software, science, and systems thinking.
Enterprise teams don’t fail because of bad code — they fail because of misalignment. AI is becoming a crucial new bridge.
A reflection on software systems that bend but don't break — inspired by biology, ecosystems, and adaptive design.
Software development and scientific research share more than we admit. This note explores modeling, approximation, and the value of transient tools.
Key principles from my Software for Thinking Manifesto — tools that amplify insight, not just process workflows.
Not all leadership looks loud. This note reflects on invisible structure, social sensing, and why stability often comes from the quietest contributors.
Some insights arrive before the market is ready. This note explores how I’ve used systems thinking to spot what's coming.
Disruption doesn't mean recklessness. Here’s how I design experiments within the bounds of time, family, and financial responsibility.
My strength isn’t just code — it’s the scientific reasoning behind the code. This note shares why that matters.