Software Architecture: The Hard Parts
Each year, it took longer and longer to ship features to customers, and the risk of even small changes causing major problems kept growing. In 1998, developers could make changes and deploy them immediately. By 2004, pushing code changes into production required hours, even days, to be deployed.39 Teams were no longer able to solve Layer 1 problems
... See moreSteven J. Spear • Wiring the Winning Organization: Liberating Our Collective Greatness through Slowification, Simplification, and Amplification
The whole development team didn’t understand the reasons behind the technical practices. They ended up cutting corners here or gaming the system there, creating little sub-teams—or even “teams of one”—operating with a different set of standards and an incomplete view of the whole system. This made integrating code a nightmare-like experience that n
... See moreDavid Scott Bernstein • Beyond Legacy Code: Nine Practices to Extend the Life (and Value) of Your Software
I believe that we need a new generation of software architects trained to do much more than group patterns between technical components. They’ll need to know how to facilitate workshops, understand group dynamics, and contribute to the overall business strategy. Understanding the implications of technical decisions on the social fabric will help th
... See more