TESTS BEFORE WE WRITE THE CODE (“TEST DRIVEN DEVELOPMENT”) i. TDD – Kent Beck as part of Extreme Programming 1. Ensure the tests fail – “Write a test for the next bit of functionality you want to add” ARCHITECTURE THAT ENABLES PRODUCTIVITY, TESTABILITY, AND SAFETY i. Loosely-coupled ii. Well-defined interfaces that enforce how modules connect with each other c. ARCHITECTURAL ARCHETYPES: MONOLITHS VS. MICROSERVICES

into daily work – enable flow, more automated testing h. ENABLE PAIR PROGRAMMING TO IMPROVE ALL OUR CHANGES i. Pair Programming – two engineers working together at the same workstation. Popularized increased from 70% to 85%. Since testing and debugging are often many times more costly than initial programming, this is an impressive result. Pairs typically consider more design alternatives than programmers

servers and ensure they can be reproduced in automated manner 2. Review all changes through pair programming or code review 3. Instrument the repository to detect suspicious code (API calls from certain and limits ability to take responsibility for quality of work.ii. Enable controls such as pair programming, continuous inspection, automated testing to achieve outcomes intended with controls. e. ENSURE

shared infrastructure – shared databases iv. Bounded context – compartmentalized and well-defined interfaces k. KEEP TEAM SIZES SMALL (THE “2-PIZZA TEAM” RULE) 10. Ch. 8 How to Get Great Outcomes by Integrating

show #查看网桥（虚拟交换机） bridge name bridge id STP enabled interfaces cni0 8000.9e3551d62fed no veth57d7a776 docker0 8000.0242f0503f0d