How complex software impacts your cognitive abilities
summary
Argues that cognitive overload from sprawling code causes burnout and proposes a pragmatic architecture: a boring core of immutable aggregates, explicit event-sourced commands/events, and an aggregate-per-actor runtime so handlers, sagas and services are small, testable units. Demonstrates that domain-driven ubiquitous language plus message-passing makes tests mirror runtime, shrinks front-end/API plumbing, and preserves scalability. Claims this reduces bugs, speeds iteration, and materially improves developer resilience—presenting concrete patterns and an implemented architecture that reportedly works in production.
AI-written summary · about
chapters (13)
- 0:00Start
- 4:01To deal with cognitive demands
- 6:43Cognitive Abilities
- 9:55Resilience
- 13:35Software Complexity
- 16:29Domain Driven Design (DDD)
- 18:46Impact on development process
- 25:52Layering complexity
- 26:54Domain components
- 31:04Reducing operations to intent
- 32:01Command evaluation
- 32:23Temporal Continuation
- 37:14Reducing complexity: Self similarity
related talks
53mLess look, more feel. Improving the user experience as a frontender
51mGetting the Most Out of Your Shift Left Regardless of Your Program Maturity
31mHow to do Good Without Doing Anything
25mHow to do good without doing anything
15mOperational lessons from "Atypical" brains
01h 16mA11y on the back end
45mHOW TO DO GOOD WITHOUT DOING ANYTHING
44mWriting good components