Okay, pulling out the driveway. We all know what that means it's time for drive to work. Okay, so today, I thought I would try a set that I actually was not on the design team for. It's actually said I was on the development team for. In fact, it was the very first team I ever worked on. Alliances. So, let me sort of

set up the situation because it was a lot of context to understand some of the stories today.

Okay, so, as far as personally, I had just been hired, as I explained.

What happened essentially was I got involved with Wizards through the duelist.

I first did my puzzle, and then I started writing articles for the dualist,

and then through that I started doing freelance work for other sections of the company.

In fact, I did work for, I don't know, seven some sections

of the company by the time before I got hired. And what happened was I was a good writer and I turned

my stuff in on time and, you know, magic was exploding and wizards was exploding. And so there's

a lot of opportunities for work. So one day I'm up at the offices because they used to fly me up to do some stuff, and I

happened to say that I'd be willing to move to Seattle, to which the reply was, when could

you start?

I actually had a job interview, but essentially it's like, okay, we're interested in you.

And I had said to Mike Davis, the guy who hired me at the time, the VP of R&D,

that I really thought I was a designer, not a developer, but he said, you know,

they have Richard Garfield, they didn't need designers, they needed developers.

So I'm like, okay.

And my long-term plan was always to, you know, get into design, but I figured

I would do what they needed, you know, get my foot in the door. So anyway, when I get there,

the very first thing they put me on is alliances. Now, let me stress, this was a very interesting

development team. It had 13 members. Every person remotely related in R&D who had anything to do with

magic was on the team. So why? Why did we have 13? So to understand this, let me give you a

...