Reinventing the wheel ... as a service
summary
Software engineering repeatedly repackages old ideas as new and often breaks things by oversimplifying core assumptions. Examples: attempts to sell an XML database fail because hierarchy was already solved, YAML treats "no" as false and causes bugs, machine learning alone recommends buying three washing machines, and microservices spun out of tiny modules create network latency. Project Loom returns to virtual threads after reactive cycles, Java moves from packages to OSGi to JPMS with little adoption, and serverless often resembles a mainframe in practice.
AI-written summary · about
chapters (11)
- 0:00Start
- 4:48Unnecessary complexity
- 5:37Straightforward simplicity
- 10:22Fallacies of distributed computing The network is reliable
- 12:09Intelligent systems
- 16:23Pendulum of innovation
- 18:12Spiral of innovation
- 19:48Rebranding
- 23:17Remote calls / inter process communication
- 23:44Modularization
- 26:40Software Engineering / Architecture "innovation" patterns
related talks
22mReinventing the wheel... as a service
57mStop writing software like it's 1999!
33mFrom Enterprise Architecture to Software Design - Critical Thinking
20m3 reasons why micro-services aren't the miracle cure
39mSoftware is a meal best served with different architectural spices
57mBuilding Systems that are #neverdone
50mTactics and strategies on software development: how to reach ...
36mOverengineering: Causes, Symptoms and Treatment