sutton050

I'm a huge fan of the early World of Warcraft games, I make no secret of this, and spent far far too long playing the game when it came out.  I enjoyed the game into Burning Crusade and enjoyed PVP during Wrath of the Litchking, but I think somewhere along the way there Blizzard lost their mind. And way back in 2010, on the then in vogue talk show " Shut Up We're Talking ", I predicted where I thought things would go, and that looks pretty much to be where the game has gone, it's been dumbed down, and the MMORPG inflation on damage and stats has become insipid throughout. As such, I crave a Vanilla experience, and wish Blizzard would allow the free usage of the Vanilla assets (mainly extracted client data) for all the server emulations out there - Nostalrius and Felmyst come to mind. Until that happens however, I'm stuck exploring the old game myself, alone... Yes, I still have the original client DVD's I purchased in my battlechest and armed with CMangos,...

I've said before, and I'll say again, I'm not a fan of Test Driven Development, tests and test frameworks have their place, but they should not; in my opinion; be the driving force behind a projects development stream - even if it does give managers above the dev team a warm fuzzy sense of security, or if it allows blame to be appropriated later, you're a team, work as a team and use tests on a per-developer basis as a tool not as a business rule. *cough* I do go off topic at the start of posts don't I... *heerrhum*, right... Top Three Automated Testing Tips... From my years of experience... 1. Do not test items which are tested by masses of other developers... I'm talking about when you're using a frame work of library, ensure you are using it correctly certainly, do this at training or with your coding standard, but then do not labour the point by re-testing... Lets take a good example of this, the C++ Standard Library. The Standard Library contains many ...