How to Design a Great System When the (Functional) Path Isn’t Defined Yet
summary
Practical guidance for building a robust software system when requirements and stakeholders keep changing. Covers techniques and mindset to minimize risk and maximize team impact, drawing on experience with Node.js, Python, React, disruptive architectures and agile methodologies applied across retail, healthcare, banking and other domains.
AI-written summary · about
chapters (8)
- 0:00Presentation
- 2:00System Purpose
- 4:53Minimum Essential Requirements
- 11:00Communication Strategy
- 12:25User-Centered Vision
- 16:50Fundamental Principles for Flexibility
- 19:00Event Sourcing Pattern
- 21:45Final Considerations
related talks
41mThe lost art of software design
52mFrom Code to Complexity: Shifting to Systems Thinking in Software Development
47mHow To Build Future Proofed Applications
36mFrom Software to Systems: Modern Agility
27mDesigning Even Larger (JavaScript) Applications
52mThe Lost Art of Software Design
57mSoftware Architecture: The Hard Parts
44mSoftware Architecture in a Scenario of Uncertainty