Setting the record straight....

If you do the crime, you do the time.

It’s funny that the most things we have blogged about is the Blame Hat and all the shame therein.

Well today went pretty good. We made a lot of changes to the Technical Design, things we didn’t foresee, however the design seems more robust and reusable.

A big part of making PC games is making sure they work across different hardware, a lesson I’m sure we have all learnt throughout the year. So today we began work on creating our game to work with different Graphics cards and drivers. Not the most exciting coding experience in the world but still necessary.

A big part of learning at Media Design School is learning Industry trends and practices.

Oh and Liam got the blame hat. I’ll just try to keep it away from me. I got pinged for spelling earlier on in the day, just as marketing walked in and snapped the very handsome photo. Naturally I changed the rules to not include spelling.

Untill another time,
If the minimum isn't acceptable it shouldn't be called the minimum.

Keegan Gibson
Build Master / Programmer

Stuff

Greetings.

In accordance, with the team's new "blame" policy, I was forced to carry the blame for the entire day, because I forgot an "=" and a "0". Now it's gone though, which is good, because I was slowly losing my insanity to the effects of the blame hat.
It gets to you... Sitting there, with the word "BLAME" written on it in large block letters...

Silently taunting you...

Gnawing away at the fringes of your mind...

Anyway, I guess I should sign off now, as my ramblings are growing thin...

One last thing,

To take a Panda by surprise, approach not from the back, as it will see you coming. For maximum con-panda-bility, approach from the sides.

An Implementation

You know the Blame Hat idea? Well it seems that it has become a reality. All it took was one folded piece of A3 paper and one white board marker. It has already been passed around three times.

An Idea

It seems apparent that even at Day two we're having a few issues. We have ten programmers all working on the same solution. We are using Tortoise SVN as a sort of repository system where everyone can upload their progress and download the progress of everyone else.

This works in theory. The problem arises when someone uploads a section of code that doesn't work and consequently everyone else receives the error. Tortoise SVN has a nice feature that allows you to see who uploaded a section of code, it even has the helpful title of the Blame button. This is all well an good, but I don't think it's good enough.

My solution is to implement some form of headpiece that has "Blame" written in big letters across it. The system works quite easily: whoever uploads an incomplete or buggy section of code is forced to wear the Blame Hat. The Blame Hat can only be removed when someone else uploads an error.

- Josh