Welcome to Syntax. Today, we're going to be talking about what you should be thinking about when planning or starting a new build or a new project.

The syntax team is going to be developing the third version of the syntax site really soon.

It was designed by a good friend of mine, designer Travis Nielsen, and we have the site design. We're ready to go.

So just yesterday, we sat down and came up with a big old list and a whole bunch of things about

what we need to accomplish, like who's going to do what, how we're going to organize things,

decisions we're going to make about this codebase, and we're going to be talking all

about that in this episode. My name is Scott Toulinski. I'm a developer from Denver, Colorado,

with me as always, is Wes Boss. What's up, Wes? Yeah, it's kind of interesting one, because

when you have either a new build or you have a major rewrite or redesign, there's some like decisions

that need to be made, right? And especially for like me, you and CJ, there's a lot, we use a lot

of different tech. We try absolutely everything. So it's, it's kind of important to sort of sit down

and say, all right, what are we going to use?

What are we sticking with? What are we changing? Sort of asking those questions of like,

how do we tackle this? Otherwise, we're going to be mash in all kinds of different

approaches and styles and whatnot together. And it doesn't become a good thing.

So I think this is a pretty common thing that hits teams that need to do or redesign.

So I thought it would be a cool episode.

Yeah, totally.

And one of those decisions we made, obviously, Wes, is to use Sentry.

Because one, we already have it in the code base, so we're not going to get rid of it now.

But two, last time when we launched the V2 version of Syntax, Century was like pretty

instrumental in making sure that after we launched that this thing was actually as good as it

...