The 'I' in Team: Peer-to-Peer Best Practices for Growing Data Science Teams
summary
Starts from a two-person R team and shows a real mishap: an internal counselor package update that changes font sizes in a ggplot2 theme, silently altering R Markdown → Word plots during a time-sensitive report. Diagnosis lists concrete failures: poor documentation, no communication, misaligned priorities. Remedies are practical: use Git/GitHub conventions, add inline comments and usage notes, make team norms explicit, treat documentation as an investment, and schedule short social/onboarding sessions so new members and existing workflows actually survive change.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:33The incident and lessons
- 5:29Why 'I' in team matters
- 6:32Onboarding new teammates
- 10:51Patience in team growth
- 11:55Documentation as investment
- 14:43Social connections beyond work
- 15:46Individual responsibility
- 16:27Q&A
related talks
31mProductionalizing a Data Science Team
20mRipples of Change with R- It's more than just coding
38mBuilding Effective Data Teams: Strategies for Success
21mThe Power of We: Unleashing the Collective Strength of Your Team
39mAll Hands on Deck: Mentorship Breakdowns and How You Can Prevent Them!
26mUpdate your team to be more extreme
39mFoundations of Data Teams
27m5 Approaches to Increasing Your Open Source (Team) Happiness