Pipeline

This week, we're happy to welcome our newest member, programmer Andrew.

He comes to us with high recommendations, and we're glad to have him on board.

We've leapt upon the opportunity to have him play-test the game with fresh eyes, and he's already given us some useful feedback.

We're always eager to get new- fresh play-testers trying out Scourge.

Now, we're keen to get him integrated comfortably into our workflow.

Naturally, this has got us examining our code base and in-engine structure - and let's face it, we could probably use a clean out!

Getting ready for our internal project review, we just threw things together- hence the term 'Rapid Prototyping'.

However, its the time for us clean out the old and unused code and make sure the project is neat enough to sustain long-term development, especially now with another programmer joining the team.

Think of it like spring-cleaning... except everything is written in C#... and that damn designer doesn't use proper coding conventions half as much as he should!