Great post on an area we all need help in from time to time. In summary the lessons are:
Lesson #1: Make Useful AssumptionsLesson #2 Assume Positive IntentLesson #3: Know What You WantLesson #4: Meet People Where They AreLesson #5: Listen To Go DeepLesson #6: Choose Your Words CarefullyLesson #7: Relationships Are About PerceptionLesson #8: Project and Expect The BestLesson #9: Keep Your Wits About YouLesson #10: Create Change In Stages
Some new anti-patterns (Arrowhead, Heisenbugs) and some familiar ones (Monster Objects & Utils Class).
Good article debunking familiar reasons for not trying these best-in-class practices. The conclusion is worth repeating:
If you want to increase the productivity of your team, then do these three things:
- write a microtest that fails before you change any code;
- adopt a “no-pair no-keep” agreement;
- establish a shared understanding of internal quality.