What do you do when you can't get your hands on a dev kit? You "acquire" one, …

Share this story

Last week, I flew to EA's San Francisco offices in order to get a closer look at one of the company's next big games. Expect some in-depth coverage of that title in the next day or so. What was interesting about the trip was the amount of access we were given to the facility; the tours were a pretty eye-opening look at both how much money EA has and how hard everyone involved with the games works in order to get things out on time. Then there was the memorabilia, much of it attached to interesting stories. One of these stories begged to be told, and that was the tale of the pirate Genesis development kit.

You see, when the Genesis was a baby, Sega couldn't pump out enough dev kits to meet demand. This says something about the difference in power that EA had then versus the juggernaut it has become now; can you imagine a console manufacturer stiffing EA on dev kits today? At any rate, EA wanted very much to be in the Genesis business, so someone "acquired" a dev kit from someone else. Where that dev kit came from, or how EA was able to borrow it for an extended amount of time... these details were left a little hazy in the telling of the story.

The engineers at EA then went to work, tearing the dev kit down, taking notes, and then they turned around and backwards-engineered their own version of the hardware before returning it from whence it came. This is a pretty impressive technical feat, and luckily for the historians out there, EA kept this pirate dev kit, which is now on display in one of EA's collection of gaming hardware. It just shows that all is fair in love and gaming: if they won't give you the hardware you need, you need only grab someone's else's kit and make a copy.

This was a neat look at a bit of gaming history that most people don't know exists. Sometimes, to get ahead, you need a little underhandedness.