How Google Tests Software
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 point is that whenever possible, you should choose in-process tests over those that destroy product.
Andrew S. Grove • High Output Management
Questions for readers: Does IT consider itself to be a service provider, a partner to business units, or a driver of innovation? What do other leaders in the organization think? Are you measuring change lead time, release frequency, time to restore service, and change fail rate across all your products and services? Are you making them visible to a
... See moreJez Humble, Joanne Molesky, • Lean Enterprise: How High Performance Organizations Innovate at Scale
Niklaus Wirth, “A Brief History of Software Engineering,” IEEE Annals of the History of Computing 30, no. 3 (July–September 2008): 34.