How to fuck up your remote/offshore development
summary
Claims that offshoring often fails — roughly 50% failure rate — and that project budgets omit real costs like travel, setup and broken comms. Real problems listed: flaky internet that causes two weeks lost to outages, cultural misalignment, and rigid fix-price contracts that trigger penalties. Remedies that actually work are specific: paid ten‑day on‑site kickoffs, investment in reliable video conferencing and infrastructure, hiring senior engineers plus project managers with strong social skills.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:15Why remote development fails
- 7:44Hidden costs of offshore teams
- 14:53Cultural clashes in teams
- 22:34Legacy code challenges
- 29:23Fixed-price contracts backfire
- 33:17Solutions for distributed teams
- 35:25When remote development works
- 40:24Worst-case scenarios
- 46:44Q&A
related talks
40mBeing a remote developer
55mLeadership Without Borders: Working with Global Teams
17mFull Remote: How to Succeed Working as a Team?
57mLessons from {distributed,remote,virtual} communities and companies
49mGlobally Distributed Software Engineering - The Good, the Bad and the Ugly
52mRemote Working Approaches That Worked (And Some That Didn’t)
48mThe Secret Lives of SREs - Controlling the Costs of Coordination across Remote
55mHow to build a kick-ass remote Scala team