Dev Logs
How I’m Structuring Laser Beast’s Level Progression
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.
Game Design Principles
Technical Design Documents: System Planning for Programmers
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.
Tutorials
Advanced Git Commands You Don’t Use Daily (But Should Know)
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.
Dev Logs
Laser Beast’s Programming is Done. Now We Build Levels.
Save systems, scene navigation, Steamworks integration, and the Bootstrapper all finished in April. Here is where Laser Beast stands heading into May.
Tutorials
The Git Commands Worth Learning First
A practical reference covering repo setup, branch management, and committing your work. The git commands that handle most of what you need.
Game Analysis
What Super Meat Boy Taught Me About Difficulty Progression
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.
Tutorials
A Git Workflow in Practice: Building Pong from Scratch
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.
Dev Logs
How I Built the Laser System for Laser Beast
The laser system in Laser Beast has four types, a shared visual layer, and an event-driven button system. Here is how it all fits together.
Tutorials
A Clean Git Workflow: Branching, Commits, and Pull Requests
A structured Git workflow keeps your project stable, your history readable, and your codebase ready to scale. Here’s the system I use on every project.
Game Design Principles
Planning Game Development from the Top Down
How a professional programmer plans game development from the top down. Start with the player, build toward core systems, and know when to stop planning.