The Eric Normand Podcast All about the volatility lens
Sep 11, 2023
Introducing the volatility lens in software change, addressing its unpredictability and fear. Exploring the psychological aspect of coding and the need for adaptability. Emphasizing the importance of gathering stakeholder information for informed decisions. Designing code for change, discussing risks and benefits. Exploring changeability in programming and the importance of finding a balance.
AI Snips
Chapters
Transcript
Episode notes
Volatility Lens Core Questions
- The volatility lens asks what can change, how often, and in what way in software design.
- Understanding change is crucial but often misunderstood as totally unpredictable and maximal.
Avoid Premature Generalization
- Avoid adding complex mechanisms today for hypothetical future configurability.
- Such premature generalization adds unneeded complexity that often isn't utilized.
Coffee Shop Change Example
- Eric uses a coffee shop example to analyze volatility of product sizes and add-ins.
- Sizes never changed so hardcoding fits, while add-ins change daily and need database storage.