Welcome to Syntax on this Monday, Hasty Treat.

We're going to be talking about local data.

Locally right now, Wes, I'm trying to get a snack in.

I don't know if you've ever had these rice mochi balls from Trader Joe's, but holy cow, they're my favorite thing in the whole world.

It takes great restraint for me not to eat them.

Eat the whole bag, yeah. Yeah, I don't keep them locally in my office usually because then I'll need to access

them all the time.

But if you need to access your data locally, we're going to be talking about that in

this episode.

But what happens if you need to access your data locally and that data's not there and

you're not checking to see if it's there correctly?

Well, you're going to to see if it's there correctly. Well,

you're going to get a bug in your site. And oftentimes, you know, with this stuff, especially

if we're talking about syncing engines, making sure the data is where it's supposed to be.

You can often get in these situations where we think we're in the happy path all the time.

And oftentimes we might not even realize what that happy path is. I experience that

all the time on my habit path app because I use local data and data syncing. And man, it is hard

to solve those bugs, but not with Century because Century lets me know who has what issues at any

given point in my application. And I know what's happening beyond the Happy path. It works for me. All my data is

local. It works. Nothing but sad paths in your century. Just a sad place to be. You know what?

The best part is, too, you know, Courtney also uses habit path. And just like most things,

when other people use your stuff, it's really nice for them to be like,

...