Two sides of the same coin: Contracting the right way
summary
16 years in development and roughly 100 games of experience ground practical rules for hiring and being hired: set up shared access, pick a single bug database, and write bugs with exact reproduction steps and expected fixes so a mislabeled controller image on PlayStation doesn’t trigger a TRC failure. Build simple onboarding docs, agree release-date contingencies and who fixes what in the contract, and flag platform or SDK changes early to avoid late-stage rework.
AI-written summary · about
chapters (8)
- 0:00Contracting collaboration intro
- 3:59Core values for contractors
- 5:02Contract documentation clarity
- 10:04Proactive planning for workflows
- 20:38Specificity in communication and responsibilities
- 33:15Context for alignment
- 40:38Feedback handling transparency
- 43:28Q&A
related talks
30mEquipping your team to support junior developers
01h 03mHow To Do Kick-Ass Software Development
58mBackwards Compatible- Lessons from a Quarter Century in Software
57mHard truths and soft skills: 10 pieces of advice for novice game devs
51mSo you (or someone else decided) you're a producer
31mThings I Wish I Knew When I Started Playing 'Developer'
36mMaking it as an Indie Developer
33mVideo Game Developers: Masters of Workarounds?