How to Program Your Team to Be Productive
summary
Rafał Żebrowski draws on 12+ years as a developer and 5 years freelancing to explain how to make software teams more productive by improving communication and mutual understanding. He gives simple, concrete examples showing why some teams work and others fail, argues for treating people individually, and describes how to speak to teammates and assign tasks so they want to do them.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 3:10Soft skills importance
- 6:00Team stories and lessons
- 10:15Attachment style and personality
- 13:29Eliminating fear of failure
- 17:29Role of criticism and feedback
- 21:04Overconfidence and creativity
- 23:11Team communication impact
- 25:03Self-awareness and strengths
- 27:57Personality types at work
- 31:33Elevator pitch for relationships
- 36:54Summary and Q&A
related talks
33mMeasuring Developer Productivity: the good, the bad and the data
01h 03mThe Effective Developer - Work Smarter, Not Harder.
17mSo You Think You Can Lead a Software Team?
20mWorking with Others and Delivering as a Team — Bridges Seen Through Human Relationships
12m12 Lessons That Made Me Ultra Productive
52mThe Developer Rhapsody
26mUpdate your team to be more extreme
31mThe Effective Developer - Work Smarter, Not Harder