Sublime
An inspiration engine for ideas
As development proceeded, the developers changed partners once or twice a day. Each developer got to see what all the others were doing, and so knowledge of the code spread generally throughout the team.
Robert C. Martin • Agile Principles, Patterns, and Practices in C# (Robert C. Martin Series)
Quantity Goal Quality Goal Result Three new features Fewer than five bugs per feature in quality assurance testing Developers will write cleaner code.
John Doerr • Measure What Matters: How Google, Bono, and the Gates Foundation Rock the World with OKRs
The Gang of Four stated two principles of good object-oriented design that were present in all the patterns: “favor object composition over class inheritance” and “program to an interface, not an implementation.”8
Adam Barr • The Problem With Software: Why Smart Engineers Write Bad Code (The MIT Press)
OSTs Help Product Trios Adopt a Continuous Mindset
Teresa Torres • Continuous Discovery Habits: Discover Products that Create Customer Value and Business Value
At a more technical level, the drive for better testability and deployability (particularly testability) encourages engineers to design systems that separate essential and accidental complexity more effectively. This in turn keeps your options more open for changes, even quite radical changes, in other architectural properties of the system. This a
... See moreMichael Keeling • Software Architecture Metrics
The role of testing becomes to prove that deliverables support desired actor behaviours, instead of comparing software features to technical expectations. If a deliverable does not support an impact, even if it works correctly from a technical perspective, it is a failure and should be treated as a problem, enhanced or removed.
Gojko Adzic • Impact Mapping: Making a big impact with software products and projects
