Organizations

The Godfather keeps coming up in my business conversations. Not because of the blood, but because of the scenes where people negotiate, read a room, exchange favors, protect a reputation, and discover that a decision they thought was professional was carrying an entire moral order inside it. Mario Puzo’s novel and Francis Ford Coppola’s films should be treated as related but distinct instruments rather than rivals for the same crown. Puzo gives the world breadth and backstory; Coppola gives it ritual, faces, and lines that have become almost proverbial. Together they dramatize the informal curriculum every organization runs alongside its formal one — who can ask for what, which obligations get remembered, how trust is priced, when a refusal becomes an insult. The Corleone family is not a model to imitate. It is a pressure chamber in which ordinary organizational mechanisms become impossible to look away from. …

There is a strange gap in American software. At one end sit the companies large enough to turn engineering practice into infrastructure: Amazon, Apple, Microsoft, and their peers can afford dedicated platform teams, internal tooling, architecture review boards, and years of accumulated institutional memory. At the other end sit the garage companies and small shops that don’t pretend to have a software development life cycle at all — they deploy from a laptop because the product is one person, the customer is waiting, and the alternative isn’t a more rigorous process but no product. Between those poles sit thousands of companies with enough software to need engineering discipline and not enough margin, attention, or organizational slack to make it a first-class concern. That middle is where most software actually gets written, and it is the part of the industry the industry’s own literature has the least to say about. …