Five Game Developer Habits That Help Software Engineers
summary
Five practical habits: start with a performance‑first mindset—use allocation/memory/polygon budgets and profile hot paths instead of deferring optimization; embrace a hybrid agility that allows short creative pivots inside sprint discipline; learn full‑stack game skills (Unity engine, Blender models, shaders, audio, backend/multiplayer, Git, Rider/Visual Studio and common Unity plugins/asset store); treat requirements as iterative experiments to discover “fun”; keep work playful with Easter eggs — the conference talk itself is a Unity mini‑game built with mocap after ~200–400 hours practice.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:30Speakers' backgrounds
- 3:14Why this talk
- 4:19Software vs game history
- 18:34Performance-first mindset
- 24:17Agility in development
- 28:58Full stack awareness
- 37:10Requirements as puzzle
- 42:29Fun and creativity
- 45:18Conclusion and key takeaways
- 47:51Q&A
related talks
57mHard truths and soft skills: 10 pieces of advice for novice game devs
52mGameDev as a hobby
11mTips from Industry Vets – Julie Wotzko
27mEvergreen skills for software developers
31mPanel: Tutorial Mode: What Every Developer Needs To Know Before Joining the Games Industry.
23mEvergreen skills for software developers
38mGrowing as a developer
31mThings I Wish I Knew When I Started Playing 'Developer'