The Bitter Lesson for Software | Fulcrum

Software is made of information flows

Software is made of information flows Software encodes information flows. An ERP system, for instance, takes procurement and locks it into a specific sequence of purchase orders, approval routing, invoice matching, and payment release. Git takes multiple people changing code and imposes a protocol of branching, diffing, reviewing, and merging. By codifying these information flows, software says how things should happen; it makes patterns repeatable and enforceable by expressing them in deterministic code. Software took over the world because we learned to express useful actions into informatio

saved by

• Julian H
• Florent Tavernier

related reading

• The Bitter Lesson for Softwarefloatingcomputer.substack.com
• The Eternal Sloptember | the singularity is nearergeohot.github.io
• Thoughts on slowing the fuck downmariozechner.at
• What's Easy Now? What's Hard Now? - Marc's Blogbrooker.co.za
• How to fully automate software engineering | Mechanize, Inc.mechanize.work
• The Eternal Sloptember | the singularity is nearergeohot.github.io
• The Case for Software Craftsmanship in the Era of Vibes — Zed's Blogzed.dev
• Would you fly on an AI-coded plane | Hackle's bloghacklewayne.com
• Why Software Automation Is Hard — LessWronglesswrong.com
• Professional Software Developers Don't Vibe, They Control: AI Agent Use for Coding in 2025arxiv.org
• Is Software Losing Its Head? | Andreessen Horowitza16z.com
• Software Engineering in the Age of AIadiamond.me