What I’d Look for Before Hiring a Game Programmer
For programmers looking for game dev jobs, here are the OOP principles, system design concepts, and version control practices I'd recommend knowing first.

If it has anything to do with how games get made, it lives here.
If something we learned the hard way can save you time, that’s a win.
For programmers looking for game dev jobs, here are the OOP principles, system design concepts, and version control practices I'd recommend knowing first.
Game design is easy to neglect during long development cycles. Here's the system I use to keep practicing it without losing momentum on my main project.
Designing difficulty progression means deciding what the player learns first, and in what order. Here's the framework I used for my game Laser Beast.
Programmers need a plan for every system and event before writing code. Here is how I build that plan, and why it works for more than just programming.
Some advanced git commands are useful, but don't come up often. It's helpful to know what these features are, what they do, and when to use them.
Save systems, scene navigation, Steamworks integration, and the Bootstrapper all finished in April. Here is where Laser Beast stands heading into May.
A practical reference covering repo setup, branch management, and committing your work. The git commands that handle most of what you need.
Super Meat Boy's difficulty progression is completely intentional. Here's what I learned analyzing it, and what I'm bringing into my own game.
Learn how a professional Git workflow applies to a real project. We use Pong as a simple, step-by-step demonstration from empty repo to shipped build.