Integrating an expert solo developer into a development team
summary
An internal product called engineNetwork internal product already predicts engine health and ships analytics; integrating solo experts succeeds when specific gaps are fixed: teach git branching and team workflows, deployments to target environments, unit tests and code review etiquette, and use tooling like the black autoformatter to remove style fights. Early pair programming accelerates onboarding. The digital cell doubles in size while mistakes happen from hiring for code only and not validating communication skills; targeted coaching for each newcomer's gaps turns knowledge into maintainable, shared code.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 0:30Overview
- 1:08Who I am
- 2:56Digital Innovation Cell
- 3:46Engine Network
- 7:13Team Members
- 7:37The Hair
- 10:08The Butterfly
- 12:14The Owl
- 14:26The Skills
- 21:55Teamwork Skills
- 24:10Pair Programming
- 26:21Mistakes
- 29:11Summary
related talks
30mTechnical Onboarding, Training, and Mentoring
11mUn-becoming the bottleneck
01h 21mSoftware Development - Mob Programming, Pair Programming or Fly Solo?
45mAn Open Source Approach to Driving Developer Efficiency
26mBeyond the code: Leading engineering teams in the GenAI era
19mUsing paired programming to have fun & sell your solutions
32mLessons Learned from 7 Years of Running Developer Platforms
11mLeading without committing: Managing teams outside your tech stack