Nobody Likes Working With You
summary
Argues that technical skill is worthless if teammates avoid collaboration and gives four rules to fix it: make people feel important (use names, public praise, a thanks channel in Slack), stop harsh criticism and use constructive feedback (replace “but” with “and”, ask questions), learn what others want by listening, and avoid or de-escalate arguments (set common ground, postpone, or give up). Recommends practical practices: praise in pull requests, pair programming during interviews, and follow-up reading before deciding.
AI-written summary · about
chapters (26)
- 0:00Introduction
- 1:35Tom
- 4:15Bad Communication
- 7:15Everyone wants to feel important
- 8:15Learn the names
- 9:10Show appreciation
- 11:10Get credit
- 12:50Dont criticize
- 13:50Why do we criticize
- 14:55Constructive feedback
- 16:40Example
- 20:35Rule number 3
- 21:35Stop thinking about us
- 23:20Listen properly
- 25:20Bill Nye
- 26:15Listen
- 27:25Its secret to win
- 28:30The problem with discussing
- 29:25Sometimes there are disagreements
- 30:10Prime Directive
- 31:40Common Ground
- 34:10The Common Ground
- 36:00Give Up
- 37:45Summary
- 38:20Quote
- 39:05Question
related talks
38mNobody Wants to Work With You
39mHow To Be A Great Developer
50mTalk to Me Nicely - How to Communicate Your Ideas and Speed Up Your Career
20mKeynote: Programmers Don't Like People...or Do They?
47mTalk to Me Nicely - How to Communicate Your Ideas and Speed Up Your Career
51mCommon pitfalls in technical teams and how to avoid them
39mCommunication Skills What You Need to Succeed
36mKeynote - You're Insufficiently Persuasive