Why This Exists

Back when I was a freshman at DigiPen, I thought I was a master programmer. I had already tried (and failed) a programming degree at another college. I knew a few languages, including Java (I thought), Ruby (Ehhh…) and C++ (HA!). I spent multiple years programming in Ruby in RPG maker making games (“programming”) and made one game that had 14+ hours of content (of mixed results). I thought my experience making games alone would carry me through a college that thought it was difficult.

It turns out, making games is hard.

How do you plan content for levels based on the variable and often low skill of your teammates? How do you handle five classes, possible part time jobs, errands and other tasks while completing things for game class? How do you scope a project in the first place? What are some best practices you should be doing but probably aren’t? Do you even have the time to set them up and is it worth it?

That’s what this blog is for. I’m working at Google now as a tools programmer on Android Messages, and I’ve learned a lot since my first day at DigiPen. I’m still not a master programmer. This is a letter to my past self to let them know that they are especially not master programmer. To show them what they could be doing and why they should. To warn them of all the pits they’re going to fall into despite this warning.

This is a survival guide for DigiPen students.

It’s worth mentioning, this is highly geared towards programmers, especially tools programmers.

I don’t like to waste time. Let’s begin.