Design and Change
Design is fundamentally fractal, where the principles of coupling and cohesion apply at all scales. Emphasizing the importance of relationships among designers, users, and stakeholders can reduce the need for extensive upfront design, allowing for more flexibility in adapting to changes. By implementing safety nets like test automation, making changes to production systems becomes more manageable, even if not entirely easy.In this clip
From this podcast
Software Engineering Radio - the podcast for professional software developers
SE Radio 615: Kent Beck on "Tidy First?"
Related Questions
How do I know if I'm overengineering and doing too much upfront design in software architecture?
How do I know if I'm overengineering and doing too much upfront design in software architecture for the episode SE Radio 615: Kent Beck on "Tidy First?" and the clip Design and Change?
How do I know if I'm overengineering and doing too much upfront design in software architecture in the episode SE Radio 616: Ori Saporta on the Role of the Software Architect and the clip Curating Design Vision?