✳flâneur — a map of the web's best reading
The Bitter Lesson for Software | Fulcrum
fulcrum.inc · 713 words · saved by 2 readers
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
Explore this link on the map →saved by
related reading
- The Eternal Sloptember | the singularity is nearergeohot.github.io
- Thoughts on slowing the fuck downmariozechner.at
- 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
- Building Effective AI Agents \ Anthropicanthropic.com
- Why Software Automation Is Hard — LessWronglesswrong.com
- What's Easy Now? What's Hard Now? - Marc's Blogbrooker.co.za
- Is Software Losing Its Head? | Andreessen Horowitza16z.com
- The Eternal Sloptember | the singularity is nearergeohot.github.io
- Building Effective AI Agents \ Anthropicanthropic.com
- Thoughts on slowing the fuck downmariozechner.at
- After Automation | Everyevery.to