https://www.scribd.com/document/461600374/20-patterns-in-software-teams-pdf Any pattern you see frequently or disagree with?? Domain Champion Hoarding the Code Unusually High Churn Bullseye Commits Heroing Over Helping Clean As You Go In the Zone Bit Twiddling The Busy Body Scope Creep Flaky Product Ownership Expanding Refactor Just One More Thing Rubber Stamping Knowledge Silos Self-Merging PRs Long-Running PRs A High Bus Factor Sprint Retrospectives
When I was an IC, I frequently did "Clean As You Go" and often stayed late to refactor code as I saw fit. As I gained more experience, I learned to balance this with the team's priorities. I had a team member who aimed for perfect code all the time, which led to overworking and missed deadlines. I gave him feedback, suggesting that he clearly communicate his progress during daily standups and create a draft PR if a task was taking longer than expected.