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
• Computers can be understood - Made of Bugsblog.nelhage.com
• AI is removing the middle class of software engineeringblog.florianherrengt.com
• Malleable software in the age of LLMsgeoffreylitt.com
• Software Engineering fundamentals matter more than everrhonabwy.com
• Society's Technical Debt and Software's Gutenberg Momentskventures.substack.com
• How to fully automate software engineering | Mechanize, Inc.mechanize.work
• Malleable software: Restoring user agency in a world of locked-down appsinkandswitch.com
• Software Engineering in the Age of AIadiamond.me
• Thoughts on slowing the fuck downmariozechner.at
• Jaya Gupta (@JayaGup10) on Xx.com
• Does the Bitter Lesson Have Limits?dbreunig.com