Measuring Architectural Change
Kevlin discusses the importance of identifying recurring patterns in software changes, emphasizing the need for architecture that localizes these changes effectively. Klaus highlights the significance of metrics in shaping team dynamics and suggests that understanding which components change frequently can signal instability. Both stress the value of establishing rules to manage change costs while fostering a sustainable architecture.In this clip
From this podcast
Software Engineering Radio - the podcast for professional software developers
Episode 142: Sustainable Architecture with Kevlin Henney and Klaus Marquardt
Related Questions