By martinig
via softdevtube.com
Published: Feb 19 2013 / 09:55
What happens to the architecture of established systems in an environment where concurrent feature delivery projects make architectural ‘adjustments’ for their own ends? How can erosion of this shared architecture be managed across multiple teams? How can projects acting in their own best interests avoid over-exploiting the common architectural resource on which they all depend? Should ownership of the architecture be distributed and shared, or centralized and tightly controlled? Perhaps most importantly, can we detect when the architecture has been violated?
-
The Cloud Isn't a Beverly Hills Nose Job at a Tijuana Price
-
Teststack, Dojo 2, and More by Dylan Schiemann (Podcast)
-
Practical MVVM For Windows Phone
-
GoingNative 16: Garrett Serack - Inside NuGet for C++
-
Build your own supercomputer out of Raspberry Pi boards
-
Doom3 BFG Source Code Review: Introduction
Add your comment
