|
|
|
|
|
by zach
990 days ago
|
|
If you’re interested, I worked for a short time on Daikanana and have some thoughts on this topic, some of which match up to themes in John’s book: https://www.cracked.com/personal-experiences-1596-5-things-w... To make this more HN-relevant, I will say that the whole point of Ion Storm was supposed to be unleashing Romero’s game direction, but the business partners who were supposed to give him that space instead provided another level of distraction. John worked insanely hard and doesn’t blame others for what he’s responsible for, but with all the business chaos at Ion which he dealt with personally, he just could not be on top of everything and that’s the major reason why DK was not the epic game it could have been. That’s the part that he doesn’t want to say, but to me it’s clear. It’s a good example of why a startup needs its product visionary highly focused at the most critical times. As a rough approximation, every night John went to bed thinking about Ion’s latest issues instead of thinking about Daikatana was a lost chance to make the game 2% better. That adds up. |
|
I read the article and it certainly touches on the high points, but to John's credit, he goes into much deeper detail in the book. Eight people left because of high level infighting, but John knew of the problem and didn't do anything about it until it was too late. John was for buying the Anachronox crew thinking it was an easy way to knock off one of their game commitments to Eidos. Turned out it wasn't so easy. Eidos was all in on the fancy office tower and happy to pay because it would be their corporate HQ as well.
I was a bit surprised that the article said Dallas was a difficult place to staff. My impression from the book was that good people were so keen to work with a big name game developer that they'd go anywhere to do so. My memory from the book was that John got pretty much anyone he made an offer to.