Figure 8-1: Handoffs between engineering roles
To design for change, make the components of your system
-
Self-contained
-
Independent
-
Well-documented
-
Standardized
-
Portable
Going beyond the Unit Test
Unit Tests: It’s Alive!
Integration Tests: Do All the Pieces Work Together?
Regression Tests: After Changes, Does the Code Behave the Same?
Visual Tests: Does Everything Look the Same?
Performance Testing
-
Failing fast (it’s not what you might think)
-
Prioritizing important work over false urgency
-
Increasing velocity through improved performance
Figure 12-2: Three boundaries of engineering work
Figure 13-1: Build-Measure-Learn
Figure 13-2: Receive-Analyze-Communicate-Change
Figure 13-3: Customer feedback pipeline
Figure 13-4: A dogfooding feedback pipeline
Figure 16-1: The thoughts of a fixed mindset
Figure 16-2: The thoughts of a growth mindset
Figure 18-1: Monolithic versus microservice architecture
Figure 18-3: The phases that focus on post-incident reviews
