The harsh truth of video games programming
More like "The Harsh Truth About Me"<p>I'm a 30+ year veteran of both the indie and mainstream game industries. I've completed and released 4 titles solo. I once transferred my "non-transferable" games/3D/Unity knowledge to a dream job in Oculus Research. More than that, I've transferred my somewhat-game-specific ways of thinking about computation, simulation, and UI/UX to boring business jobs to great effect. Use your head and don't be so literal about what a transferable skill is. It needn't be memorized function signatures from the Unity API.<p>If you're looking to commiserate and feel better about how hard game programming is (and yes, it's hard) then this article is for you, maybe. Probably not. I don't know what good it will do you, but you can commiserate and feel better about quitting and finding something you like better. And if you don't really like game programming, obviously don't do it. But realize that not finding it rewarding is a statement about <i>you</i>. I've found it immensely rewarding in all the usual way$.<p>But if you're looking for anything constructive about becoming a better game programmer, this article may <i>hinder</i> you. It depressed me to read and to think that other people are going to read it and agree with it.