A Modern Development Culture for a Modern Development Process.
summary
Studio uses trunk based dev with continuous integration and deployment, pushing builds to a build repository so one binary deploys to dev/stage/live via config rather than rebuilding. Life Beyond has 47 releases so far and a team that grew to ~40. Editor changes reach artists in ~5 minutes, targets rotate in an hour, and multiple daily deploys happen with nightly automated builds. Tools include crash reporter, smoke QA, static analysis, mandatory code reviews and feature flags; production ships with asserts on and reports zero known server crashes. Zero pre‑commit checks and 3–4 deploys per day illustrate tradeoffs between speed and stability.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 3:39Core values
- 5:22Process setup & automation
- 7:32Stability & quality
- 10:04Code reviews
- 12:29Release & deployment
- 14:18Technical direction
- 18:59Debt vs features
- 26:10Culture building
- 32:27Modernization tips
- 34:19Summary
- 34:39Q&A
related talks
34mEnabling a Continuous Deployment Mindset
45mContinuous Integration: That’s Not What They Meant
11mWorking with sharp tools - A case study of Continuous deployment
33mSoftware development practices for companies that want to make an impact
59mThe continuous culture
24mContinuous Deployment at Scale
01h 12mPitfalls of Continuous Deployment
25mFrom Git Push to Exit