On building software and the decisions behind it
I was in an interview recently and got asked about a project that had been on the books for several quarters without shipping. The question was straightforward “why do you think this project never got prioritized?”
I answered with the things I usually see. Lack of ownership, not enough capacity to deliver in the timeframe needed, or the most common, competing priorities that were more valuable.… Read more
I’ve been reflecting on a recent experiment building a multi-agent system that generates software from a product specification. What stood out was not whether it could produce code, it obviously can. What stood out was how quickly weak product definition showed up in the output. In the first version, the system produced something functional, but it was clearly built on incomplete assumptions.… Read more
As systems scale, so do dependencies. The question is not whether they exist. It is whether teams know how to work through them.
I’ve seen teams say they’re blocked by dependencies when they’re actually blocked by something else: nobody wants to move until the boundary is finished.
That is a costly mistake.… Read more