Who Will Get the Axe?


log in or register to remove this ad


After being in corporate American for the last 15 years, I'll agree that often its because of mergers and such. But just as often it happens for no reasonable or aparent reason.

IMO, this is due to some budgetary reason that is then translated into revenge upon anyone in the position of decision-making power wishes to exact upon anyone they can effect. The people that management like? They get to stay. (How they are "liked" can be reasons both good and bad.)
 

For Now. That's what worries me about cutbacks like this - someone you think is pretty well entrenched there suddenly starts giving autoreplies like what Russ got from Linae.

Sad thing, too - Linae has been one of the best presences out there for putting a public face on WotC after the 2006 public relations debacle. My concern is we'll go right back to the people who actually interact with the fans just disappearing and the company going silent again like two years ago.

Could you elaborate on the 2006 PR debacle? I was paying very little attention to the industry during that year, so I'm at a bit of a disadvantage here.
 

More job openings posted on WotC in the last few days:

Database Developer 8/28/2008
Program Manager - D&D 8/26/2008
Software Architect - D&D 8/27/2008
Technical Analyst 8/29/2008
Sr. Software Development Lead 8/28/2008


Those don't exactly strike me as positions that you fill when you're even remotely close to sending a product like the DDI to market. Those seem like things that you have in place before you start working on a product. Anyone else think that they're scrapping prior code and hitting the reboot switch on some of the DDI's major features? Not a good sign.
 

Those don't exactly strike me as positions that you fill when you're even remotely close to sending a product like the DDI to market. Those seem like things that you have in place before you start working on a product. Anyone else think that they're scrapping prior code and hitting the reboot switch on some of the DDI's major features? Not a good sign.

Actually I could interpret that as a good sign. Given how successful Wizards software endeavours have been up till now, perhaps scrapping the lot is the best thing they can do.

It's firing Linae that looks like a bad sign to me, specifically wrt changes to the GSL. According to everyone who's dealt with her she is a pleasure to work with, which make's me wonder why she was let go. Paranoia: perhaps they don't need a licensing manager if they don't plan on having a license. Or maybe the internal fight over the GSL made her enemies.

Of course, the layoffs may just be a result of the new WotC president wanting to make his mark. Presidents like to mark things, like cats.
 

When did WOTC get a new president?

@ Elephant, I think the PR debacle of 2006 was when WOTC stopped talking to its fanbase. I could be wrong though.
 

More job openings posted on WotC in the last few days:

Database Developer 8/28/2008
Program Manager - D&D 8/26/2008
Software Architect - D&D 8/27/2008
Technical Analyst 8/29/2008
Sr. Software Development Lead 8/28/2008


Those don't exactly strike me as positions that you fill when you're even remotely close to sending a product like the DDI to market. Those seem like things that you have in place before you start working on a product. Anyone else think that they're scrapping prior code and hitting the reboot switch on some of the DDI's major features? Not a good sign.
Being a Lead Developer with 8 years of practice in the industry... yes, the positions indicate that they are either starting a new project or rebooting an existing one. That's about one-half of the team I believe is needed to make DDI work (the other half being another Software Architect, two more developers, a web specialist, and several artists; if anyone is wondering why two Software Architects are needed - let's just say that large projects such as this one require a second opinion).
 


More job openings posted on WotC in the last few days:

Database Developer 8/28/2008
Program Manager - D&D 8/26/2008
Software Architect - D&D 8/27/2008
Technical Analyst 8/29/2008
Sr. Software Development Lead 8/28/2008


Those don't exactly strike me as positions that you fill when you're even remotely close to sending a product like the DDI to market. Those seem like things that you have in place before you start working on a product. Anyone else think that they're scrapping prior code and hitting the reboot switch on some of the DDI's major features? Not a good sign.

Wouldn't you rather have a great product, which is significantly delayed, than a crappy product? I know I would. Of course, a reboot by no means that the end product will be great. However, there is a chance at least.
 

Remove ads

Top