Hello, World
I’ve been writing in private for years. Notes to myself, memos to teams, would-be blog posts to reignite a blog I made early on as an engineer. Those posts always died on the vine because they were never perfect. My new strategy is to embrace imperfection.
Why now
I have a bad habit of thinking about writing and never actually doing it. At the same time, I have lots of experiences spanning my career. This is my attempt to capture those stories.
Somewhere along the way, the problems I found most interesting stopped being purely technical. They became organizational, economic, ecological. How do you build systems, be that human or digital, that hold up under stress? How do you design for resilience instead of just efficiency?
These are the questions I keep returning to, and I think they’re worth working through in the open.
What to expect
This blog will cover a few recurring themes:
- Engineering leadership - the hard parts that don’t fit neatly into a framework. Team dynamics, technical strategy, the gap between what we plan and what actually happens.
- Systems thinking - feedback loops, emergent behavior, and why most interventions make things worse before they make them better.
- Ecology and regenerative economics - what software engineers can learn from ecosystems, and why “sustainable” is a low bar.
Posts will be infrequent and unhurried. I’d rather write one thing worth reading than maintain a content calendar.
A note on tone
I’m not interested in thought leadership, hot takes, or engagement farming. If something I write is useful to you, great. If not, no hard feelings. I’m writing primarily to think more clearly. If that resonates with a few people, even better.
More soon.