I'm pulling out of the gas station. We all know what that means. It's trying for another drive to work.

And when I got in my car today, I realized that I didn't have enough gas to make it to work.

And once before in the podcast, I've actually gotten gas during the podcast, and it went horribly.

So I decided today, I would start at the gas station, which is close to my house.

I will make sure to get a full 30 minutes.

So if I get to work and I'm not quite 30, I will stay until I get the 30.

So you guys will get your full.

I don't want to short you of any content.

Okay, so today I'm going to talk about an important tool that we use in making

magic sets. Today is all about databases. Ooh, databases, excited to happen. So I'm going to explain

what a database is, how we use it, and just talk about it as a tool that is an important part of making magic.

Okay, so essentially when you think about it, we are making a product.

When we make a magic set, we're making a physical product.

The end result is actual cards that have to get printed that have art on them and proper

rules text with templating and, you know, there is a finished product we are making.

So we need something that keeps track of that product.

Because a lot of different people will work on the product, and a lot of different people need to have insight on what's going on.

So we need a repository where all the information can be in one place.

In addition, we need to have the means to be able

to look back and see what changes got made and see, you know, maybe we change a card but didn't want

to change it back. We want to make sure we have a record of what once was. In addition, we want

a place where we can make comments, where people, someone who can see something, go, oh, I want to make sure

...