A Moogle  🏳️‍🌈 💻 🎮 🎶 🇸🇪

Random advice thread on being a coder in the game industry. First things first: Clear your mind of any pie-in-the-sky ideas of working on your favorite game. The fact that I got to work on Minecraft was blind luck, and not representative of most game industry experiences.

Moreover, you should accept well in advance that, at some point at least, you'll wind up working on games you're not enthusiastic about, and that's OK. Everyone goes, "I want to work on Mario!" Nobody goes "I want to be a junior programmer on Barbie Magical Horse Adventure!"

But nothing's wrong with working on Barbie Magical Horse Adventure. As a programmer, you're not responsible for the design, or the art, or even the idea of the game. And lest you think I'm joking, @jimhejl can most likely back me up on this. Now? He's a Tech Director.

Point is, nobody in a position of hiring cares one whit *what* games you worked on. They care *that* you worked on them. That's a very important distinction to make: if you're cut out for the game industry, you will take pride not necessarily in the game, but in what you *do*.

Moving on from what you'll most likely be working on, let's talk pay. The game industry is not a path to riches, period, full stop. Unless you are *wildly* lucky, you are most likely not going to make the next Minecraft. It's just not statistically likely to happen.

In fact, if you want bank, go into banking or productivity software. However, working in the game industry *will* give you a rather reasonable paycheck. You will be able to support yourself, and a partner. And if the company does well, you just might get a good bonus.

If you want job security, the game industry is also most likely not for you, unless you quickly and markedly excel among your peers, making yourself invaluable. But that still won't save you from potential mass layoffs. Always have a plan B, a plan C, and a plan D.