How to get into the games industry as a SoftwareEngineer
summary
Explains that game engineering is different from traditional software: engines like Unity Unreal and GameMaker and languages C# C++ JavaScript matter but so do rapid prototyping over perfect architecture and crossdiscipline communication with artists and designers. Claims nothing is standardized, jobs shift fast, expect to relearn tools and code often; recommends concrete actions: build small shipped projects, join game jams, show team size and role, and embrace writing code that will make you cry to validate designs quickly.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 5:27Game dev uniqueness
- 9:00Key differences
- 12:10Creative prototyping
- 16:41Multi-disciplinary challenges
- 23:46Barriers to entry
- 27:00Career paths & steps
- 30:11Final advice & Q&A
related talks
31mPanel: Tutorial Mode: What Every Developer Needs To Know Before Joining the Games Industry.
05mHow Video games have prepared me for a career in engineering
01h 05mFive Game Developer Habits That Help Software Engineers
27mMore Than Games, Options For A Future Beyond Games
57mHard truths and soft skills: 10 pieces of advice for novice game devs
36mBeginner's guide - How to become a game developer
01h 32mBeginner's guide - How to become a game designer
52mGameDev as a hobby