Soft Skills & Ecosystem Deep Dive · 2 of 12

Collaboration — How Teams Compound

Most engineers can solo-ship a feature. Few can level up the people around them. Collaboration is the deliberate set of habits — pairing, code review, async updates, blameless retros — that turn a group of contributors into a team that ships faster than the sum of its parts.

Pair / mobCode reviewAsync-firstPsychological safetyOnboarding
← Back to Soft Skills & Ecosystem
Pairing & Mobbing

Two Heads, One Keyboard

  • Driver / navigator. One types, the other thinks ahead. Swap every 20–30 minutes.
  • Best for hard problems — gnarly bugs, design choices, knowledge transfer to a new joiner.
  • Not for everything — routine work pairs poorly; do it solo and review.
  • Mob (ensemble) programming — three to five people, one keyboard. Killer for cross-team alignment and whole-team learning.
  • Remote pairing tools — VS Code Live Share, JetBrains Code With Me, Tuple, plain screen-share.
Code Review

The Single Most-Done Collaboration

  • Review for the right things. Correctness, design, security, maintainability — let formatters and linters handle style.
  • Ask, don't assert. "What happens when this is null?" beats "This is broken."
  • Praise the good. "Nice refactor here" costs nothing and changes culture.
  • Distinguish blocker / suggestion / nit. Reviewers should label severity; authors shouldn't have to guess.
  • Small PRs. 200 lines gets reviewed; 2000 gets rubber-stamped. Split aggressively.
  • Same-day turnaround. Slow reviews are the #1 dev-velocity killer.
  • Disagree-and-commit. Once the author has heard the concern and pushed back with reasoning, ship it; don't litigate forever.
Async-First Habits

Distributed-by-Default

  • Default to writing. A doc beats a meeting for anything more than two people.
  • Decisions in threads, not DMs. Public channels create searchable team memory.
  • Status updates without standups. A daily Slack post or a weekly newsletter scales further.
  • Respect time zones. Don't expect EU to attend a 9pm PT meeting weekly.
  • Long-form video (Loom) for complex demos — viewers control pace.
Team Culture

What Actually Compounds

  • Psychological safety — Google's Project Aristotle found this is the single biggest predictor of team performance. Wrong answers welcome; blame retired.
  • Blameless post-mortems. Focus on systems, not individuals. Track action items.
  • Onboarding buddies. First-week pair pays off for years.
  • "Disagree and commit" — debate ideas freely, then back the decision.
  • Reward asking for help. Not knowing is normal; pretending to know is dangerous.
Tradeoffs

What Goes Wrong

  • Reviewers as gatekeepers. If reviews feel like trials, juniors stop opening PRs.
  • Pairing all day, every day. Exhausting; reserve for hard problems.
  • Meeting overload. "Collaboration" doesn't mean "synchronous." Default to async.
  • Hero culture. A 10× engineer who can't share knowledge is a single point of failure.
  • Politeness as silence. Avoiding hard feedback is unkind; honest critique respects the recipient.
Continue

Other Soft Skills

← Communication Problem Decomposition → Time & Focus → Debugging Mindset → ↑ Back to Soft Skills & Ecosystem