WEBVTT

00:00:12.120 --> 00:00:15.680
<v Scott>Welcome to the Bikeshed podcast, where we talk about all things software engineering,

00:00:16.420 --> 00:00:20.220
<v Scott>which terminal I'm using today, and the new Getting Killed album by Geese.

00:00:21.040 --> 00:00:25.880
<v Scott>I'm your co-host, user of Ghostty Today, but Wezterm tomorrow, Scott Kaye.

00:00:26.450 --> 00:00:28.320
<v Scott>And alongside with me are my co-hosts.

00:00:28.840 --> 00:00:30.720
<v Scott>He wrote the blog post on building your application.

00:00:32.020 --> 00:00:34.440
<v Scott>Your code's current version bows down to his next one.

00:00:34.960 --> 00:00:36.860
<v Scott>He's deploying tomorrow's solutions today.

00:00:37.820 --> 00:00:38.460
<v Scott>Matt Hamlin.

00:00:39.480 --> 00:00:42.820
<v Scott>And my other co-host, the Southern Syntax Scorcher,

00:00:43.380 --> 00:00:46.340
<v Scott>melting server-side requests and blazing through performance.

00:00:47.300 --> 00:00:49.640
<v Scott>Dillon, spicy take curry.

00:00:51.540 --> 00:00:54.440
<v Scott>Fellas, I heard we got something different for the viewers today.

00:00:56.120 --> 00:00:57.300
<v Dillon>Yep, we sure do, Scott.

00:00:58.340 --> 00:01:01.720
<v Dillon>We have no topic, but we have some things we want to talk about.

00:01:03.060 --> 00:01:04.000
<v Dillon>So we're going to go through some of those.

00:01:05.300 --> 00:01:09.620
<v Dillon>Matt, why don't you let us know some of the things you think we're going to talk about today, at least.

00:01:09.740 --> 00:01:10.920
<v Dillon>And then we'll see where it takes us.

00:01:12.020 --> 00:01:13.660
<v Matt>I've been thinking a little bit about coffee brewing.

00:01:14.780 --> 00:01:16.080
<v Matt>So that's something we can talk about.

00:01:17.060 --> 00:01:20.540
<v Matt>Cursor 2.0 dropped the other week, which is interesting.

00:01:22.920 --> 00:01:24.840
<v Matt>And I've been struggling with Claude Code.

00:01:26.060 --> 00:01:27.980
<v Matt>So those are the things that I'm interested in.

00:01:28.020 --> 00:01:32.440
<v Matt>And I think next is a next.js is like maybe something we should dig into.

00:01:32.940 --> 00:01:35.420
<v Matt>Um, so maybe we'll, we'll cover that as well.

00:01:37.760 --> 00:01:42.660
<v Matt>So we, a variety, variety, uh, bag of, uh, mixed treats.

00:01:42.800 --> 00:01:44.160
<v Matt>It's a, it's, it's our Halloween episode.

00:01:44.320 --> 00:01:45.480
<v Matt>It's our trick or treat, right?

00:01:45.580 --> 00:01:47.220
<v Matt>You get, uh, get a few different things.

00:01:47.800 --> 00:01:51.560
<v Scott>I'm really excited to talk about how to use Claude code successfully.

00:01:54.140 --> 00:01:54.840
<v Dillon>You know, I think what's gonna happen.

00:01:55.040 --> 00:01:56.820
<v Dillon>We're just gonna talk about coffee for the next hour.

00:01:58.780 --> 00:02:00.140
<v Scott>i'd prefer to do that too

00:02:04.000 --> 00:02:09.720
<v Dillon>i happen to be drinking like some of the worst coffee at least in my opinion

00:02:04.000 --> 00:02:09.720
<v Matt>it's interesting like i feel

00:02:09.820 --> 00:02:14.860
<v Matt>like i agree i i'm not i'm not a fan of Dunkin coffee

00:02:09.820 --> 00:02:14.860
<v Dillon>they don't know what i'm holding up yeah

00:02:14.980 --> 00:02:19.800
<v Matt>for listeners don't drinking a what's the uh what's the go-to order everyone orders like an

00:02:19.900 --> 00:02:26.099
<v Matt>iced medium or whatever

00:02:19.900 --> 00:02:26.099
<v Dillon>this is just a Dunkin latte regular

00:02:19.900 --> 00:02:26.099
<v Matt>okay

00:02:19.900 --> 00:02:26.099
<v Matt>yeah we took the train down

00:02:26.100 --> 00:02:32.040
<v Matt>to Stamford on tuesday and uh tuesday morning and um the there's like a Dunkin at the train track or

00:02:32.040 --> 00:02:36.640
<v Matt>the train station there so we got some coffee there and it's like it's like all right it's fine but

00:02:36.700 --> 00:02:42.880
<v Dillon>it's not excellent yeah i only drink it when like i'm too lazy to make coffee which i have to be

00:02:43.050 --> 00:02:50.739
<v Dillon>really lazy but it is interesting as like a non-northeasterner like i feel like everyone here

00:02:51.060 --> 00:02:56.900
<v Matt>that's like from here like loves Dunkin but then it's like i've tried it and it's just like it's

00:02:56.900 --> 00:03:03.300
<v Dillon>just coffee it's not yeah yesterday who's from here and they're like Dunkin's the greatest and

00:03:03.300 --> 00:03:11.220
<v Dillon>i'm like no it's it's terrible but i'm not from here yeah yeah i'm gonna lie around that too i

00:03:11.580 --> 00:03:19.139
<v Scott>Dunkin is not good it's it yeah like have you had a dutch bros matt you've had dutch bros haven't

00:03:19.160 --> 00:03:20.340
<v Scott>They at least have those in California.

00:03:21.020 --> 00:03:25.360
<v Scott>So I feel like Dunkin' Donuts is more of like you're getting a dessert and not real coffee.

00:03:25.940 --> 00:03:27.500
<v Scott>Like that's the attraction to it.

00:03:28.020 --> 00:03:28.540
<v Scott>You know what I'm saying?

00:03:28.700 --> 00:03:30.920
<v Scott>It's not like about somebody who really likes to drink coffee.

00:03:31.080 --> 00:03:32.980
<v Scott>It's you want to get something that tastes good.

00:03:33.780 --> 00:03:35.460
<v Scott>Which Starbucks kind of does a lot now.

00:03:36.060 --> 00:03:38.260
<v Scott>But Dutch Bros does that to the nines.

00:03:39.180 --> 00:03:41.080
<v Scott>And it's like awesome.

00:03:41.360 --> 00:03:43.320
<v Scott>But even their regular cold brew tastes good.

00:03:44.120 --> 00:03:48.740
<v Matt>Have you guys seen those like TikTok short, YouTube shorts, whatever it is, Instagram reels,

00:03:48.920 --> 00:03:51.420
<v Matt>of people making insane Dunkin' orders

00:03:51.750 --> 00:03:54.260
<v Matt>where it's like, I want 15 scoops of sugar.

00:03:54.560 --> 00:03:56.260
<v Matt>And then they show a large iced cup,

00:03:56.700 --> 00:03:57.720
<v Matt>and half of it is sugar.

00:03:58.240 --> 00:04:00.460
<v Matt>And then they add in some syrup on top of it.

00:04:01.320 --> 00:04:04.920
<v Matt>I feel like that's just the standard Dunkin' Donuts order.

00:04:05.540 --> 00:04:07.060
<v Matt>The person that walks into Dunkin' Donuts,

00:04:07.060 --> 00:04:08.020
<v Matt>they order that thing.

00:04:09.380 --> 00:04:11.600
<v Matt>I feel like that's the only way that they can drink the coffee

00:04:11.690 --> 00:04:14.400
<v Matt>is if it has 90% sugar in it.

00:04:15.200 --> 00:04:16.420
<v Scott>They're not ordering the coffee.

00:04:16.579 --> 00:04:17.799
<v Scott>They're ordering the cream and sugar

00:04:17.820 --> 00:04:20.060
<v Scott>with a splash of coffee flavor.

00:04:20.320 --> 00:04:21.739
<v Scott>Yeah, that's exactly how I feel.

00:04:22.280 --> 00:04:22.820
<v Matt>Which is interesting.

00:04:22.870 --> 00:04:24.580
<v Matt>I feel like Dunkin' has that reputation,

00:04:24.670 --> 00:04:25.920
<v Matt>whereas Starbucks maybe doesn't.

00:04:26.220 --> 00:04:27.600
<v Matt>But Starbucks is definitely the same thing.

00:04:28.000 --> 00:04:29.400
<v Matt>It's like you're ordering a sugar drink

00:04:30.060 --> 00:04:30.900
<v Matt>with coffee flavoring.

00:04:31.540 --> 00:04:33.920
<v Dillon>This all makes me realize why I hate Dunkin'

00:04:33.980 --> 00:04:35.780
<v Dillon>is because I don't put sugar in my coffee,

00:04:36.000 --> 00:04:38.080
<v Dillon>even with a Dunkin' order.

00:04:38.360 --> 00:04:41.600
<v Dillon>So I'm getting the worst form of Dunkin'.

00:04:42.100 --> 00:04:42.220
<v Matt>Yeah.

00:04:43.300 --> 00:04:45.060
<v Dillon>Like if I was ordering the dessert in a cup,

00:04:46.160 --> 00:04:47.360
<v Dillon>then it would probably be okay.

00:04:48.200 --> 00:04:54.280
<v Dillon>but I'm just like getting the worst version of it I made that mistake with uh my first time at

00:04:54.380 --> 00:04:59.560
<v Matt>Dunkin I went I went down to we had to there was a Dunkin in the mall at Wayfair and I was in early

00:04:59.840 --> 00:05:04.640
<v Matt>and I went down with Andrew and like Andrew knew his order because he basically does Dunkin every

00:05:04.740 --> 00:05:11.340
<v Matt>day I'm pretty sure um and and I this is the first time I've been to Dunkin and I was like I'll just

00:05:11.440 --> 00:05:16.380
<v Matt>take like a cold brew and that was like or I don't even know if I ordered a cold brew I think it was

00:05:16.300 --> 00:05:22.320
<v Matt>just an iced coffee. I got like a, the largest size they have just pure black iced coffee. And

00:05:22.460 --> 00:05:30.980
<v Matt>that was maybe the wrong decision. It was terrible.

00:05:22.460 --> 00:05:30.980
<v Dillon>We've talked about all the bad coffee. I mean,

00:05:31.340 --> 00:05:36.900
<v Dillon>or Dunkin, sorry.

00:05:31.340 --> 00:05:36.900
<v Matt>Yeah.

00:05:31.340 --> 00:05:36.900
<v Dillon>Matt, recently you mentioned that you were trying to make coffee

00:05:37.540 --> 00:05:43.980
<v Dillon>at home and you had some issues. Well, yeah, I guess to back up a little bit. So I've been,

00:05:44.640 --> 00:05:48.100
<v Matt>So at home in Boston, we have an espresso machine.

00:05:49.180 --> 00:05:53.360
<v Matt>I'm blanking on the name, but it's kind of a similar model that Scott recently got.

00:05:55.300 --> 00:05:57.480
<v Matt>And so we used to do espresso basically every morning.

00:05:59.140 --> 00:06:02.060
<v Matt>But I've been switching up to using this palm press thing.

00:06:03.480 --> 00:06:07.460
<v Matt>It's kind of like a pour over, kind of like a French press blend thing.

00:06:08.200 --> 00:06:09.340
<v Matt>Like, you know, cross between the two.

00:06:10.820 --> 00:06:11.820
<v Matt>And that's been nice.

00:06:12.790 --> 00:06:14.600
<v Matt>But here at...

00:06:14.660 --> 00:06:16.400
<v Matt>at my in-laws, like we have like a Chemex.

00:06:16.690 --> 00:06:24.780
<v Matt>And so I've been trying to like, like, it's kind of nice to like experiment or use the Chemex when I haven't, I haven't really used it that often.

00:06:25.500 --> 00:06:30.200
<v Matt>And so like every time I come back and it's like a couple months or so between times I'm here.

00:06:30.320 --> 00:06:32.740
<v Matt>So it's like, I kind of like forget how I used it.

00:06:34.060 --> 00:06:41.760
<v Matt>So I used it yesterday morning and it's like, I just end up with a cup that's like kind of half, not really half full, but like there's a lot of like sediment at the bottom of the cup.

00:06:41.900 --> 00:06:42.980
<v Matt>And I was like, what am I doing wrong?

00:06:44.240 --> 00:06:46.960
<v Matt>apparently you need to use a paper filter along with the metal filter.

00:06:47.820 --> 00:06:50.860
<v Matt>That's something I just didn't think about.

00:06:51.340 --> 00:06:52.260
<v Scott>No, that's understandable.

00:06:52.840 --> 00:06:54.240
<v Scott>We've always had a pour over.

00:06:54.400 --> 00:06:55.140
<v Scott>I don't have the Chemex.

00:06:55.260 --> 00:06:56.180
<v Scott>Chemex is nice.

00:06:56.880 --> 00:07:00.820
<v Scott>But we just had a pour over where the paper filter wouldn't make it through,

00:07:00.880 --> 00:07:01.740
<v Scott>so we have to use both.

00:07:02.300 --> 00:07:04.240
<v Scott>So I just toss a paper filter inside.

00:07:04.780 --> 00:07:07.380
<v Scott>And it still gets a little bit of that stuff at the bottom of the batch.

00:07:08.820 --> 00:07:10.820
<v Scott>I honestly just try to pour that out.

00:07:11.720 --> 00:07:15.920
<v Scott>But another thing you can do is you can try to refilter that part of the batch.

00:07:16.480 --> 00:07:19.240
<v Scott>So like before you pour that last cup, pour it through another filter.

00:07:20.280 --> 00:07:21.560
<v Scott>But you don't have to do that.

00:07:21.680 --> 00:07:22.940
<v Scott>Chemex filters are probably costly.

00:07:24.100 --> 00:07:26.760
<v Matt>But you also do like Scott, correct me if you're wrong.

00:07:26.820 --> 00:07:31.320
<v Matt>You're using your Chemex as like a cold brew maker versus just like a hot pour over setup.

00:07:31.520 --> 00:07:32.980
<v Scott>No, I do a hot pour over now.

00:07:33.160 --> 00:07:34.820
<v Scott>I have a, you said a palm press.

00:07:35.060 --> 00:07:38.940
<v Scott>I actually have like a plastic version of the same thing.

00:07:39.040 --> 00:07:41.260
<v Scott>It's like a French press where I might do that.

00:07:41.420 --> 00:07:43.880
<v Scott>But I actually, that has a lot of grit in it too.

00:07:43.970 --> 00:07:52.420
<v Scott>So I'll actually pour that after through the paper in my regular pour over.

00:07:52.560 --> 00:07:56.240
<v Scott>I'll pour it through that again to try to like clean that up.

00:07:56.580 --> 00:07:58.720
<v Scott>You know, I wish the intro said something about coffee.

00:07:59.640 --> 00:08:00.880
<v Scott>It's like the first time I did that.

00:08:05.880 --> 00:08:10.859
<v Matt>Yeah, let me, I'm just digging up the thing that I have as my, like the thing I use basically

00:08:10.880 --> 00:08:14.880
<v Matt>daily is this like palm press i don't even i don't know if it's that brand but it looks the exact same

00:08:15.080 --> 00:08:22.000
<v Matt>thing we'll share a link to it in the uh in the episode notes the show notes

00:08:15.080 --> 00:08:22.000
<v Dillon>i was trying to dig

00:08:22.180 --> 00:08:27.880
<v Dillon>up this medium post that i wrote which sounds crazy because i never write blog posts so i think it's

00:08:27.880 --> 00:08:34.200
<v Dillon>like the last one last blog post i ever wrote was how to make like coffee and a chemex for people in

00:08:34.200 --> 00:08:41.440
<v Dillon>a hurry because i feel like at that time every like chemex video was like some barista spending

00:08:41.700 --> 00:08:47.240
<v Dillon>20 minutes teaching you how to do it and i feel like it's just not that complicated it's like the

00:08:47.320 --> 00:08:54.020
<v Dillon>most basic way to make coffee but it's simple clean and like easy i feel and it tastes the best in my

00:08:54.080 --> 00:09:02.359
<v Matt>opinion this was one of the things that i feel like i was uh late to catch on when we worked

00:09:02.380 --> 00:09:08.900
<v Matt>together at Wayfair was like the like brewing coffee in the office movement which I feel like

00:09:09.200 --> 00:09:17.060
<v Matt>it came back uh kind of at the tail end of COVID before we started leaving um but uh yeah I don't

00:09:17.060 --> 00:09:22.400
<v Matt>know I feel like it I feel like for the most part like getting coffee when when at work was either

00:09:22.500 --> 00:09:26.939
<v Matt>going to one of the coffee machines which is actually even worse than maybe Dunkin but uh

00:09:28.279 --> 00:09:33.920
<v Matt>or going like walking on our sort of twice daily trip to the Starbucks in the mall.

00:09:35.960 --> 00:09:36.160
<v Dillon>Yeah.

00:09:36.400 --> 00:09:37.940
<v Dillon>The making coffee in the office was just,

00:09:38.220 --> 00:09:40.800
<v Dillon>we didn't want to spend the money to go to Starbucks every day,

00:09:41.120 --> 00:09:44.120
<v Dillon>but it was also, it's just another form of the water cooler chat.

00:09:44.500 --> 00:09:46.300
<v Dillon>So we'd go like hang out, get a break from work.

00:09:47.340 --> 00:09:49.120
<v Dillon>And maybe there was a recent layoff.

00:09:49.460 --> 00:09:51.160
<v Dillon>So we just wanted to hide from our desks.

00:09:56.460 --> 00:10:08.480
<v Matt>Yeah, and then the Starbucks coffee walk eventually evolved into a blank street coffee walk, which eventually became nothing because we were spending too much money on coffee.

00:10:11.520 --> 00:10:11.760
<v Dillon>All right.

00:10:11.830 --> 00:10:12.820
<v Dillon>Have we coffeed out?

00:10:14.860 --> 00:10:15.060
<v Matt>Yea

00:10:15.520 --> 00:10:15.660
<v Scott>Nope.

00:10:15.670 --> 00:10:16.760
<v Scott>I got more to talk about.

00:10:16.850 --> 00:10:18.180
<v Scott>We didn't talk about my Breville yet.

00:10:19.980 --> 00:10:23.580
<v Matt>Yeah, Scott, give us a review of the Breville because you haven't used the Breville before, right?

00:10:23.640 --> 00:10:27.740
<v Scott>I never used a Breville or espresso machine ever.

00:10:29.060 --> 00:10:32.600
<v Scott>I mean, I made coffee with like Keurigs and stuff. All right. It's amazing.

00:10:33.360 --> 00:10:34.780
<v Scott>It's not too hard to do.

00:10:35.200 --> 00:10:38.660
<v Scott>I guess like everyone who has this or has an espresso machine is just going to

00:10:38.760 --> 00:10:41.320
<v Scott>know. I don't know if either of you have or had,

00:10:41.760 --> 00:10:44.400
<v Scott>but like the hardest part is probably when you get fresh coffee,

00:10:44.760 --> 00:10:47.440
<v Scott>understanding how much to grind it at.

00:10:47.560 --> 00:10:50.760
<v Scott>So there are grind levels that has its own grinder and you,

00:10:50.860 --> 00:10:52.880
<v Scott>you don't want it to be too fine or too coarse. If I remember,

00:10:53.180 --> 00:11:01.520
<v Scott>You want a pretty fine grind, but if it's fresher, you want it to be slightly coarser.

00:11:01.520 --> 00:11:02.780
<v Scott>You don't want it to be too fine.

00:11:03.000 --> 00:11:12.220
<v Scott>And then if it's not fresh coffee, you often have to use more of it to get a good pour versus when it's fresher, you have to have less in the level.

00:11:12.740 --> 00:11:15.580
<v Scott>So I've tried to weigh it, but it's tough.

00:11:15.750 --> 00:11:18.980
<v Scott>So basically the first one you do is like an experiment.

00:11:19.110 --> 00:11:20.180
<v Scott>Do I need a little more coffee?

00:11:20.420 --> 00:11:23.260
<v Scott>do I need a little less to try to get that perfect espresso?

00:11:23.900 --> 00:11:26.260
<v Scott>I have not used any of the tools with the Breville,

00:11:27.710 --> 00:11:28.920
<v Scott>the frother or any of that stuff.

00:11:29.320 --> 00:11:31.140
<v Scott>I've only used, I already have a frother,

00:11:31.480 --> 00:11:34.660
<v Scott>so we've made cold drinks, just haven't made any warm drinks.

00:11:35.760 --> 00:11:37.760
<v Scott>I've had one espresso shot,

00:11:38.070 --> 00:11:40.300
<v Scott>but I usually just make an Americano, add water,

00:11:40.580 --> 00:11:43.200
<v Scott>or I'll make it into a latte, but like an iced latte,

00:11:43.420 --> 00:11:45.300
<v Scott>not a warm drink yet.

00:11:45.560 --> 00:11:48.040
<v Scott>So TBD, when it gets really cold out,

00:11:48.090 --> 00:11:49.500
<v Scott>if I start having some warmer bevs,

00:11:50.060 --> 00:11:52.040
<v Scott>But the thing's great.

00:11:52.820 --> 00:11:53.720
<v Scott>It's been really nice.

00:11:53.930 --> 00:11:57.100
<v Scott>And for the first month of having it, I made one every single morning.

00:11:57.690 --> 00:12:01.080
<v Scott>And I make one for me and Brittney because I can just do a double shot.

00:12:01.500 --> 00:12:04.060
<v Scott>And we have shot glasses because I don't really drink.

00:12:04.090 --> 00:12:05.640
<v Scott>But I use these really nice shot glasses.

00:12:06.180 --> 00:12:07.680
<v Scott>Our friends David and Jane got us.

00:12:08.340 --> 00:12:11.140
<v Scott>And we put one in the fridge for her.

00:12:11.190 --> 00:12:12.440
<v Scott>And she just makes a drink with it.

00:12:12.560 --> 00:12:13.060
<v Scott>So that was great.

00:12:13.230 --> 00:12:15.060
<v Scott>I haven't done that for like the last week.

00:12:15.400 --> 00:12:16.720
<v Scott>And every weekend, that's what we drink.

00:12:16.900 --> 00:12:18.620
<v Scott>But I honestly haven't gotten Starbucks since.

00:12:19.660 --> 00:12:22.640
<v Scott>It's just like, I don't think Starbucks is like amazing or anything.

00:12:22.840 --> 00:12:26.720
<v Scott>I kind of use it now because like for a long time it had tons of deals.

00:12:27.000 --> 00:12:27.380
<v Scott>I'm ranting.

00:12:27.700 --> 00:12:29.160
<v Scott>I'm going on a full on rant.

00:12:29.410 --> 00:12:30.380
<v Scott>It used to have tons of deals.

00:12:30.470 --> 00:12:36.200
<v Scott>Like when we used to go on our trips at work and you'd get a free drink pretty often or

00:12:36.230 --> 00:12:37.540
<v Scott>you get something for free pretty often.

00:12:37.960 --> 00:12:39.300
<v Scott>I'd get a free bag of coffee or something.

00:12:39.820 --> 00:12:45.160
<v Scott>Now, like I rarely get them, but I'm starting to see them again since I think I haven't been

00:12:45.160 --> 00:12:46.100
<v Scott>a customer as much.

00:12:46.280 --> 00:12:49.420
<v Scott>But yeah, I just, Starbucks coffee is just okay.

00:12:49.620 --> 00:12:53.140
<v Scott>It's over roasted and you can tell it's like burnt.

00:12:53.640 --> 00:12:54.160
<v Scott>Yeah, it's burnt.

00:12:54.340 --> 00:12:54.940
<v Scott>It's like burnt beans.

00:12:55.920 --> 00:12:56.500
<v Scott>It's okay.

00:12:56.740 --> 00:12:57.840
<v Scott>It's fine in a pinch.

00:12:57.860 --> 00:13:01.440
<v Scott>It's better than Dunkin's for sure.

00:13:02.100 --> 00:13:04.280
<v Scott>But I have no reason to now.

00:13:04.420 --> 00:13:05.980
<v Scott>I'm just like, what beans do I get?

00:13:06.580 --> 00:13:11.400
<v Scott>And recently I had gotten some Atomic beans, the same that I had gotten you, Matt.

00:13:11.820 --> 00:13:13.380
<v Scott>I don't know if we discussed that on here.

00:13:13.440 --> 00:13:15.620
<v Scott>We didn't, but we're both drinking atomic.

00:13:15.840 --> 00:13:16.920
<v Scott>Maybe you've already went through it.

00:13:17.440 --> 00:13:22.080
<v Scott>And also I was at Atomic two days ago with Eric Hermanson.

00:13:22.400 --> 00:13:23.180
<v Scott>Shout out to Eric.

00:13:24.440 --> 00:13:26.200
<v Scott>I went to pick up a bag while we were there.

00:13:26.680 --> 00:13:29.760
<v Scott>They only had the smaller bags and then I forgot to grab one.

00:13:30.300 --> 00:13:32.860
<v Scott>Usually I get like a two pounder, but yeah.

00:13:33.400 --> 00:13:33.540
<v Scott>Okay.

00:13:33.820 --> 00:13:34.840
<v Scott>That's enough about coffee, right?

00:13:36.380 --> 00:13:39.140
<v Matt>One thing that, or a couple of things that came to mind as you're talking is like, one,

00:13:39.170 --> 00:13:44.480
<v Matt>we're probably going to alienate 90% of our audience because that we're like sort of really

00:13:44.660 --> 00:13:45.300
<v Matt>shitting on Dunkin.

00:13:45.400 --> 00:13:47.140
<v Matt>and then I feel like some of them are going to be like,

00:13:47.490 --> 00:13:49.180
<v Matt>I enjoy Dunkin or something like that.

00:13:51.300 --> 00:13:52.240
<v Scott>Whoa, whoa, whoa, whoa, whoa.

00:13:52.590 --> 00:13:56.120
<v Scott>I mean, it's not top tier coffee, but we all drink it.

00:13:56.680 --> 00:13:57.980
<v Scott>Dillon's drinking one right now.

00:13:59.080 --> 00:14:00.660
<v Scott>I'll recommend the cold brew.

00:14:00.750 --> 00:14:02.360
<v Scott>The cold brew is better than the regular iced

00:14:02.720 --> 00:14:05.420
<v Scott>as a less tangy taste to it or bitter taste to it.

00:14:05.540 --> 00:14:10.040
<v Scott>But it's just not, I don't know.

00:14:10.090 --> 00:14:11.660
<v Scott>If you're like a coffee connoisseur,

00:14:11.780 --> 00:14:13.340
<v Scott>it's like not the best beans.

00:14:13.360 --> 00:14:14.280
<v Dillon>It's never a first choice.

00:14:15.160 --> 00:14:15.720
<v Dillon>It's last choice.

00:14:16.560 --> 00:14:21.380
<v Scott>Have you guys watched the more recent seasons of Curb Your Enthusiasm?

00:14:23.540 --> 00:14:24.020
<v Scott>Okay, Larry.

00:14:24.200 --> 00:14:24.380
<v Scott>All right.

00:14:24.660 --> 00:14:25.360
<v Scott>Spoilers, spoilers.

00:14:25.600 --> 00:14:28.660
<v Scott>But Larry starts a coffee shop.

00:14:29.360 --> 00:14:32.220
<v Scott>And they just talk about it's all about the beans.

00:14:32.600 --> 00:14:33.420
<v Scott>And they make these jokes.

00:14:33.520 --> 00:14:34.360
<v Scott>Oh, he's got the beans.

00:14:35.700 --> 00:14:40.560
<v Scott>Dunkin doesn't "got the beans" as much as a smaller place.

00:14:44.160 --> 00:14:44.320
<v Matt>All right.

00:14:44.440 --> 00:14:46.440
<v Matt>Maybe we talk a little bit about cursor 2.

00:14:47.800 --> 00:14:50.620
<v Matt>So Scott has probably had no idea what we're talking about when we talk about

00:14:50.740 --> 00:14:52.500
<v Matt>cursor two, because he uses something called *bleep* chat,

00:14:53.140 --> 00:14:55.820
<v Matt>which maybe we're like leaking some internal secrets from Airbnb,

00:14:56.060 --> 00:14:57.500
<v Matt>but it's basically cloud code.

00:14:59.400 --> 00:15:00.380
<v Matt>I use cloud code at work.

00:15:00.580 --> 00:15:02.160
<v Scott>We were going to just say Claude code, man.

00:15:02.230 --> 00:15:03.200
<v Dillon>Just bleep it, man.

00:15:03.410 --> 00:15:04.540
<v Matt>He uses something called bleep chat.

00:15:04.920 --> 00:15:06.200
<v Scott>I'm going to have to learn how to bleep.

00:15:10.060 --> 00:15:14.000
<v Matt>But for those that are software engineers probably know,

00:15:14.120 --> 00:15:16.020
<v Matt>like within the past two weeks, I think,

00:15:16.240 --> 00:15:17.400
<v Matt>Cursor dropped their,

00:15:17.990 --> 00:15:19.280
<v Matt>so for Cursor, for those that don't know,

00:15:19.340 --> 00:15:20.320
<v Matt>Cursor is like a code editor.

00:15:22.100 --> 00:15:24.020
<v Matt>It's a fork of VS Code

00:15:24.900 --> 00:15:26.680
<v Matt>and has like a lot of AI features built in.

00:15:27.200 --> 00:15:28.840
<v Matt>They dropped their 2.0 release,

00:15:29.800 --> 00:15:31.560
<v Matt>which basically flipped the model.

00:15:31.670 --> 00:15:33.400
<v Matt>So before it was basically a nice code editor,

00:15:33.530 --> 00:15:35.860
<v Matt>like VS Code, with a lot of AI features built in.

00:15:36.260 --> 00:15:38.100
<v Matt>Now it's like an AI editor with,

00:15:38.420 --> 00:15:41.560
<v Matt>or like an AI experience with a code editor built in.

00:15:43.400 --> 00:15:47.200
<v Matt>And they also released a new model that they trained themselves that they said is really good.

00:15:48.880 --> 00:15:51.660
<v Matt>I've only used it a little bit, so I can't really speak too much about the model.

00:15:54.499 --> 00:15:59.480
<v Dillon>I'm looking at these UI changes, and it just feels like the chat has been flipped to the left side of the screen.

00:16:00.220 --> 00:16:02.960
<v Dillon>And then maybe there are a couple other drop-downs or something.

00:16:04.340 --> 00:16:08.880
<v Matt>Yeah, but it also defaults you to the chat-first experience, I think.

00:16:09.660 --> 00:16:10.040
<v Dillon>Okay.

00:16:11.400 --> 00:16:13.940
<v Matt>Like previously you would come into something that looks like this code where,

00:16:14.210 --> 00:16:17.020
<v Matt>you know, for most people it's like the file system, file tree on the left,

00:16:17.140 --> 00:16:18.340
<v Matt>and then your editor pane in the middle.

00:16:18.600 --> 00:16:21.380
<v Matt>And then you have like a right sidebar that had chat experience.

00:16:22.040 --> 00:16:24.420
<v Matt>Now it's like an, a chat experience.

00:16:24.910 --> 00:16:26.860
<v Matt>The left sidebar becomes a history of chats.

00:16:27.500 --> 00:16:30.260
<v Matt>And then on the right side, you can sometimes open up an editor window to

00:16:30.400 --> 00:16:32.240
<v Matt>see the diff of like what the code it's generating.

00:16:34.160 --> 00:16:34.600
<v Matt>It's interesting.

00:16:34.760 --> 00:16:37.980
<v Matt>I'm only realizing this now, but like kind of have like nice, like blend

00:16:38.160 --> 00:16:39.160
<v Matt>here of like experience here.

00:16:39.220 --> 00:16:45.120
<v Matt>because like Dillon i feel like you use primarily cursor or at work i guess

00:16:39.220 --> 00:16:45.120
<v Dillon>yeah basically have like

00:16:45.220 --> 00:16:51.360
<v Dillon>unlimited cursor tokens at work

00:16:45.220 --> 00:16:51.360
<v Matt>and you guys don't use Claude Code

00:16:51.400 --> 00:16:58.400
<v Dillon>i've dabbled with the cursor cursor cli which is similar to Claude Code only because i've had issues

00:16:58.540 --> 00:17:04.819
<v Dillon>with installing mcp servers into cursor but for whatever reason they work with cursor cli

00:17:06.360 --> 00:17:09.900
<v Matt>yeah scott's kind of on the opposite end where you guys don't use cursor at AirBnB

00:17:10.540 --> 00:17:14.439
<v Matt>but you'd use a chat experience in the terminal bleep chat

00:17:16.480 --> 00:17:24.620
<v Scott>we actually piloted cursor and it got bad feedback at the company uh just to reiterate for the

00:17:24.920 --> 00:17:31.739
<v Scott>millionth time i use vim the rest of the front-end engineering org at work uses vs code um so that's a

00:17:31.760 --> 00:17:38.220
<v Scott>thing. However, I guess I want to ask, so I am familiar with Cursor. I have used it.

00:17:39.000 --> 00:17:45.620
<v Scott>Like if it was real game changing, I would probably use it. Vim has plugins that basically

00:17:45.880 --> 00:17:52.460
<v Scott>do the same thing. I have a plugin called Avante at work that uses open AI models that literally

00:17:52.880 --> 00:17:57.399
<v Scott>emulates, I guess, Cursor V1. So what's the difference here? Is it just, it sounds like

00:17:57.420 --> 00:18:05.120
<v Scott>it's a ui change where um it's more of like let's do ai coding first but also is there like any

00:18:05.320 --> 00:18:09.640
<v Scott>difference with like MCP are there new features that actually make this better or is it just

00:18:10.100 --> 00:18:15.300
<v Scott>we're approaching cursor as an ai first product and less of a VScode clone that has an extension

00:18:15.810 --> 00:18:25.160
<v Matt>to do yeah that's my like sort of baked in read of it um the uh that it's like the and i guess we

00:18:25.140 --> 00:18:29.020
<v Matt>should be fair, like cursor was like a lot better than VS code in terms of like

00:18:29.050 --> 00:18:29.680
<v Matt>its AI features.

00:18:30.030 --> 00:18:33.680
<v Matt>Whereas like, like VS code, I haven't used it like vanilla VS code for a while,

00:18:34.090 --> 00:18:37.260
<v Matt>but like, I guess like they've been baking a lot of in like GitHub Copilot

00:18:37.390 --> 00:18:37.660
<v Matt>into it.

00:18:39.040 --> 00:18:42.760
<v Matt>But cursor was like sort of even better in the sense that had a like really

00:18:43.000 --> 00:18:44.280
<v Matt>deeply integrated AI experience.

00:18:46.060 --> 00:18:53.799
<v Matt>And now it's like basically an AI editor plus, you know, also some features for

00:18:53.900 --> 00:18:56.720
<v Matt>like manually looking at and editing code on the side.

00:18:58.300 --> 00:19:00.380
<v Scott>Can I just say I like looking at it.

00:19:00.380 --> 00:19:02.940
<v Scott>I watched a video of it quickly with the sound off.

00:19:03.520 --> 00:19:04.380
<v Scott>It just looks like

00:19:06.660 --> 00:19:08.300
<v Scott>Vercel built a

00:19:09.960 --> 00:19:11.800
<v Scott>coding app with V0.

00:19:12.500 --> 00:19:13.580
<v Scott>I mean, I don't know.

00:19:13.580 --> 00:19:15.220
<v Scott>It just looks like the

00:19:16.640 --> 00:19:18.000
<v Scott>ShadCN V0.

00:19:19.340 --> 00:19:20.280
<v Scott>Yeah, it just looks that way.

00:19:20.580 --> 00:19:21.540
<v Matt>And they had support.

00:19:21.840 --> 00:19:22.840
<v Matt>You brought up MCP also.

00:19:22.960 --> 00:19:25.400
<v Matt>but they had support for MCP before as well.

00:19:25.800 --> 00:19:27.780
<v Matt>And so I don't think that necessarily changes with this.

00:19:27.920 --> 00:19:30.720
<v Matt>It's just, they just sort of like re-skinned

00:19:30.900 --> 00:19:31.600
<v Matt>the editor experience.

00:19:32.620 --> 00:19:34.360
<v Matt>So you're just using a GUI to--

00:19:35.000 --> 00:19:36.120
<v Scott>- It's just a UI update.

00:19:36.340 --> 00:19:39.580
<v Scott>Like they don't, they didn't add new MCP changes,

00:19:39.840 --> 00:19:42.240
<v Scott>but it's like a major change because it's UI.

00:19:42.660 --> 00:19:46.040
<v Scott>So like, can you change, I guess this doesn't matter too much,

00:19:46.120 --> 00:19:48.180
<v Scott>but can you make coding your default

00:19:48.440 --> 00:19:52.440
<v Scott>or does it like force you into a AI first approach?

00:19:53.020 --> 00:20:06.300
<v Matt>I think it, so I think it defaults you to the agent experience, which is the AI first experience, but you can, I think, flip it to be an editor experience where you kind of go back to the standard VS code, like layout of like a file tree and a file view.

00:20:07.060 --> 00:20:12.880
<v Dillon>I think the editor view is like when you're using the chat, it's single model back and forth chat.

00:20:13.540 --> 00:20:20.760
<v Dillon>But when you opt into the agent view, it's like it gives you these additional tools to say like, we haven't really talked about this.

00:20:20.930 --> 00:20:25.000
<v Dillon>You can run one prompt against as many models as you want at the same time.

00:20:25.780 --> 00:20:27.800
<v Dillon>Or you can say like

00:20:25.780 --> 00:20:27.800
<v Scott>that's cool.

00:20:29.120 --> 00:20:32.860
<v Dillon>Run it five times for the same model and see the different responses.

00:20:33.800 --> 00:20:38.480
<v Dillon>And then you can also do a feature that some people have been doing, which is called using

00:20:38.610 --> 00:20:45.100
<v Dillon>Git worktrees to like run multiple agents on different copies of the same code.

00:20:45.150 --> 00:20:49.060
<v Dillon>But it has like built in support for that now, where you can like opt into worktrees

00:20:49.630 --> 00:20:52.160
<v Dillon>and then start running multiple agents at the same time.

00:20:52.400 --> 00:20:53.280
<v Dillon>I haven't tried this.

00:20:53.760 --> 00:20:56.860
<v Dillon>I can barely multitask at all.

00:20:57.180 --> 00:21:00.820
<v Dillon>So this sounds insane to try to like solve multiple problems on the same code base at

00:21:00.820 --> 00:21:01.340
<v Dillon>the same time.

00:21:01.700 --> 00:21:02.540
<v Dillon>But yeah, I don't know.

00:21:02.760 --> 00:21:05.300
<v Matt>Yeah, I'm curious about your guys' experience with Worktrees.

00:21:05.360 --> 00:21:08.560
<v Matt>Have you guys been using Worktrees at all with AI yet?

00:21:09.320 --> 00:21:09.640
<v Dillon>Not me.

00:21:10.480 --> 00:21:11.380
<v Scott>Wow, this is interesting.

00:21:11.580 --> 00:21:15.040
<v Scott>I actually started using Worktrees for this very reason.

00:21:15.680 --> 00:21:25.740
<v Scott>However, I realized I was experimenting because I wanted to see if our dev VM supported multiple instances of those Worktrees, and it doesn't.

00:21:26.420 --> 00:21:29.940
<v Scott>But I did start doing it so I could solve multiple problems at once.

00:21:30.440 --> 00:21:33.480
<v Scott>And I was actually talking to other friend of the show,

00:21:34.400 --> 00:21:36.300
<v Scott>Joe Boyle, about using Worktrees.

00:21:36.860 --> 00:21:38.160
<v Scott>And it was very interesting because I was like,

00:21:38.220 --> 00:21:39.280
<v Scott>oh, this is really easy to do.

00:21:39.520 --> 00:21:40.680
<v Scott>Like, I don't see why you wouldn't do this.

00:21:40.700 --> 00:21:42.980
<v Scott>I think the only caveat to using Worktrees

00:21:43.060 --> 00:21:44.780
<v Scott>was like you can't be on the same branch

00:21:44.980 --> 00:21:45.880
<v Scott>on multiple Worktrees.

00:21:46.380 --> 00:21:48.760
<v Scott>So like if you are on main or master

00:21:50.440 --> 00:21:51.580
<v Scott>for one of your branches,

00:21:52.520 --> 00:21:54.420
<v Scott>like if you try to switch on another branch,

00:21:54.540 --> 00:21:55.300
<v Scott>you just, you can't.

00:21:55.860 --> 00:21:57.060
<v Scott>So that is like a caveat.

00:21:57.720 --> 00:21:59.380
<v Scott>But Joe had mentioned, he's like,

00:21:59.500 --> 00:22:03.420
<v Scott>Yeah people I've talked to that do this, just clone the repo in multiple places. Like, what's

00:22:03.420 --> 00:22:06.660
<v Scott>the difference? And he said, sell me on work trees. I said, I don't know. I'm just like,

00:22:07.020 --> 00:22:12.920
<v Scott>just learning work trees. It seems like, I don't, I guess my only sale here would be like,

00:22:13.280 --> 00:22:20.000
<v Scott>if you have a mono repo or a repo that's so big, like one of our repos, cloning a worktree could

00:22:20.160 --> 00:22:27.160
<v Scott>take a long time, even if you're like doing a depth one flag on that clone. So like, yeah,

00:22:27.360 --> 00:22:32.120
<v Scott>work tree might make sense, but I mean, I'm not going to honestly advocate too

00:22:32.220 --> 00:22:33.760
<v Scott>hardly for that anymore.

00:22:33.990 --> 00:22:37.480
<v Scott>Like get built a feature that's like inception of itself.

00:22:37.990 --> 00:22:41.200
<v Scott>If you can just clone the same thing multiple times, but I mean, I don't know,

00:22:41.260 --> 00:22:45.260
<v Scott>it's teach his own, whatever path works for the user, but I do think it's a

00:22:45.360 --> 00:22:46.040
<v Scott>really cool workflow.

00:22:46.250 --> 00:22:49.900
<v Scott>I did watch a Primeagean video about how he was like, you should be using this.

00:22:50.720 --> 00:22:53.820
<v Scott>This is the best thing ever, but it's a, it's a couple of years old.

00:22:54.480 --> 00:23:07.240
<v Scott>I thought it was neat and I wanted to learn it, but if I can't actually have like a version of the application running in multiple places, it's a little bit of a moot point kind of defeats the purpose.

00:23:07.480 --> 00:23:20.100
<v Scott>But if you're doing like a quick fix or something or adding a test or, you know, fixing pipelines, the stuff that you don't really need to look at at the moment, I guess you could multitask.

00:23:20.140 --> 00:23:22.560
<v Matt>Yeah, I've been I haven't gone down the worktree support.

00:23:22.760 --> 00:23:27.640
<v Matt>I've just gone down, like, I'm just going to clone the repo into, you know, we have a repo called Bend HubSpot.

00:23:27.740 --> 00:23:29.820
<v Matt>And now I just have a clone called Bend HubSpot-2.

00:23:30.300 --> 00:23:34.200
<v Matt>And then maybe if I need a third one, I can do Bend HubSpot-3, et cetera.

00:23:34.320 --> 00:23:38.860
<v Matt>And then it's just like, it's just easier for me to manage that versus WorkTrees.

00:23:39.000 --> 00:23:41.980
<v Matt>Because I never really invested the time to actually understand it.

00:23:43.180 --> 00:23:47.520
<v Dillon>Yeah, since this feature came out yesterday, that's probably the primary reason I haven't used it yet.

00:23:48.200 --> 00:23:57.120
<v Dillon>But I just thought while Scott was talking that my like ideal use case for work trees or multiple clones is I'm working on a feature.

00:23:58.360 --> 00:24:04.140
<v Dillon>And then something breaks out like an incident happens, for instance, and now I need to make a hot fix.

00:24:04.800 --> 00:24:05.920
<v Dillon>I'm like halfway through this feature.

00:24:06.250 --> 00:24:16.960
<v Dillon>I previously I just like literally add on my stage changes and just commit them and just say work in progress, which is like a really weird way to leave off.

00:24:18.419 --> 00:24:22.760
<v Dillon>but with work trees I'm seeing that like I don't have to do that I can just go like make my hot

00:24:22.840 --> 00:24:28.700
<v Dillon>fix separately commit that and then when I'm done I can come back and like continue where I left off

00:24:28.960 --> 00:24:34.680
<v Dillon>and I'm now I'm like I gotta do this yeah I feel like that's the the old head approach of git where

00:24:34.760 --> 00:24:39.760
<v Matt>it's like yeah just create a commit or stash it I think Scott is a big is a big stash fan yeah just

00:24:39.880 --> 00:24:44.499
<v Matt>stash your changes check out the new branch apply the change or whatever and then jump back and then

00:24:44.520 --> 00:24:46.200
<v Matt>on the pop your stash.

00:24:48.799 --> 00:24:50.160
<v Scott>- Yes, so what Dillon's saying,

00:24:50.380 --> 00:24:51.920
<v Scott>that is like the selling point for it.

00:24:51.960 --> 00:24:52.920
<v Scott>Every video I watched,

00:24:53.000 --> 00:24:54.560
<v Scott>like it's actually a pretty simple API.

00:24:54.840 --> 00:24:55.540
<v Scott>There's probably more to it.

00:24:56.100 --> 00:24:56.900
<v Scott>There's definitely more to it.

00:24:56.920 --> 00:24:58.440
<v Scott>It's like, but all I know is like,

00:24:59.080 --> 00:25:00.500
<v Scott>get Worktree add, get Worktree delete.

00:25:00.740 --> 00:25:02.860
<v Scott>And then like I get checkout different branches

00:25:03.060 --> 00:25:04.340
<v Scott>on different streams.

00:25:04.740 --> 00:25:06.780
<v Scott>And basically just to explain what it does,

00:25:07.020 --> 00:25:08.040
<v Scott>I probably should have done this earlier,

00:25:08.160 --> 00:25:10.040
<v Scott>but all it does is when you create a new Worktree

00:25:10.460 --> 00:25:13.060
<v Scott>inside of the repo, it creates a new folder.

00:25:13.520 --> 00:25:15.300
<v Scott>that's like a mimic of that repo.

00:25:15.430 --> 00:25:17.620
<v Scott>So if I do like Git Work Tree secondary,

00:25:17.870 --> 00:25:19.040
<v Scott>which is what I do for some reason,

00:25:20.080 --> 00:25:22.820
<v Scott>then inside my repo, there's a secondary folder

00:25:23.320 --> 00:25:24.520
<v Scott>and that's basically all it does.

00:25:24.640 --> 00:25:27.060
<v Scott>It's like a nested version of the same thing.

00:25:28.120 --> 00:25:31.020
<v Scott>So it's not crazy, but Dillon, yes,

00:25:32.420 --> 00:25:35.420
<v Scott>your explanation of it is like exactly the use case for it.

00:25:35.770 --> 00:25:38.860
<v Scott>But also, yeah, Matt, I am a huge fan of stashing.

00:25:38.950 --> 00:25:42.039
<v Scott>Like actually, funny, I've become even bigger

00:25:42.060 --> 00:25:48.100
<v Scott>of a fan of stashing, but now like I learned how to like stash and then, uh, stash a couple

00:25:48.100 --> 00:25:48.620
<v Scott>of files.

00:25:49.080 --> 00:25:52.560
<v Scott>And now I, I name all my stashes so that they actually have relevance.

00:25:53.400 --> 00:25:57.960
<v Scott>Um, and I've been like crazy about it because I had been going back and forth here.

00:25:58.220 --> 00:26:01.860
<v Scott>Cause I, I can only see like one thing, but I'm constantly kind of pulled between two

00:26:02.040 --> 00:26:05.500
<v Scott>things and development is a little slower at the size of the, the company.

00:26:05.760 --> 00:26:10.000
<v Scott>So like when someone pulls me off on something, I'm stashing and naming at this point.

00:26:10.060 --> 00:26:11.580
<v Scott>And I, I honestly, I'm just fine with that.

00:26:12.220 --> 00:26:14.260
<v Matt>I feel like at that point, why not just commit?

00:26:14.760 --> 00:26:17.220
<v Matt>And that way you basically have...

00:26:17.220 --> 00:26:20.260
<v Matt>I feel like stashing and committing at that point are basically the same thing.

00:26:20.640 --> 00:26:23.380
<v Matt>So I've been doing work in progress commits.

00:26:23.500 --> 00:26:27.300
<v Matt>So I'll just commit with a message of work in progress with some context.

00:26:28.140 --> 00:26:30.080
<v Matt>And then I'll jump over to the other branch and then do the changes.

00:26:30.090 --> 00:26:32.020
<v Matt>And I jump back and I just soft reset.

00:26:32.860 --> 00:26:36.520
<v Matt>So I get the changes back so they're staged and whatnot.

00:26:36.650 --> 00:26:37.380
<v Matt>And then I can edit it.

00:26:37.520 --> 00:26:40.600
<v Matt>Or I create more changes and I just amend my commit.

00:26:41.440 --> 00:26:44.040
<v Matt>when I'm ready for rephrasing it.

00:26:46.260 --> 00:26:47.200
<v Scott>I'll do that too, actually.

00:26:47.810 --> 00:26:49.059
<v Scott>I guess it depends on...

00:26:50.960 --> 00:26:52.260
<v Scott>The choice for me depends on

00:26:52.430 --> 00:26:53.840
<v Scott>how rough are the changes I'm making.

00:26:55.240 --> 00:26:56.460
<v Scott>Often, I'll build some stuff.

00:26:56.470 --> 00:26:58.400
<v Scott>We don't have sometimes clear constraints.

00:26:59.200 --> 00:27:00.380
<v Scott>And I might do something,

00:27:00.520 --> 00:27:01.400
<v Scott>and it passes all the tests,

00:27:01.470 --> 00:27:02.260
<v Scott>and I think it's right.

00:27:02.680 --> 00:27:06.180
<v Scott>And then I realize there's X other problem or whatever.

00:27:06.860 --> 00:27:09.480
<v Scott>And I'm starting to rummage my way through it.

00:27:09.600 --> 00:27:13.880
<v Scott>If I don't feel like it's in a great spot, I'd rather stash those changes and then think

00:27:14.000 --> 00:27:18.680
<v Scott>about, okay, could I push this one out and make these as a follow-up commit?

00:27:20.140 --> 00:27:20.740
<v Scott>Think about it.

00:27:21.180 --> 00:27:25.100
<v Scott>Basically, if I'm in a really rough state with what I'm doing, I'll stash that.

00:27:25.340 --> 00:27:30.460
<v Scott>I don't really want to taint something that's in a better place.

00:27:31.100 --> 00:27:32.180
<v Scott>So I guess that's how I view it.

00:27:32.500 --> 00:27:33.620
<v Scott>But I do the same thing.

00:27:33.680 --> 00:27:35.840
<v Scott>I don't even write work in progress.

00:27:35.980 --> 00:27:36.740
<v Scott>I just say updates.

00:27:38.000 --> 00:27:42.540
<v Scott>I literally have like a one-liner that just says git commit updates.

00:27:44.860 --> 00:27:45.000
<v Matt>Yeah.

00:27:46.460 --> 00:27:47.600
<v Matt>I guess one of the things that,

00:27:48.460 --> 00:27:50.120
<v Matt>jumping a little bit back to the cursor to stuff,

00:27:50.300 --> 00:27:53.200
<v Matt>it's one of the things that sounds exciting is that it sounds like it

00:27:53.460 --> 00:27:56.680
<v Matt>abstracts away the work tree complexity from you potentially,

00:27:57.300 --> 00:27:58.340
<v Matt>which I think will be nice.

00:27:58.490 --> 00:27:58.760
<v Matt>Cause yeah,

00:27:58.900 --> 00:27:59.040
<v Matt>it's not,

00:27:59.280 --> 00:27:59.460
<v Matt>you know,

00:27:59.720 --> 00:28:00.620
<v Matt>maybe it's not that complex,

00:28:00.770 --> 00:28:01.280
<v Matt>but I feel like,

00:28:01.560 --> 00:28:01.680
<v Matt>you know,

00:28:01.740 --> 00:28:02.160
<v Matt>it's like a,

00:28:02.940 --> 00:28:03.500
<v Matt>at this point,

00:28:03.500 --> 00:28:06.020
<v Matt>I feel like I'm a kind of like an old dog with git where it's like,

00:28:06.020 --> 00:28:06.480
<v Matt>you can't treat,

00:28:06.850 --> 00:28:07.740
<v Matt>you can't,

00:28:08.659 --> 00:28:10.000
<v Matt>you can't learn new tricks.

00:28:11.500 --> 00:28:12.720
<v Matt>And so hopefully Cursor is like,

00:28:13.100 --> 00:28:13.880
<v Matt>just does that for me

00:28:14.140 --> 00:28:15.060
<v Matt>and I don't have to worry about it.

00:28:15.060 --> 00:28:15.740
<v Matt>It's like a black box.

00:28:15.880 --> 00:28:17.040
<v Matt>It's just like, it'll do that.

00:28:18.840 --> 00:28:20.540
<v Dillon>Yeah, that's kind of how it is for me.

00:28:20.660 --> 00:28:21.800
<v Dillon>It's like, I've never used work trees

00:28:22.600 --> 00:28:23.660
<v Dillon>and then it's like, oh, it has work trees.

00:28:23.730 --> 00:28:24.900
<v Dillon>And it's like, oh, I've heard of those.

00:28:25.420 --> 00:28:26.620
<v Dillon>I've never like put in the time

00:28:26.650 --> 00:28:27.540
<v Dillon>to learn how to use them.

00:28:28.520 --> 00:28:29.500
<v Dillon>But maybe this will make it easier

00:28:29.550 --> 00:28:31.120
<v Dillon>for me to like test it out.

00:28:32.120 --> 00:28:34.280
<v Dillon>And then I sort of going back to 2.0.

00:28:34.380 --> 00:28:36.379
<v Dillon>Another feature you kind of touched on

00:28:36.400 --> 00:28:43.520
<v Dillon>there's this new composer model that they they're shipping with it um which only had maybe an hour

00:28:43.530 --> 00:28:50.440
<v Dillon>of testing with it but they they basically say that it is it has some like instructions to

00:28:50.950 --> 00:28:57.060
<v Dillon>to inform it more about all the different editor tools that are like available to the agent so it

00:28:57.260 --> 00:29:03.080
<v Dillon>should be like plugging into that like into the cursor workflow better um so i'm curious i'm

00:29:03.100 --> 00:29:08.900
<v Dillon>interested to see like does that actually net like have a net positive to your development but we'll

00:29:08.980 --> 00:29:14.800
<v Matt>see yeah i've been on the side and this maybe transitions us to another topic also but on the

00:29:14.880 --> 00:29:22.340
<v Matt>side i've been sort of vibe coding a like deploy it yourself cms package um which is interesting

00:29:22.660 --> 00:29:28.080
<v Matt>in the sense of like you like it'll ship with adapters that you basically run and like like if

00:29:28.080 --> 00:29:33.060
<v Matt>you're running it on node on some you know like on your on a vps or something that you just use a

00:29:33.080 --> 00:29:37.100
<v Matt>adapter and you hook it up to like Postgres and stuff like that and it just manages it for you

00:29:37.610 --> 00:29:42.780
<v Matt>um and but the default path I'm like sort of optimizing for is like hosting on Cloudflare

00:29:42.900 --> 00:29:50.060
<v Matt>workers so I can just like deploy it to Cloudflare and like and like hook it up to KV and uh SQLite

00:29:50.340 --> 00:29:55.980
<v Matt>database and stuff like that and it just works um but uh so like last night for the most part

00:29:56.060 --> 00:29:59.940
<v Matt>I've been using Claude Code for a lot of that development uh just because I find Claude like

00:29:59.960 --> 00:30:04.080
<v Matt>pretty good as a tool. I've tried using ChatGPT's

00:30:04.620 --> 00:30:08.080
<v Matt>codex CLI, but it's a little clunky. I feel like it's not as good.

00:30:08.720 --> 00:30:11.840
<v Matt>And so last night, I was like, all right, I hit my

00:30:12.920 --> 00:30:15.880
<v Matt>this is maybe another topic, but I hit my limit on Claude code. So I was like,

00:30:15.880 --> 00:30:19.200
<v Matt>all right, I basically need to stop for the night and then return to it tomorrow.

00:30:19.660 --> 00:30:21.620
<v Dillon>I can't work anymore. The AI can't help.

00:30:22.040 --> 00:30:27.700
<v Matt>Exactly. But then I realized, I was like, oh, cursor 2 is out.

00:30:27.780 --> 00:30:28.940
<v Matt>but maybe I'll just give it a little try.

00:30:29.130 --> 00:30:30.960
<v Matt>And so I jumped into it with Cursor 2

00:30:31.200 --> 00:30:34.020
<v Matt>and had it start working on some stuff

00:30:34.160 --> 00:30:35.600
<v Matt>and it built out, I think.

00:30:35.850 --> 00:30:37.480
<v Matt>And so that's another interesting thing

00:30:37.620 --> 00:30:39.240
<v Matt>is I need to go back and validate all this code.

00:30:39.370 --> 00:30:41.440
<v Matt>I haven't actually read all the stuff it's generated so far,

00:30:42.420 --> 00:30:45.220
<v Matt>but it built out like a GraphQL support for the CMS.

00:30:47.180 --> 00:30:48.700
<v Matt>And it seemed fine.

00:30:48.870 --> 00:30:51.380
<v Matt>Like it got the same, like it seemed like it got work done.

00:30:51.580 --> 00:30:53.160
<v Matt>It's been writing tests and the tests are passing,

00:30:53.380 --> 00:30:53.780
<v Matt>which is good.

00:30:55.140 --> 00:30:57.740
<v Matt>But I feel like it's certain places in the model

00:30:57.760 --> 00:31:01.620
<v Matt>this is using the new composer model, certain places where it was just like, oh, like there's

00:31:01.670 --> 00:31:04.900
<v Matt>some typescript errors, but that's not related to my changes. So I'm not going to worry about those

00:31:05.180 --> 00:31:08.260
<v Matt>or, oh, there's some test failing, but that's not related to my changes. I'm not going to worry

00:31:08.360 --> 00:31:12.740
<v Matt>about those. Whereas Claude, I feel like either through my training, through my Claude.md file,

00:31:13.380 --> 00:31:19.560
<v Matt>like I've gotten it to care about those and actually like fix those. Um, I feel like it's

00:31:19.560 --> 00:31:24.600
<v Matt>the classic example of like sort of lazy engineers are like, oh, that's failing on main. And so I

00:31:24.620 --> 00:31:30.020
<v Matt>don't care about fixing it locally on my branch or whatever um yeah i don't know i've been going on

00:31:30.020 --> 00:31:35.220
<v Matt>and off about this but uh i don't know if that's been your guys's experience with using ai also of

00:31:35.280 --> 00:31:40.400
<v Matt>like is it kind of lazy in the sense of like if something is failing but it's it itself is like

00:31:40.740 --> 00:31:43.020
<v Matt>oh i don't need to fix that because it's not related to what i'm working on

00:31:43.820 --> 00:31:50.500
<v Matt>or have you guys found that that's not the case locally

00:31:43.820 --> 00:31:50.500
<v Dillon>give me an example maybe you just did, I need it again

00:31:50.720 --> 00:32:15.000
<v Matt>I mean, one example is like, oh, like tests are failing or like it Claude will be like, okay, I've implemented your change or cursor, whatever it is. Like your agent will be like, I've implemented your change. And, you know, the tests that we've added or the tests that relate to the logic that we've touched are passing, but there might be other tests failing. And it's just like, nah, those are fine. Those are unrelated. So I'll just like only worry about the things I've touched.

00:32:15.080 --> 00:32:19.340
<v Dillon>I feel like when I've been using it recently, like it'll make all the changes I want.

00:32:20.180 --> 00:32:22.080
<v Dillon>And then it'll just start detecting all these issues.

00:32:22.980 --> 00:32:24.380
<v Dillon>And I'm like, dude, just wait a second.

00:32:24.620 --> 00:32:26.960
<v Dillon>Like, let me like test this first.

00:32:27.140 --> 00:32:29.860
<v Dillon>It'll just start fixing all kinds of random stuff that's not even related.

00:32:30.960 --> 00:32:32.000
<v Dillon>So I'm having the other problem.

00:32:33.280 --> 00:32:33.660
<v Dillon>The opposite.

00:32:34.600 --> 00:32:36.640
<v Scott>One of it's, that's interesting.

00:32:37.040 --> 00:32:39.560
<v Scott>Do you guys have like Claude.md files?

00:32:39.920 --> 00:32:40.140
<v Dillon>Yeah.

00:32:41.240 --> 00:32:44.960
<v Scott>- Or like, do you have Claude write your Claude.md file?

00:32:45.559 --> 00:32:48.660
<v Matt>- I've had it, so this is another interesting sort of tangent.

00:32:48.880 --> 00:32:51.000
<v Matt>Like I have like a PR that's been sitting

00:32:51.080 --> 00:32:53.880
<v Matt>for a while at work of like, I've had it try to like

00:32:54.160 --> 00:32:55.600
<v Matt>initialize its own Claude.md file.

00:32:55.620 --> 00:32:56.760
<v Matt>And we're getting like a lot of sort of

00:32:56.960 --> 00:32:58.200
<v Matt>iterative feedback on that PR.

00:32:59.920 --> 00:33:00.540
<v Matt>But it's--

00:33:00.620 --> 00:33:00.980
<v Scott>- No.

00:33:01.940 --> 00:33:02.220
<v Scott>- No.

00:33:02.320 --> 00:33:03.840
<v Scott>- It's supposed to write its own instructions

00:33:04.060 --> 00:33:05.840
<v Scott>and you're supposed to tell it to change the,

00:33:06.120 --> 00:33:06.660
<v Scott>update the instructions.

00:33:06.760 --> 00:33:08.580
<v Scott>You're not supposed to manually edit it.

00:33:08.760 --> 00:33:09.400
<v Matt>- Well, you can.

00:33:14.039 --> 00:33:21.200
<v Matt>like yes the default path isn't that you need to manually edit it but

00:33:14.039 --> 00:33:21.200
<v Scott>sure

00:33:14.039 --> 00:33:21.200
<v Matt>you can

00:33:14.039 --> 00:33:21.200
<v Scott>sure it can

00:33:21.500 --> 00:33:26.920
<v Scott>make i i had to read a couple articles about this maybe i can find them um but like it can you can

00:33:27.060 --> 00:33:35.279
<v Scott>make manual updates sure but in reality you're supposed to or it's recommended by um anthropic

00:33:35.600 --> 00:33:41.280
<v Scott>that you let it write them and then tell it to update them and then constantly over time tell it

00:33:41.400 --> 00:33:49.920
<v Scott>to um refine

00:33:41.400 --> 00:33:49.920
<v Matt>i think yes but at least in my experience on this um the the pr at work that

00:33:49.920 --> 00:33:55.560
<v Matt>i'm working on it's like it hallucinated a ton of stuff it like found so we have a it's not like

00:33:56.300 --> 00:34:01.519
<v Matt>super complex but we have like a relatively decent sized monorepo for managing this internal tool

00:34:02.040 --> 00:34:06.900
<v Matt>and it just like finds a folder called like um i don't know something visualization and it's like

00:34:06.980 --> 00:34:11.120
<v Matt>oh this must be a internal ui to visualize the internal state of the cli and it's like no that's

00:34:11.179 --> 00:34:15.879
<v Matt>actually not at all what it does it's like okay maybe we poorly named that package and or the

00:34:15.940 --> 00:34:20.679
<v Matt>package the package also didn't have a readme so it didn't like couldn't infer from that and so it

00:34:20.679 --> 00:34:26.200
<v Matt>just like tries to um it just tries to like make up something in the Claude.md file so that's why we

00:34:26.500 --> 00:34:30.200
<v Matt>had to like go back and forth and like iterate and like try to figure out the right thing and also

00:34:30.220 --> 00:34:36.179
<v Matt>like it pulls some commands to run for example for like internal development on the project but then

00:34:36.760 --> 00:34:41.280
<v Matt>it's like pulling ones it's like obviously it's pulling ones that exist in our package.json but

00:34:41.360 --> 00:34:44.720
<v Matt>like some of them it's like that's not exactly what it does or not exactly how it's intended to

00:34:44.720 --> 00:34:49.280
<v Matt>be used and so we need to like go in and tweak it to to be more accurate

00:34:44.720 --> 00:34:49.280
<v Scott>all right i have more

00:34:49.530 --> 00:34:57.320
<v Scott>questions so do you only have is this the only clodmd file this has

00:34:49.530 --> 00:34:57.320
<v Matt>yes

00:34:49.530 --> 00:34:57.320
<v Scott>okay so then you should

00:34:57.340 --> 00:35:02.260
<v Scott>just yeet the Claude.md file and update it over time. I think trying to perfect the perfect clod file

00:35:02.840 --> 00:35:08.600
<v Scott>is not going to solve the problem. And it's hurting now more than it's helping. So that's

00:35:09.140 --> 00:35:13.440
<v Scott>my first take on this is like, yeah, sure. It might be missing stuff, but let's get it out there.

00:35:13.520 --> 00:35:19.540
<v Scott>We have nothing out there. And it's hurting more now. So there's that. But I guess I asked this

00:35:19.680 --> 00:35:25.280
<v Scott>question because that's probably why you're seeing it do a lot of things that you didn't ask it to do.

00:35:25.360 --> 00:35:32.020
<v Scott>it has no instruction um or in a in that example because i'm actually experiencing like the opposite

00:35:32.270 --> 00:35:39.340
<v Scott>problem where we have so many Claude.md files that like it just is just any types typescript all the

00:35:39.480 --> 00:35:42.940
<v Scott>time even though it's supposed to be like a typescript wizard that's like one example

00:35:43.470 --> 00:35:48.760
<v Scott>um so i'm like always fixing types with it i think it's actually improving with upgrades to be honest

00:35:49.200 --> 00:35:55.900
<v Scott>but like i i see like different issues or like still sometimes it over engineers and i have to

00:35:55.900 --> 00:36:01.460
<v Scott>be like okay we don't need to do that like we can take the temperature down a little bit let's think

00:36:01.640 --> 00:36:08.460
<v Scott>about the rules of react and and how we can like simplify this um but uh no i would just like

00:36:09.220 --> 00:36:14.160
<v Scott>i would push for more iterative approach on that like yeah it might be missing stuff but like

00:36:14.480 --> 00:36:15.740
<v Scott>it's completely missing.

00:36:16.820 --> 00:36:19.580
<v Scott>So let's add the missing things as we go.

00:36:19.800 --> 00:36:21.220
<v Scott>This is code.

00:36:21.360 --> 00:36:22.100
<v Scott>This is iterative.

00:36:23.340 --> 00:36:26.300
<v Matt>Yeah, I think maybe getting a little bit back

00:36:26.380 --> 00:36:27.580
<v Matt>to what I was talking about as well,

00:36:27.740 --> 00:36:28.520
<v Matt>but I don't know, Dillon,

00:36:28.620 --> 00:36:30.340
<v Matt>if you had something on that point.

00:36:30.640 --> 00:36:32.780
<v Dillon>Just going to say, Matt's just holding AI wrong.

00:36:34.760 --> 00:36:35.700
<v Dillon>Yeah, that's true.

00:36:35.780 --> 00:36:36.820
<v Scott>Oh, Matt's not doing anything wrong.

00:36:37.660 --> 00:36:38.580
<v Scott>Matt's not doing anything wrong.

00:36:39.220 --> 00:36:40.920
<v Scott>It sounds like this is like an at work thing

00:36:41.200 --> 00:36:42.740
<v Scott>where everyone wants an opinion on

00:36:42.860 --> 00:36:43.860
<v Scott>what's in the Claude.md file.

00:36:44.000 --> 00:36:44.260
<v Matt>Yeah.

00:36:46.760 --> 00:36:46.860
<v Matt>Yeah.

00:36:47.260 --> 00:36:49.280
<v Matt>I think the other thing I've noticed with,

00:36:49.960 --> 00:36:51.660
<v Matt>and this is like going all the way back to our cursor,

00:36:52.619 --> 00:36:56.500
<v Matt>like cursor and composer usage is like last night,

00:36:57.040 --> 00:37:01.040
<v Matt>Claude, I feel like does pretty well of like handling type script in my

00:37:01.240 --> 00:37:02.820
<v Matt>experience on this side project, at least.

00:37:03.300 --> 00:37:05.640
<v Matt>Whereas cursor was just doing a ton of like, it's like, oh,

00:37:05.700 --> 00:37:06.200
<v Matt>there's a type error.

00:37:06.280 --> 00:37:09.380
<v Matt>So I'm just going to do like foo equals bar as any,

00:37:09.860 --> 00:37:10.880
<v Matt>and then like call it fix.

00:37:11.160 --> 00:37:13.220
<v Matt>And it's like, that's not, that's not fixed.

00:37:15.160 --> 00:37:19.480
<v Matt>and so i had to like it took me a bit of hand holding with with composer to like go through and

00:37:20.480 --> 00:37:26.220
<v Matt>and like actually you know remove as in ease if possible and it's like use better typecasting use

00:37:26.800 --> 00:37:30.720
<v Matt>actual types or like um you know figure out why the types are wrong and things like that

00:37:31.470 --> 00:37:36.460
<v Scott>am i allowed to continue talking about claude a little bit yeah

00:37:31.470 --> 00:37:36.460
<v Dillon>no

00:37:31.470 --> 00:37:36.460
<v Scott>like we because we're going

00:37:36.400 --> 00:37:44.960
<v Scott>a little back so do you guys use um yeah okay okay Dillon is kind of bringing it up here but

00:37:44.960 --> 00:37:49.300
<v Scott>do you guys use when you use claude matt do you use like planning mode and do you use

00:37:50.200 --> 00:37:56.380
<v Scott>um like the think modes like think harder and ultra think have you used any of that i ultra

00:37:56.480 --> 00:38:00.740
<v Scott>think every command

00:37:56.480 --> 00:38:00.740
<v Matt>yeah yeah i reach for ultrathink a lot i don't i don't necessarily opt into

00:38:00.740 --> 00:38:06.360
<v Matt>the plan mode or not all that often i think i'm always just in the i guess the sonnet 4.5 model

00:38:06.380 --> 00:38:10.540
<v Matt>Um, oh yeah, Dillon, this might not be a thing that you realize, but there's this, there's

00:38:10.540 --> 00:38:12.240
<v Matt>these keywords that Claude hooks into.

00:38:13.080 --> 00:38:17.580
<v Matt>I don't even if it's Claude or if it's like the underlying model that it hooks into to

00:38:17.580 --> 00:38:19.540
<v Matt>like opt into more thinking tokens.

00:38:20.160 --> 00:38:25.740
<v Scott>I told, I told Luke Reisch another name drop about this and he, he, he was like "ultrathink

00:38:25.940 --> 00:38:28.580
<v Scott>what the *bleep*?" or LOL or something.

00:38:28.600 --> 00:38:34.460
<v Scott>But yeah, there's multiple modes that it picks up on these keywords and it will take more

00:38:34.720 --> 00:38:35.360
<v Scott>time to reason.

00:38:35.520 --> 00:38:46.520
<v Dillon>I feel like these tools are just like building in all these extra little add-ons because every time you use one of these, it's like I'm opting into spending just a little bit more money.

00:38:47.360 --> 00:38:50.220
<v Dillon>And maybe I'm just one of the negative things that I missed.

00:38:50.740 --> 00:38:54.860
<v Scott>So the cool thing to do now is like, I'll ask, I'll, I'll ask it a prompt.

00:38:55.040 --> 00:38:58.600
<v Scott>And if it doesn't have enough context, it'll give me a series of questions about the prompt.

00:38:59.020 --> 00:39:00.320
<v Scott>And I'm like, wow, this is like CLI.

00:39:00.420 --> 00:39:02.800
<v Matt>So I think that's, I think that's planning mode in action.

00:39:04.200 --> 00:39:33.900
<v Scott>No, it's not always planning mode. Like, yes, I do planning mode, but it's like planning mode used to just be a conversation, but now it does. But also, like, I would actually recommend you almost do everything in planning mode first, you will get a better, like, this is the workflow I've gone through, you get better results. And like, I literally have a conversation. So one of the, this is something I wanted to get into, and I'll be quick about it. But basically, I try to unbiasedly tell plan mode, like, hey, like, I want to do this thing. Like, what do you think?

00:39:34.200 --> 00:39:35.180
<v Scott>I have my plan.

00:39:35.520 --> 00:39:36.920
<v Scott>And then once it gives me its plan,

00:39:37.400 --> 00:39:39.540
<v Scott>I start having conversations about those two plans.

00:39:39.900 --> 00:39:42.420
<v Scott>Because if you give it any slight inclination

00:39:42.660 --> 00:39:44.800
<v Scott>that you wanna do your plan,

00:39:45.260 --> 00:39:46.080
<v Scott>it'll just run with it.

00:39:46.160 --> 00:39:47.160
<v Scott>But yeah, yeah, yeah, let's do this.

00:39:47.480 --> 00:39:49.160
<v Scott>So try to use,

00:39:51.680 --> 00:39:54.000
<v Scott>try to be dumb with it first,

00:39:54.480 --> 00:39:54.980
<v Scott>get some plan,

00:39:55.440 --> 00:39:56.480
<v Scott>look at the pros and cons of yours,

00:39:56.760 --> 00:39:58.080
<v Scott>and then have a conversation about it,

00:39:58.340 --> 00:39:59.180
<v Scott>and then tell it to execute.

00:39:59.400 --> 00:40:00.940
<v Scott>You'll always end up with something better.

00:40:01.200 --> 00:40:03.780
<v Scott>And I think that's why I like Claude Code so much.

00:40:05.180 --> 00:40:08.640
<v Matt>Yeah, I think I haven't really been using the planning mode that much.

00:40:10.700 --> 00:40:21.120
<v Matt>But there are some times where it's like, or I think I just generally sort of put this in my prompts of like, think about it first and then come back, like, ask me like an opinion on approaches.

00:40:21.640 --> 00:40:29.640
<v Matt>So it's like, I have this feature I want to implement, you know, think about a few different ways to approach it and ask me like, like present those options to me.

00:40:29.640 --> 00:40:31.880
<v Matt>And then I'll basically tell it which of the options to go down.

00:40:32.640 --> 00:40:40.940
<v Matt>But yeah, for Dillon, because you didn't realize or maybe haven't experienced social think, it's pretty cool now that the Claude will like highlight it or like give you this rainbow.

00:40:41.350 --> 00:40:44.700
<v Matt>I shared a screenshot in our chat, but maybe we'll put it in the show notes.

00:40:45.480 --> 00:40:52.580
<v Dillon>My take on some of this stuff is just giving engineers easy ways to waste money.

00:40:53.040 --> 00:40:56.280
<v Dillon>But that's kind of my take on Cursor 2.0, actually.

00:40:56.350 --> 00:40:57.560
<v Dillon>And I never really touched on that earlier.

00:40:58.200 --> 00:41:04.580
<v Dillon>There's all these ways to just run more and more prompts all at once.

00:41:05.950 --> 00:41:13.640
<v Dillon>Do you really need to run it 17 times to figure out how to make a button appear on the screen in a good way?

00:41:15.910 --> 00:41:21.560
<v Scott>Well, honestly, with the plan mode on Claude Code, I never have to tell it to do the same thing over again.

00:41:21.840 --> 00:41:25.800
<v Scott>Because it makes it clear what it's going to do ahead of time doesn't do it.

00:41:26.000 --> 00:41:28.920
<v Scott>And then if I can read it over review it and be like, oh, we need this and that.

00:41:29.350 --> 00:41:39.200
<v Scott>You know, it's honestly, like, I think the best feature, like that and UltraThink, like, I know it's costing somebody a lot of money, but it works.

00:41:39.720 --> 00:41:48.580
<v Matt>Well, like on the cost side, it's like, I think I was saying this earlier also, but like, I've been hitting my limits on Claude Code more frequently as I've been using it.

00:41:49.220 --> 00:41:54.740
<v Matt>And then this is also, we were talking about this a little bit before recording of like, maybe I actually am using it incorrectly.

00:41:55.360 --> 00:42:09.060
<v Matt>Like, I think I'm using it a lot where sometimes it's, like, very menial tasks, and it's just, like, easier to prompt it to do something than it is for me to sit down and write a script for it or, like, to do the meta prompt of, like, write a script for this to make this change.

00:42:10.120 --> 00:42:21.500
<v Matt>So, like, one example actually from last night is, like, it's been turning along on this side project code base for a bit, and it's been using const everywhere, and I kind of hate const.

00:42:21.700 --> 00:42:25.080
<v Matt>I have this hot take that const is not worth using.

00:42:25.650 --> 00:42:27.380
<v Matt>I always prefer let, which is--

00:42:27.770 --> 00:42:28.040
<v Matt>I don't know.

00:42:28.200 --> 00:42:29.200
<v Matt>Maybe we get into that.

00:42:32.859 --> 00:42:34.300
<v Matt>And so I just basically said, OK,

00:42:34.480 --> 00:42:36.820
<v Matt>go in and replace all the instances of const with let.

00:42:37.420 --> 00:42:39.680
<v Matt>And it does this, find and replace and stuff like that.

00:42:39.710 --> 00:42:41.440
<v Matt>But it burns through all the tokens that I have.

00:42:41.940 --> 00:42:45.020
<v Matt>And so it's like this isn't even running chats in parallel.

00:42:45.160 --> 00:42:46.520
<v Matt>This is just a single chat doing that.

00:42:46.620 --> 00:42:48.440
<v Matt>It's like I probably should have just had it write a script

00:42:48.920 --> 00:42:50.520
<v Matt>to do that, find and replace for me.

00:42:51.240 --> 00:42:53.360
<v Scott>I guess it's more because you're on a budget here.

00:42:53.540 --> 00:42:57.280
<v Scott>I have the luxury of just telling it to do everything.

00:42:57.820 --> 00:43:01.000
<v Scott>Although I get into this mode where I don't want it to do everything.

00:43:01.560 --> 00:43:02.780
<v Scott>I want to do some things here.

00:43:03.580 --> 00:43:04.540
<v Scott>Not just fix the types.

00:43:06.200 --> 00:43:10.200
<v Dillon>I think probably our first episode, I think we talked about AI.

00:43:11.560 --> 00:43:15.500
<v Dillon>And we talked about how we were going to stop using it for a week.

00:43:16.060 --> 00:43:17.280
<v Dillon>And then we report back.

00:43:18.960 --> 00:43:20.540
<v Dillon>It's been over a year.

00:43:21.200 --> 00:43:23.220
<v Dillon>and I think we all failed that challenge

00:43:25.320 --> 00:43:25.800
<v Matt>I mean

00:43:26.180 --> 00:43:27.700
<v Scott>okay so are we doing a new challenge

00:43:27.900 --> 00:43:29.400
<v Scott>here are we going to try to do that for once

00:43:30.000 --> 00:43:31.860
<v Scott>I'm going to get laid off if I do that

00:43:31.900 --> 00:43:33.520
<v Scott>I won't make it

00:43:33.840 --> 00:43:35.720
<v Matt>outside of work I definitely went through this

00:43:35.820 --> 00:43:37.620
<v Matt>period maybe within the past couple

00:43:37.780 --> 00:43:39.540
<v Matt>months of like where I just like wasn't working

00:43:39.580 --> 00:43:41.660
<v Matt>on side projects at all so that was kind of like

00:43:41.840 --> 00:43:43.340
<v Matt>not using AI in a sense

00:43:43.920 --> 00:43:45.660
<v Matt>but obviously in work I was using

00:43:46.120 --> 00:43:46.240
<v Matt>AI

00:43:47.600 --> 00:43:49.620
<v Dillon>have you been doing interviews lately

00:43:50.080 --> 00:43:50.580
<v Dillon>at work

00:43:52.040 --> 00:43:58.520
<v Matt>uh i've shadowed a few but um i haven't uh haven't done too many

00:43:52.040 --> 00:43:58.520
<v Dillon>like a its own episode but

00:43:59.130 --> 00:44:06.260
<v Dillon>um do you guys allow them to use like ai tools in the interview

00:43:59.130 --> 00:44:06.260
<v Matt>we don't currently which is really

00:44:06.460 --> 00:44:11.240
<v Matt>interesting because we are we we pride ourselves on being ai fluent like literally one of our

00:44:11.520 --> 00:44:14.580
<v Matt>criteria in our interviews is and it's not necessarily during the coding sessions but

00:44:14.640 --> 00:44:20.560
<v Matt>it's like a behavioral question we ask of like how ai fluent is the candidate uh like what ai

00:44:20.580 --> 00:44:24.800
<v Matt>are using what's their experience with it and so like if you don't use ai and you come in and do an

00:44:24.900 --> 00:44:29.400
<v Matt>interview and it's like and then you like answer that kind of poorly that maybe serves as like a

00:44:29.760 --> 00:44:37.380
<v Matt>yellow flag of sorts um and so it's but and yet and yet our coding sessions don't use ai or we're

00:44:37.380 --> 00:44:43.100
<v Matt>not allowed and candidates aren't allowed to use ai which is kind of oddly weird

00:44:37.380 --> 00:44:43.100
<v Dillon>we basically it start

00:44:43.100 --> 00:44:46.580
<v Dillon>the interview with like hey you're allowed to use these tools but you can't just like dump the

00:44:46.600 --> 00:44:51.440
<v Dillon>question into it and the problem get the answer and paste it like it's not an option

00:44:53.220 --> 00:44:58.620
<v Matt>you're just reach for ultrathink in your interview

00:44:53.220 --> 00:44:58.620
<v Scott>i've heard that uh companies are

00:44:58.760 --> 00:45:04.640
<v Scott>now giving interviews where they're making people use ai and then trying to get them to explain like

00:45:05.020 --> 00:45:10.140
<v Scott>not just put the exact answer in but like how could this actually be better which makes a lot

00:45:10.140 --> 00:45:15.460
<v Scott>of sense to me that that's starting to become a thing

00:45:10.140 --> 00:45:15.460
<v Matt>i haven't also experienced the case where

00:45:15.480 --> 00:45:21.440
<v Matt>it's like very clearly the the candidate is like cheating and like using ai like like you know the

00:45:21.720 --> 00:45:25.780
<v Matt>Cluely is like the popular example of this where it's like a piece of software that people can use

00:45:25.780 --> 00:45:31.240
<v Matt>to like basically like answer answer interview questions for them while being trying to like

00:45:31.540 --> 00:45:36.860
<v Matt>almost invisible to the person interviewing them um

00:45:31.540 --> 00:45:36.860
<v Dillon>i've been so skeptical on some of my recent

00:45:37.080 --> 00:45:42.599
<v Dillon>interviews where like they don't use ai but i'm like why are they coding top to bottom nobody

00:45:42.620 --> 00:45:49.380
<v Dillon>thinks like they'll just like input the solution and i'm just like yeah what

00:45:42.620 --> 00:45:49.380
<v Matt>line by line instead

00:45:49.400 --> 00:45:53.700
<v Matt>of like sort of like

00:45:49.400 --> 00:45:53.700
<v Matt>building

00:45:49.400 --> 00:45:53.700
<v Dillon>the instruction there's like three separate instructions but

00:45:53.820 --> 00:45:58.360
<v Dillon>and then they're like solving for all three at once and i'm like dude are you paying attention

00:45:59.300 --> 00:46:03.380
<v Dillon>like slow down sorry we can do a whole interviews episode

00:46:05.500 --> 00:46:11.020
<v Matt>yeah i think i mean i think it's been a long long long lasting topic idea for us to get back to is

00:46:11.020 --> 00:46:15.900
<v Matt>like ai in interviews um or maybe just interviews in general which i think is interesting yeah

00:46:11.020 --> 00:46:15.900
<v Dillon>i've

00:46:15.920 --> 00:46:22.700
<v Dillon>seen it like i'll prompt candidates that they can use ai if they want and i think some of them feel

00:46:22.780 --> 00:46:29.820
<v Dillon>like if they use it they're going to get docked for using it which is not maybe i'm not like

00:46:31.000 --> 00:46:35.760
<v Dillon>telling them or like giving them a good enough explanation for why they can use it and and

00:46:36.100 --> 00:46:40.040
<v Dillon>explain that they're not going to get docked but i feel like most of them sort of steer away from it

00:46:40.520 --> 00:46:48.580
<v Dillon>but then they end up using google which is ai so it's pretty funny

00:46:40.520 --> 00:46:48.580
<v Matt>all right do we have any

00:46:49.080 --> 00:46:54.300
<v Matt>further topics or do we want to wrap it up there we didn't really do a stand-up update today maybe

00:46:54.330 --> 00:47:01.220
<v Matt>we do a quick little end stand-up scott what's up with you

00:47:04.340 --> 00:47:10.680
<v Scott>didn't have enough time to prepare uh i mean tomorrow's halloween so now i've dated this

00:47:10.900 --> 00:47:16.640
<v Scott>podcast uh excited about that i get the trick-or-treaters this will be a third year that

00:47:17.120 --> 00:47:20.760
<v Scott>we usually don't get too many so i get all the leftover candy excited about that

00:47:21.640 --> 00:47:27.660
<v Scott>um are you had a flat tire

00:47:21.640 --> 00:47:27.660
<v Matt>are you a wait wait on the on the halloween thing are you a big candy

00:47:27.680 --> 00:47:36.040
<v Matt>person like a full-size candy bar person or are you a tiny candy person

00:47:27.680 --> 00:47:36.040
<v Scott>no, in today's economy to use a matt phrase

00:47:36.040 --> 00:47:43.320
<v Dillon>right um have you

00:47:36.040 --> 00:47:43.320
<v Scott>i mean i would love to be

00:47:36.040 --> 00:47:43.320
<v Dillon>tasted the candy that's like packed with seven other

00:47:43.500 --> 00:47:51.660
<v Dillon>candies it tastes terrible

00:47:43.500 --> 00:47:51.660
<v Matt>yes yes i noticed this yesterday yes that's 100 true

00:47:43.500 --> 00:47:51.660
<v Scott>what candy

00:47:51.660 --> 00:47:56.880
<v Scott>you guys talking about

00:47:51.660 --> 00:47:56.880
<v Matt>specifically cases like at least in my case it was like chocolate chocolate

00:47:56.900 --> 00:48:00.820
<v Matt>candy that's in a bag of like non-chocolate candy

00:47:56.900 --> 00:48:00.820
<v Dillon>it just like all the candy and it's just like

00:48:00.940 --> 00:48:06.240
<v Dillon>everything's like absorb into the other candies and then when you eat it it just tastes like

00:48:06.980 --> 00:48:12.040
<v Dillon>like the soda that you get if you mix like every soda together

00:48:06.980 --> 00:48:12.040
<v Matt>the graveyard soda or whatever it

00:48:12.040 --> 00:48:18.780
<v Dillon>was you guys called it

00:48:12.040 --> 00:48:18.780
<v Scott>we just got some like a assorted like um sour patch kids

00:48:19.460 --> 00:48:21.840
<v Scott>kind of thing so maybe that'll go over all right

00:48:24.559 --> 00:48:26.220
<v Scott>um yeah I got a flat tire yesterday

00:48:27.420 --> 00:48:28.220
<v Scott>not exciting

00:48:28.880 --> 00:48:30.340
<v Scott>repaired it yesterday

00:48:30.800 --> 00:48:31.260
<v Scott>it's all better

00:48:32.320 --> 00:48:33.920
<v Scott>so that really derailed my work

00:48:34.100 --> 00:48:36.060
<v Scott>so right now

00:48:36.420 --> 00:48:38.180
<v Scott>I'm under the gun and

00:48:38.620 --> 00:48:40.300
<v Scott>chatting with you guys isn't making it any better

00:48:40.760 --> 00:48:42.080
<v Dillon>speaking of flat tires

00:48:44.359 --> 00:48:45.560
<v Dillon>I bought this

00:48:46.240 --> 00:48:46.620
<v Dillon>wireless

00:48:48.299 --> 00:48:49.420
<v Dillon>battery operated

00:48:50.030 --> 00:48:51.800
<v Dillon>air pump for my car

00:48:52.280 --> 00:48:52.500
<v Matt>The compressor.

00:48:52.840 --> 00:48:52.940
<v Dillon>Yeah.

00:48:53.520 --> 00:48:53.940
<v Dillon>It's sick.

00:48:54.060 --> 00:48:54.700
<v Dillon>It has like a light.

00:48:55.220 --> 00:48:55.940
<v Scott>I got one of those.

00:48:56.940 --> 00:48:57.580
<v Dillon>You just tell it.

00:48:58.040 --> 00:49:01.120
<v Scott>It's not wireless, but

00:48:58.040 --> 00:49:01.120
<v Dillon>you tell it what pressure you want it to go to and just hit a button

00:49:01.280 --> 00:49:02.600
<v Dillon>and then it just like fills up and stops.

00:49:03.480 --> 00:49:03.960
<v Dillon>It's awesome.

00:49:05.160 --> 00:49:05.940
<v Scott>Oh, that's better than mine.

00:49:06.360 --> 00:49:06.820
<v Scott>Mine's old school.

00:49:08.280 --> 00:49:08.780
<v Dillon>But it's been good.

00:49:08.900 --> 00:49:13.060
<v Dillon>Like I'll just like check my tires every once in a while and then fill them back up.

00:49:13.180 --> 00:49:13.420
<v Dillon>It's great.

00:49:16.400 --> 00:49:17.840
<v Dillon>That's my standup update as well.

00:49:24.920 --> 00:49:27.920
<v Scott>i don't know if i was done but i guess i am now

00:49:24.920 --> 00:49:27.920
<v Matt>well yeah any other

00:49:28.500 --> 00:49:32.920
<v Matt>closing thoughts there scott on your stand-up update we saved for parking lot that's probably

00:49:38.480 --> 00:49:42.560
<v Scott>no no no that's enough i mean we talked about coffee so we're good

00:49:44.600 --> 00:49:48.800
<v Matt>Dillon what's your uh what's your stand-up update

00:49:44.600 --> 00:49:48.800
<v Dillon>i don't know i'm just i'm taking two days off of

00:49:48.720 --> 00:49:52.900
<v Dillon>work everyone's like what are you doing and i'm like not much nothing

00:49:48.720 --> 00:49:52.900
<v Matt>arc raiders

00:49:48.720 --> 00:49:52.900
<v Dillon>yeah i'm gonna

00:49:52.900 --> 00:49:58.600
<v Dillon>try to play this arc raiders game i in my head i'm gonna play it for like six hours but what's

00:49:58.820 --> 00:50:03.900
<v Dillon>actually gonna happen is i'm gonna play it for like 45 minutes get mad and go like do something else

00:50:06.260 --> 00:50:11.980
<v Matt>i feel like also for those don't know arc raiders is like a uh infill extraction shooter so like

00:50:12.080 --> 00:50:17.740
<v Matt>you lose like if you lose well actually i don't know how it exactly works but for other games in

00:50:17.720 --> 00:50:23.180
<v Matt>a similar genre like if you lose all your backed up stuff like saved guns and loot and whatnot then

00:50:23.300 --> 00:50:28.160
<v Matt>it's like you kind of run out of reasons to play maybe like you you i feel like you slowly get

00:50:28.240 --> 00:50:32.760
<v Matt>tired of like going in empty and like trying to extract the stuff

00:50:28.240 --> 00:50:32.760
<v Dillon>yeah

00:50:28.240 --> 00:50:32.760
<v Matt>um so i don't know i'll

00:50:32.760 --> 00:50:38.320
<v Matt>be curious if you feel the same as well

00:50:32.760 --> 00:50:38.320
<v Dillon>yeah i think there's this fear which makes it more

00:50:38.500 --> 00:50:43.760
<v Dillon>interesting and if you do lose everything there's opportunities in the game to like start with

00:50:44.400 --> 00:50:51.640
<v Dillon>like barely anything and sort of slowly work your way back up for for no value

00:50:44.400 --> 00:50:51.640
<v Matt>yeah

00:50:44.400 --> 00:50:51.640
<v Dillon>so it's like an

00:50:51.880 --> 00:50:59.540
<v Dillon>interesting um type of game so i've know i've tried to play games in this this type like um

00:50:59.880 --> 00:51:08.220
<v Dillon>escape from tarkov but it's just that game is insane and it impossible to get into

00:50:59.880 --> 00:51:08.220
<v Matt>yeah we at

00:51:08.220 --> 00:51:12.800
<v Matt>least scott and i have played um dmz in the past like the call of duty version of it and it was

00:51:12.760 --> 00:51:14.720
<v Matt>pretty good. It still has a pretty vibrant community,

00:51:14.790 --> 00:51:16.120
<v Matt>even though they've basically shut it down.

00:51:18.040 --> 00:51:18.400
<v Matt>And then

00:51:19.060 --> 00:51:20.780
<v Matt>recently I played the Delta Force version of

00:51:20.860 --> 00:51:22.700
<v Matt>the Extraction Shooter, which is kind

00:51:22.750 --> 00:51:24.600
<v Matt>of interesting. But I feel like that audience,

00:51:24.800 --> 00:51:26.860
<v Matt>there was a group of people that moved over to that

00:51:27.020 --> 00:51:28.600
<v Matt>from DMZ and played it

00:51:28.900 --> 00:51:30.400
<v Matt>pretty frequently. It's not as

00:51:30.980 --> 00:51:32.760
<v Matt>tough as Escape from Tarkov

00:51:33.339 --> 00:51:34.560
<v Matt>or the other ones, but

00:51:36.480 --> 00:51:38.540
<v Matt>I feel like it's slowly burnt out also.

00:51:38.860 --> 00:51:40.360
<v Matt>Or a lot of people are probably shifting from that to

00:51:40.650 --> 00:51:42.720
<v Matt>Arc Raiders. Anyway, we're not a game

00:51:42.760 --> 00:51:42.920
<v Matt>podcast.

00:51:45.510 --> 00:51:46.560
<v Matt>Now we are. We're rebranded.

00:51:48.080 --> 00:51:48.880
<v Dillon>The sound

00:51:49.200 --> 00:51:50.820
<v Dillon>design is amazing. The visuals

00:51:51.040 --> 00:51:51.860
<v Dillon>are really, really good.

00:51:52.920 --> 00:51:54.980
<v Dillon>And then it's not made by a massive

00:51:55.320 --> 00:51:57.020
<v Dillon>AAA studio either. It's the company

00:51:57.020 --> 00:51:58.960
<v Dillon>that made the finals, which is

00:51:58.990 --> 00:51:59.800
<v Dillon>actually a pretty good game.

00:52:02.100 --> 00:52:02.960
<v Matt>I didn't know that.

00:52:03.180 --> 00:52:05.220
<v Dillon>And it doesn't cost $70.

00:52:05.480 --> 00:52:06.920
<v Dillon>It's only $40, which is kind of

00:52:07.040 --> 00:52:07.200
<v Dillon>crazy.

00:52:08.980 --> 00:52:10.720
<v Dillon>There's a lot of other cool things going for it.

00:52:13.480 --> 00:52:20.060
<v Matt>cool so your whole stand-up update is just Arc Raiders

00:52:13.480 --> 00:52:20.060
<v Dillon>pretty much i mean i'm still my i can go

00:52:20.420 --> 00:52:23.840
<v Dillon>to the last episode i'm still staying consistent with that workout that i said i was doing

00:52:25.740 --> 00:52:34.240
<v Dillon>nice on the third week in a row with no no skips

00:52:25.740 --> 00:52:34.240
<v Matt>that's great i've been i i was trying to get back

00:52:34.300 --> 00:52:35.900
<v Matt>into my daily walk routine.

00:52:36.480 --> 00:52:37.660
<v Matt>I feel like sometimes it's like,

00:52:38.880 --> 00:52:40.260
<v Matt>well, as of late, one, it's

00:52:40.480 --> 00:52:42.140
<v Matt>dark in the morning, so it's really hard to convince

00:52:42.340 --> 00:52:44.240
<v Matt>myself to go outside and go for my walk in the

00:52:44.300 --> 00:52:46.180
<v Matt>morning. But two, it's also getting a lot

00:52:46.360 --> 00:52:48.260
<v Matt>colder. So it's like, now I'm wearing a sweater

00:52:48.580 --> 00:52:49.820
<v Matt>and pants, and

00:52:50.160 --> 00:52:52.180
<v Matt>it's just not the vibe

00:52:52.180 --> 00:52:52.780
<v Matt>to go for a walk.

00:52:54.560 --> 00:52:55.660
<v Matt>I need to get back into it.

00:52:56.340 --> 00:52:57.100
<v Dillon>What's your update, Matt?

00:52:59.280 --> 00:52:59.740
<v Matt>Let's see.

00:53:00.580 --> 00:53:02.140
<v Matt>Yeah, so I was in Connecticut this week for a

00:53:02.220 --> 00:53:04.260
<v Matt>few days. We were doing kind of like a walkthrough of our

00:53:04.880 --> 00:53:06.320
<v Matt>location for our wedding.

00:53:07.540 --> 00:53:08.080
<v Matt>It was pretty neat.

00:53:10.320 --> 00:53:10.980
<v Matt>I don't know what else.

00:53:11.180 --> 00:53:12.900
<v Matt>I'm burning through tokens in

00:53:13.020 --> 00:53:14.760
<v Matt>Claude. I've been

00:53:15.440 --> 00:53:16.900
<v Matt>sort of kind of

00:53:17.020 --> 00:53:18.880
<v Matt>thinking about upgrading to either the $100

00:53:18.880 --> 00:53:20.840
<v Matt>or $200 a month plan for Claude Code for

00:53:20.880 --> 00:53:22.680
<v Matt>my personal usage, and it's just like, that feels

00:53:23.160 --> 00:53:24.000
<v Matt>insane to pay for.

00:53:25.160 --> 00:53:25.760
<v Matt>That's a lot of money.

00:53:30.920 --> 00:53:32.720
<v Matt>Battlefield 6 I've been playing a ton of

00:53:33.280 --> 00:53:34.460
<v Matt>over the past couple weeks.

00:53:35.400 --> 00:53:36.740
<v Matt>Their Season 1 update came out on Tuesday.

00:53:36.860 --> 00:53:37.900
<v Matt>I haven't been able to play it yet.

00:53:38.300 --> 00:53:40.300
<v Matt>Their Battle Royale, I haven't been able to play it yet.

00:53:40.320 --> 00:53:42.720
<v Matt>So I'm hoping to dig into those this weekend.

00:53:43.680 --> 00:53:45.520
<v Dillon>Yeah, we should all jump into that

00:53:45.920 --> 00:53:48.440
<v Dillon>since I feel like the only time I've played any games with you guys

00:53:48.520 --> 00:53:51.520
<v Dillon>is through the Call of Duty Battle Royale.

00:53:53.100 --> 00:53:53.300
<v Matt>Yeah.

00:53:54.400 --> 00:53:56.540
<v Matt>I've been trying to convince Scott to get this game.

00:53:57.440 --> 00:53:58.260
<v Matt>He hates it.

00:53:58.340 --> 00:53:59.560
<v Matt>He played the alpha or the beta.

00:54:00.140 --> 00:54:00.780
<v Matt>He hated it.

00:54:01.080 --> 00:54:02.940
<v Matt>But I think it's worth playing.

00:54:03.060 --> 00:54:03.880
<v Scott>It wasn't fun.

00:54:04.100 --> 00:54:05.920
<v Matt>Well, we should at least try the Battle Royale.

00:54:06.100 --> 00:54:08.920
<v Matt>It should be free versus the main game is paid.

00:54:09.480 --> 00:54:09.940
<v Scott>That's fine.

00:54:10.140 --> 00:54:12.040
<v Matt>Yeah, we should get back into it.

00:54:12.140 --> 00:54:15.080
<v Matt>We have a separate Discord server that we've used for a number of years

00:54:15.799 --> 00:54:17.680
<v Matt>for organizing, playing COD and whatnot.

00:54:18.120 --> 00:54:19.400
<v Matt>But we should try to use that more.

00:54:22.520 --> 00:54:23.760
<v Matt>Yeah, I think that's about it.

00:54:24.260 --> 00:54:25.260
<v Dillon>Sweet. Thanks.

00:54:25.800 --> 00:54:26.620
<v Matt>Should we wrap it there?

00:54:26.680 --> 00:54:28.760
<v Dillon>Yeah, good luck in your presentation at work, Matt.

00:54:30.380 --> 00:54:31.420
<v Matt>Thanks. Yeah, I need to

00:54:32.380 --> 00:54:34.500
<v Matt>prep for it. I wrote a script for it

00:54:34.960 --> 00:54:36.460
<v Matt>the other day, and it's like, maybe this is

00:54:36.620 --> 00:54:38.380
<v Matt>overkill, but it's going to help me stay on track

00:54:38.580 --> 00:54:40.160
<v Matt>hopefully. I have to screen share

00:54:40.560 --> 00:54:42.580
<v Matt>some stuff, and hopefully it'll be good.

00:54:43.200 --> 00:54:44.480
<v Matt>It's relatively lightweight. It's like

00:54:44.480 --> 00:54:46.340
<v Matt>a show and tell that we do, and so it's like, I have

00:54:46.440 --> 00:54:48.540
<v Matt>five minutes or something to show it all.

00:54:49.420 --> 00:54:50.560
<v Dillon>For me, it's like, how many

00:54:50.760 --> 00:54:52.620
<v Dillon>people is it in front of? It always makes

00:54:52.640 --> 00:54:54.000
<v Dillon>it harder, for whatever reason.

00:54:55.099 --> 00:54:56.360
<v Matt>Yeah. This one, I think it's

00:54:56.580 --> 00:54:58.420
<v Matt>maybe like 30 to 50, so it's not that

00:54:58.540 --> 00:55:00.340
<v Matt>bad, but...

00:55:00.360 --> 00:55:01.360
<v Matt>More than just a team.

00:55:03.600 --> 00:55:04.280
<v Dillon>You're going to crush it.

00:55:04.340 --> 00:55:04.760
<v Dillon>Cool.

00:55:07.100 --> 00:55:07.240
<v Matt>Cool.

00:55:07.680 --> 00:55:07.920
<v Matt>All right.

00:55:08.300 --> 00:55:08.420
<v Matt>Yeah.

00:55:08.600 --> 00:55:09.520
<v Matt>Thanks everyone for tuning in.

00:55:10.620 --> 00:55:11.260
<v Matt>If you enjoyed this episode,

00:55:11.420 --> 00:55:12.060
<v Matt>leave us a review,

00:55:12.620 --> 00:55:13.260
<v Matt>share it with some people.

00:55:14.880 --> 00:55:16.000
<v Matt>I haven't checked back on our stats,

00:55:16.080 --> 00:55:16.660
<v Matt>our listener stats.

00:55:16.700 --> 00:55:16.880
<v Matt>You know,

00:55:16.980 --> 00:55:17.280
<v Matt>maybe we've,

00:55:17.820 --> 00:55:19.520
<v Matt>I think we've probably fallen off in Romania,

00:55:19.780 --> 00:55:20.960
<v Matt>but maybe Lithuania,

00:55:21.180 --> 00:55:22.740
<v Matt>maybe we're jumping back up in Lithuania.

00:55:23.020 --> 00:55:23.300
<v Matt>We'll see.

00:55:25.000 --> 00:55:25.160
<v Matt>But yeah,

00:55:25.160 --> 00:55:25.520
<v Matt>we can't,

00:55:25.620 --> 00:55:28.220
<v Matt>we can't improve without you guys providing feedback and reviews.

00:55:29.120 --> 00:55:29.840
<v Matt>So let us know.

00:55:30.180 --> 00:55:30.820
<v Matt>Sound off on our Discord.

00:55:32.780 --> 00:55:32.860
<v Matt>Yeah.

00:55:33.560 --> 00:55:34.440
<v Matt>Otherwise, thanks for tuning in.

00:55:34.800 --> 00:55:37.200
<v Matt>Catch you next time.

00:55:38.700 --> 00:55:38.960
<v Dillon>Later.

00:55:39.540 --> 00:55:39.660
<v Scott>Later.

00:55:40.440 --> 00:55:40.600
<v Matt>Peace.

