Ten Lessons Learned
summary
Twenty-five years of game work boils down to concrete habits and accidents: keep learning across law, economics, UX and AI; build for 500 MHz servers with 4k×4k 1m-resolution maps and tune 400-byte packets; solve a 4 GB mapping problem for ten 16 km planets using layered Perlin-noise generators; expect water tiles sold on eBay when dynamic objects leak and watch that create microtransactions; prototype powerful platforms like MetaPlace backend but only ship what players actually want.
AI-written summary · about
chapters (6)
- 0:00Start
- 32:02Be ambitious and practical
- 34:49Surrender control
- 38:42We change people and the world
- 45:44Games are meaningless
- 51:43Ignore me.
related talks
58mCurrent challenges for game developers
39mBehind the Game: Strategies for Building the Tech That Powers Today’s Top Titles.
36m10 Years of Platonic Games - 10 Lessons Learned
21mWhen the Shit Hits the (RGB) Fan: What Can Go Wrong When Making Multiplayer Games
41mPanel: What Tools all Game Developers Should Have at Hand at all Times
43mGame Design lessons from designing Football, Tactics & Glory
01h 00mAdapting to the challenges of an ever-changing gaming landscape
43mGame Developers Life Lessons