Software Inventory
Imagine, for a moment, that you came upon a bread factory for the first time. At first it just looks like a jumble of incomprehensible machinery with a few people buzzing around. As your eyes adjust you start to see little piles of things that you do understand.
Context & Ripple Effects
Five years after Rough Type declared the week that Big Software shattered, Joel Spolsky's bread-factory essay gives the fragmented landscape a working vocabulary: shipped software is inventory — it piles up, depreciates, and has to be maintained whether or not anyone buys more of it. The argument lands mid-shift, two years after the iPad-and-Cloud-2 framing had already moved applications from boxes on shelves to services running elsewhere.
The pickup pattern matters: eight syndicated mentions across developer-heavy accounts (@destraynor, @ckindel, @carnage4life among them) within a day suggest the inventory metaphor hit a nerve with practitioners who live with the maintenance bill, not just with analysts pricing the license.
First-order effects
- Development teams at product companies get a budgeting argument for maintenance headcount: if features are inventory, keeping last year's code sellable competes directly with building next year's.
- Buyers evaluating perpetual licenses versus subscriptions gain a decision heuristic — a perpetual license is stock they now own and must warehouse, which strengthens the case for vendor-maintained service delivery.
Second-order effects
- Enterprise vendors still selling boxed, perpetual-license software face pressure to convert their catalogs into serviced offerings once customers start booking legacy code as a carrying cost rather than an asset.
- Tooling vendors — bug trackers, build systems, the category Spolsky's own Fog Creek sells into — see demand rise as maintenance shifts from invisible overhead to a first-class line item.
Third-order effects
- If the inventory framing becomes the standard mental model, the industry structurally favors recurring-revenue service firms over shrink-wrapped product companies — the same consolidation the Cloud 2 trajectory pointed toward, now with an accounting rationale underneath it.
- Hardware lifecycles follow the same logic: efforts like Neverware's push to keep old machines useful only work if someone treats the software stack on them as perishable stock needing active management, not a finished good.
The trend: Software is being re-understood less as a finished product than as perishable inventory, tilting the industry toward recurring-revenue services and permanent maintenance economics.