I'm pulling out the parking lot. We all know what that means. It's time for the drive to work.

And man, I took my son to school today. Okay. So, last time I talked, I referenced an article I

done a long time ago called When Cards Go Bad. That was all about why we make bad cards. It was one of the earliest articles I'd ever written. And then 10 years later, I wrote an article that was all about why we make bad cards. It was one of the earliest articles I'd ever written.

And then 10 years later, I wrote an article called When Cards Go Bad, Revisited.

And what I did was, I approached the same topic, but from a completely different vantage point.

The previous time, I had talked really nuts and bolts of why we did it, like why design

and development have to make bad cards, and then I sort of took a step back, and my next column,

my revisiting column, was saying, hey, why are bad cards actually part of good design? And so

that whole article sort of just said, let's talk about major design principles and talk about why bad cards fit in those.

So I thought I would do a follow-up podcast on my follow-up article.

So this is my bad card revisited podcast where I'm going to talk about my article through that lens.

And so what I'd done is the very first article, I explained seven reasons why bad cards existed.

So in my follow-up article, I talked about seven principles of design and why they mean that bad cards are part of good design.

So today, I'm going to talk about those.

Okay.

So number one, games are supposed to challenge the player.

Okay, so let's talk a little bit about what games are supposed to be.

Once again, a topic I've talked about a bunch of times in this podcast, but it's important.

Games are meant to challenge their user.

The example I gave in the article was, let's say you're a designer of lamps.

You're making a lamp.

Well, the goal of a normal lamp is you want to be very, how do I turn the lamp on?

...