Accidentally Complex Development
summary
This talk examines how introducing accidental complexity—through insufficient problem exploration or using patterns/technologies by habit—harms maintainability and team productivity. It gives representative examples and explores alternatives, discussing technologies and patterns such as microservices, CQRS, resilience patterns, and message streams, showing both their abusive misuse and proper, “good” use.
AI-written summary · about
chapters (11)
- 0:00Welcome
- 3:55Role metaphors and complexity
- 11:39Greenfield and accidental complexity
- 13:24Early decisions and technical debt
- 17:14Infrastructure and project context
- 23:12Value stream mapping
- 29:30Kafka practical example
- 35:53CQRS and legacy simplification
- 41:12Events and transactionality
- 45:02Handling real requirements
- 46:51Microservices and business abstraction
related talks
58mDon't Walk Away From Complexity, Run
56mKicking the Complexity Habit
08mLightning Talk: Breaking the Mold: Unveiling Anti-Architectural Patterns in...
44mDependencies; Devil or Darling?
52mFrom Code to Complexity: Shifting to Systems Thinking in Software Development
39mDevelopers kryptonite
41mThe challenge of building maintainable, robust applications
43mQuit Simplifying!