Solid Teamwork - a Word About Effective Cooperation
summary
Argues that SOLID maps to team behavior and gives five concrete rules: enforce at least three roles (PM developer QA) so responsibilities stay single, avoid stepping into others’ duties, and make developers interchangeable by using linters and comments and by avoiding unbattle-tested libs in production. Warns against unilateral refactoring—notify team and client—and replaces reliance on people with reliance on skill sets so projects survive absences. Practical, toolable steps and a clear metric for team composition.
AI-written summary · about
chapters (4)
- 0:00Start
- 2:29Too Many Responsibilities
- 3:31Doing Different Than Expected
- 7:06Lack of Business Attitude
related talks
30mSOLID 101: A Review for Rubyists
49mHow to Make People Work Together?
20mWorking with Others and Delivering as a Team — Bridges Seen Through Human Relationships
46mBe pragmatic, be SOLID
17mSo You Think You Can Lead a Software Team?
41mNobody Likes Working With You
49mExtreme Professionalism - Software Craftsmanship.
01h 10mAgile Cross Team Collaboration How Tos