Monday, December 3, 2012

INFR 3330 - Game Design Look Back

So I already did a look back for Engines, now it's time to do a quick look back for Game Design.

Similarly to Engines, I didn't really have any concrete expectation of this course going into it. I just expected to do less board games and more Unity games. That actually came true, since we've done less board games and most of our assignments were digital games now, mostly involving Unity.

UNITYYYYY (Wikipedia)

In terms of the course content, I actually enjoyed it pretty much. It might not show all the time, but I'm actually pretty interested in the stuff that is taught in the course, but I'm terrible at staying attentive in lectures. Especially when I'm tired, in which case I don't do well in any lecture.

The would say overall though, I liked the assignments for this class more than for Game Design I. It was nice not needing to make as many board games, and having a focus on digital games is awesome. I especially liked the Portal 2 assignment, since I thought that was pretty cool how we were using Portal for homework.

I'm just re-using old blog pics by this point.

Still, they were a lot of work. Aside from GDW, this class is definitely the class that has the most work. That's not necessarily a bad thing, but when GDW crunch time comes around, it does get fairly miserable. Especially when you have to rush assignments just to have them done and everyone is disappointed by the quality.

Regardless though, I had a bunch of fun making some of the prototypes and homework for this course, and it feels kind of weird knowing that I won't be having anymore Game Design courses. Anyways, back to working on deliverable for this classes GDW requirements.

Sunday, December 2, 2012

INFR 3110 - Engines Look Back

So it's the end of the semester. It went by surprisingly quickly. It honestly feels like yesterday that I walked into school again for my first day of classes, and now, it's pretty much the end.

We have one more week of classes left, so technically I have another Engines class, but chances are it'll be all review anyways. So here is a quick blog post on some of my thoughts about this class.

I couldn't think of a picture for this section, so here is Enrico petting a cat.

Before this semester started I was really hyped about this class. I was excited since it seemed like it was going to be an awesome class and that I would learn a lot from it. At the end of it, this class wasn't really what I expected. Granted I didn't really have an idea of what to expect aside from cool things.

In the end though, I still learned a lot and had a bunch of fun in the class itself. It was nice since it wasn't like a regular programming class where they were like "hey, this is how you do things", or "hey, look at these cool things you can do". It was more of a class that was like "hey, this is how things can be done", and they let you do your own thing.

And thus singletons. Singletons everywhere.

It was a nice change of pace, since honestly all the work we did we've pretty much done before in other classes. The only difference was that we did our work in a different environment, TwoLoc. As a result we had a chance to do the things we're familiar with, but in a different way.

I've definitely learned a lot of design patterns this semester. I feel that my understanding of engine structures and design have gotten a lot better, and I'm actually really excited to try and implement that stuff in my own framework when I have time to rewrite it.

Ugh this code is so bad. Need to rewrite it so badly.

Looking back, the homework questions weren't super bad either. So overall, I'm pretty happy with this course. Got a lot out of it I think.