The Cathedral, the Bazaar & the AI Economy

Two documentaries I watched in college helped inspire me to become an entrepreneur.

The first was Triumph of the Nerds, Robert X. Cringely’s history of the personal computer industry. It showed how hobbyists, programmers, and self-described nerds turned computers from machines owned by governments, universities, and giant corporations into products ordinary people could buy.

The second was Revolution OS, the story of Linux, free software and open source. Richard Stallman, Linus Torvalds, and Eric Raymond explained how people distributed around the world could collectively build software that competed with the largest technology companies.

Together, the films gave me a way to see technology markets. Something powerful gets built inside a company, university, or government. Eventually the cost falls, access expands, and a new group of builders arrives. Many of the biggest businesses emerge from that change.

I have spent much of my career making some version of this bet. When we started Percolate in 2011, cloud infrastructure and SaaS were still moving into the enterprise. Alephic is based on a similar belief: AI enables companies to build differentiated software that makes them titans of their industry.

The part I understand more clearly now is that open and closed systems are not opponents. The personal-computing revolution needed both, and the AI revolution will too.

The Cathedral Inside the Bazaar

Eric Raymond was a programmer and one of the early advocates for what became known as open source. In 1997, he presented The Cathedral and the Bazaar, an essay he later expanded into a book.

The book was part software case study, part management theory, and part manifesto. Raymond was trying to explain something the commercial software industry found difficult to believe: Linux was being built in public by people distributed around the world, yet it was becoming a serious operating system.

Raymond contrasted two development models. The cathedral model assumed that complex software required a small group of experts working privately against a master plan. Users received finished releases but had little visibility into how the software was built.