KOPYA NG SALIN 🔗
WEBVTT
00:00:00.160 --> 00:00:03.439
In the age of AI, everyone wants to tighten the feedback.
00:00:03.520 --> 00:00:11.759
Like being able to adapt, be flexible, and be willing to change my opinion, instead of waiting weeks to get user feedback, we can just ship it and see what happens.
00:00:11.919 --> 00:00:16.719
You know, the price you pay for not experimenting is like you don't actually know what's possible.
00:00:23.839 --> 00:00:25.760
You're listening to We Built What?
00:00:25.920 --> 00:00:29.120
The podcast for engineering leaders building in the agencera.
00:00:29.440 --> 00:00:35.119
I'm Emma Webb from Augment, and I'm so pleased to be here today with Weiwei Wu, CEO of Momentic.
00:00:35.280 --> 00:00:36.479
Thank you so much for joining us.
00:00:36.719 --> 00:00:37.520
Thanks for having me.
00:00:37.679 --> 00:00:41.039
So, Weiwei, you just recently closed your series A.
00:00:41.200 --> 00:00:42.240
Congratulations.
00:00:42.479 --> 00:00:45.600
Can you tell me a little bit about the thesis behind Momentic?
00:00:45.679 --> 00:00:46.159
What are you building?
00:00:46.479 --> 00:00:46.799
Yeah, yeah.
00:00:47.039 --> 00:00:51.119
Momentic is the AI verification layer for software.
00:00:51.439 --> 00:00:57.600
We are the guardrails to make sure your software actually works the way you intend it to, you know, for your end user.
00:00:57.679 --> 00:01:04.719
So, you know, powering some of our customers like Notion, like Built, Quora, Webflow, Xero and more.
00:01:05.040 --> 00:01:11.120
So this is such an important problem right now, and I'm really curious why do we need a standalone company to do it?
00:01:11.519 --> 00:01:29.359
Yeah, I think one of the things that's really interesting is as we see teams adopt more and more AI tools, is they're shifting towards plain English specs for how they talk to their AI coding agent for coding.
00:01:29.680 --> 00:01:42.879
We want to make that spec also the way you would verify it, you know, along with all those assess criteria, all the edge cases, you know, just the way you would describe how you would build it, that's exactly how you would verify the AI agents' work as well.
00:01:43.200 --> 00:01:47.439
So the spec is in the verification step as well, it's not just the design stage.
00:01:47.840 --> 00:01:48.239
Exactly.
00:01:48.319 --> 00:01:56.079
So like the spec is kind of how we think of it as the source of truth for how your product or feature is supposed to behave.
00:01:56.319 --> 00:02:08.400
So if I'm thinking about kind of how we build software in the agentic era, one of the things I think about or that people talk about is you really don't want the same agent that wrote the code to also be verifying it.
00:02:08.479 --> 00:02:10.639
Is that part of why Momentic as well?
00:02:10.879 --> 00:02:11.439
Yeah, yeah.
00:02:11.520 --> 00:02:18.000
I think I am tasking all of my little, you know, AI robots to write code for me.
00:02:18.159 --> 00:02:22.240
Um, you know, we have
Load full transcript
them all hooked up in Slack, for example, internally at Momentic.
00:02:22.400 --> 00:02:27.680
But at the same time, I also want proof that it did its work correctly.
00:02:27.840 --> 00:02:32.800
And, you know, this goes beyond just static code review, linters, you know, unit tests and things like that.
00:02:32.960 --> 00:02:37.280
I actually want to see it work from our user's perspective.
00:02:37.439 --> 00:02:45.919
And I think it's important that it's a separate tool that's actually verifying the work, but it also works well with the AI that's building the feature in the first place.
00:02:46.000 --> 00:02:49.360
You know, I think it's a you know an ecosystem that kind of grows together.
00:02:49.680 --> 00:02:50.879
Yeah, it's so interesting.
00:02:51.039 --> 00:02:55.680
I think there's this really big conversation right now about what it means to be AI native.
00:02:55.840 --> 00:02:57.919
What does that look like for you at Momentic?
00:02:58.000 --> 00:02:59.439
How are you how is your team building?
00:02:59.599 --> 00:03:02.159
Can you tell me a little bit about how do we build now?
00:03:02.400 --> 00:03:04.000
Yeah, yeah, that's a that's a good question.
00:03:04.080 --> 00:03:13.199
You know, when I when I first started coding uh in in high school, you know, we were using you know Notepad Plus Plus, or like I think in college I was using like Sublime Text.
00:03:13.280 --> 00:03:18.319
That was like before, you know, Cursor or any other AI coding tool existed.
00:03:18.560 --> 00:03:21.039
I would not consider myself AI native.
00:03:21.280 --> 00:03:23.520
AI native is like someone who grew up with AI, you know.
00:03:23.680 --> 00:03:27.919
I think the way we approach using and adopting AI is also quite different as well.
00:03:28.080 --> 00:03:32.479
But I think for me, like I would consider myself very flexible.
00:03:32.639 --> 00:03:43.599
It's like, you know, especially as the the founder of an AI native company, you know, being able to adapt, be flexible, and kind of be willing to change my opinion about like what's possible.
00:03:44.000 --> 00:03:50.400
It's really interesting to me because basically the way you describe it is there's kind of a before and after.
00:03:50.560 --> 00:03:58.479
And in my mind, if we're thinking AI native is someone who's always built that way, gosh, what a small cohort of people that is, right?
00:03:58.800 --> 00:03:59.599
I I agree.
00:03:59.680 --> 00:04:00.159
I agree.
00:04:00.319 --> 00:04:07.439
I think having experience in a non-AI native uh is is important for context setting.
00:04:07.520 --> 00:04:12.960
You know, instead of me prompting in my editor, um, you know, I used to have to type things out by hand.
00:04:13.039 --> 00:04:14.000
You know, that's insane.
00:04:14.159 --> 00:04:19.839
You know, it was just you know actual code autocomplete, not just you know, tab completes and things like that.
00:04:20.720 --> 00:04:21.680
In my day.
00:04:23.519 --> 00:04:30.959
Yeah, but I'm like picturing you around the fire in the future, you know, telling your grandkids in my day, we coded by hand.
00:04:31.199 --> 00:04:34.639
You know, like in the future, I imagine you know, I have an electrode attached to my temple.
00:04:34.879 --> 00:04:37.199
I'm just thinking the you know software into existence.
00:04:37.680 --> 00:04:43.920
Yeah, it's become a bit of a problem because I build so many apps now that nobody like I don't have nobody wants them.
00:04:44.079 --> 00:04:44.639
You know what I mean?
00:04:44.720 --> 00:04:46.240
And I'm like, look at this cool thing I built.
00:04:46.319 --> 00:04:48.319
And they're like, you can you can send me one per week.
00:04:48.560 --> 00:04:51.360
Like that that's your maximum app distribution.
00:04:51.519 --> 00:04:53.040
So I think about that too.
00:04:53.120 --> 00:04:58.079
Like, what is our appetite for this, for kind of this creation?
00:04:58.560 --> 00:04:59.600
Where's the limit of that?
00:04:59.680 --> 00:05:00.079
I don't know.
00:05:00.399 --> 00:05:08.879
We should be testing the latest and greatest and see what are the things that are actually bringing us, you know, 10x, 100x productivity gains.
00:05:09.120 --> 00:05:22.639
And I think part of that means that we have to experiment a lot, maybe build a lot of different apps, build a lot of different integrations and see what works because you know the price you pay for not experimenting is like you don't actually know what's possible.
00:05:22.720 --> 00:05:32.319
And I think it's important to build things, test things out, even say, you know, if 99% of them fail, like 1% is going to be, you know, a huge lever for your team.
00:05:32.560 --> 00:05:48.399
Yeah, and I think the part of that discipline then becomes too like, how do we how do we find so much more comfort than we're used to in killing those apps or killing that code or saying, we try this thing, it's kind of dumb, it didn't work out, or good idea, let's remix it and put it over here.
00:05:48.560 --> 00:06:01.600
And I I think about um even that cleanup stage, I think that's something that we haven't fully figured out yet because we've never had this proliferation of application or proliferation of code that is so disposable.
00:06:02.079 --> 00:06:08.160
Instead of saying, like, say, waiting weeks to get user feedback, you know, we publish Momentic multiple times a day.
00:06:08.319 --> 00:06:10.319
We can just ship it and see what happens.
00:06:10.480 --> 00:06:17.439
There's a lot of value in just getting it out there, experimenting and you know, see what works or not, because it's very easy to fix or update.
00:06:17.680 --> 00:06:18.959
Yeah, it totally makes sense.
00:06:19.120 --> 00:06:23.199
At Momentic, I know you're you're thinking a lot about this validation step.
00:06:23.279 --> 00:06:27.680
Um, and you're a team that's really kind of at the forefront of thinking about that idea.
00:06:27.839 --> 00:06:30.240
Your customers have run two
billion test steps.
00:06:30.399 --> 00:06:35.279
Is there anything interesting that's happened in this data that you're seeing in their behavior?
00:06:35.439 --> 00:06:40.399
Obviously, you know, they're coming to because they're in this AI moment looking for an AI solution.
00:06:40.639 --> 00:06:42.959
What are you observing from what you're seeing customers do?
00:06:43.360 --> 00:06:51.040
Yeah, I think what we're seeing is that the rate of change, you know, the rate of code output obviously has increased a lot.
00:06:51.199 --> 00:07:10.480
But I think depending on how teams adopt certain tools, um, like more output is not necessarily better, you know, because I think it's there's like uh it's important that more output, say like more code output directly translates to say like, you know, new features, better use user experience.
00:07:10.639 --> 00:07:12.800
Everyone wants to tighten the feedback loop.
00:07:12.879 --> 00:07:14.079
How can you make it faster?
00:07:14.240 --> 00:07:20.399
And I think the form of that is through tests, say like a critical flow like authentication or or billing or anything like that.
00:07:20.639 --> 00:07:28.000
And I think the people who are shipping the most value are the ones who are optimizing for that feedback loop.
00:07:28.240 --> 00:07:30.879
How do you think about the quality of the signal?
00:07:31.040 --> 00:07:43.680
You know, just in terms of if I think about kind of in a pre-AI world, if I think about A-B testing, for example, you know, part of the discipline of an A-B test is, okay, well, how long do I have to run it to get to any kind of significant signal?
00:07:43.920 --> 00:07:46.240
How do you think about that challenge now?
00:07:46.399 --> 00:07:51.759
Are people thinking about kind of like the volume of data that you need to get to significance?
00:07:51.839 --> 00:07:52.399
How do we decide?
00:07:52.639 --> 00:07:54.319
Yeah, that's a that's a good question.
00:07:54.480 --> 00:08:01.600
I think, you know, I'm just thinking back when we first started, when Jeff and I first started Momentic, we were in YC, we had maybe like two paying customers.
00:08:01.759 --> 00:08:05.839
You know, like what's this, what does statistically significant mean?
00:08:05.920 --> 00:08:09.519
You know, we're gonna survey all of them, like, you know, like two, two two out of two.
00:08:09.759 --> 00:08:13.759
Two out of two is you know, not not a lot of you know high signal data.
00:08:14.000 --> 00:08:20.800
So I think how we approach it today is like, for example, in Slack, you know, most of our customers have shared Slack channels with us.
00:08:20.879 --> 00:08:26.160
You know, we collaborate with them, we meet very often with them, you know, to get feedback, show them the latest and greatest.
00:08:26.319 --> 00:08:31.120
And I think feedback that we collect is both like quantitative and qualitative.
00:08:31.279 --> 00:08:34.399
And like, you know, for example, like we have session recordings.
00:08:34.480 --> 00:08:36.879
We can see how they're actually interacting with certain things.
00:08:36.960 --> 00:08:44.720
Like that doesn't necessarily require us to, you know, have a survey or like, you know, hey, what are the frictions of using Momentic today?
00:08:44.960 --> 00:08:48.799
How we shape product at Momentic is vibe-based, right?
00:08:48.879 --> 00:08:56.559
It's like it's based off conversations we have with prospects, with customers, you know, they're giving us feedback, you know, we're seeing how they use Momentic in the wild.
00:08:56.720 --> 00:09:02.320
Do we have to survey, you know, 300 users to get 95% with plus or minus 5% error bar?
00:09:02.559 --> 00:09:10.559
Like, probably not, but I think you know, based on all these conversations we've had with our customers, you know, I'm pretty confident that this change will make their life better.
00:09:10.960 --> 00:09:21.919
So interesting, too, because we talk so much about the attributes of taste, of judgment, of kind of having conviction of what you're building, of intent.
00:09:22.159 --> 00:09:30.960
And so I think in many ways the ability to decide based on vibes, based on taste is becomes even more important.
00:09:31.279 --> 00:09:38.879
Um, because if we're experimenting at this rate, if we're shipping at this rate, the data in many cases will never catch up to tell us.
00:09:38.960 --> 00:09:40.559
Um, or it'll be too noisy.
00:09:40.639 --> 00:09:40.720
Right.
00:09:40.879 --> 00:09:42.799
It'll be very hard to distinguish signals.
00:09:42.879 --> 00:09:43.919
So yeah, I don't know.
00:09:44.000 --> 00:09:46.720
I I think about um just that taste quality.
00:09:46.799 --> 00:09:52.080
And the other thing I think about is how do you teach taste and how do you uh develop that?
00:09:52.240 --> 00:09:55.759
But part of it is just shipping all the time, I think, and getting a feel for is this good or not?
00:09:56.000 --> 00:09:59.919
We're essentially building the tools that we wish we had when we were engineers.
00:10:00.000 --> 00:10:01.600
Well, some of them are still engineers.
00:10:01.679 --> 00:10:14.960
Um, and I think there's like incredible value in that because you know you may not necessarily be able to quantify it, but you kind of have an intuition for oh, what is the workflow I would expect as an engineer for this specific developer tool?
00:10:15.200 --> 00:10:20.639
And momentec, you spent a lot of time, you know, thinking about this validation step, thinking about this testing step.
00:10:20.879 --> 00:10:23.600
How is the role of that QA engineer changing?
00:10:23.679 --> 00:10:24.639
What are they doing now?
00:10:24.960 --> 00:10:26.960
Like how is their how does their day-to-day shift?
00:10:27.120 --> 00:10:27.200
Yeah.
00:10:27.360 --> 00:10:28.159
Tell me more about that.
00:10:28.480 --> 00:10:32.320
I think the lines between roles are blurring more and more.
00:10:32.480 --> 00:10:37.679
And I think the barrier for entry into what we
used to consider software is also blurring as well.
00:10:37.840 --> 00:10:43.919
So I think the titles I think will need to change in the very near future because you know, what is an engineer?
00:10:44.080 --> 00:10:49.279
I think technically anyone could be an engineer today, you know, if the bar is only getting higher and higher.
00:10:49.600 --> 00:11:03.039
But in a sense, I imagine those folks sitting uh, you know, as a QA engineer, uh evaluating, judging output as kind of your professional career may be very well placed.
00:11:03.200 --> 00:11:14.399
Like they have may have this very well-honed sense of judgment and taste because of that role of, you know, my role has been historically to look for bugs, to look for issues, to find problems.
00:11:14.879 --> 00:11:18.159
That feels like a kind of a useful skill set at this moment.
00:11:18.480 --> 00:11:19.120
Def definitely.
00:11:19.279 --> 00:11:24.879
And I think that it's even more powerful when you know, now you're like, say I used to be a QA.
00:11:25.279 --> 00:11:27.759
Now I'm actually building full-fledged features.
00:11:27.840 --> 00:11:36.080
Like I have a much higher bar than say someone who has ever no experience, you know, testing or verifying product.
00:11:36.159 --> 00:11:38.240
And I think that skill set is incredibly valuable.
00:11:38.399 --> 00:11:48.480
It's like it's it's almost like kind of like thinking from first principles, like, you know, it's cool, we built this really cool software, but you know, how are all the people gonna misuse it now?
00:11:48.799 --> 00:11:49.919
You know, it's a text box.
00:11:50.000 --> 00:11:51.039
What are people gonna type into it?
00:11:51.200 --> 00:11:51.600
Oh god.
00:11:51.759 --> 00:11:54.879
Um, and I think that type of thinking, I think is incredibly valuable.
00:11:55.120 --> 00:12:01.200
It's so interesting too, because I think in some, especially bigger organizations, maybe that person really wanted to go.
00:12:01.679 --> 00:12:06.159
They're like, I see it, I can fix it, I have the skills to fix it, but for whatever reason, not allowed to.
00:12:06.399 --> 00:12:11.759
Yeah, I think we want to make that loop as tight as possible with as mid little middlemen as possible.
00:12:11.919 --> 00:12:16.159
And you know, I think that's how we can iterate really quickly and just move really fast.
00:12:16.480 --> 00:12:20.879
So I'm curious, can you tell me more about how your engineering team is structured?
00:12:21.120 --> 00:12:37.200
I think this is it, it's sounds like such a kind of basic tactical question, but people are very interested in it at this moment because you know, if I can, if I can output at such a higher rate, if I have this feedback loop that's so much tighter, if I can be so much closer to both the customers and the code.
00:12:37.360 --> 00:12:39.120
Okay, well, what does my team need to look like?
00:12:39.200 --> 00:12:40.000
How have you thought about that?
00:12:40.080 --> 00:12:40.799
How are y'all starting to do that?
00:12:40.960 --> 00:12:42.320
Yeah, that's a that's a good question.
00:12:42.399 --> 00:12:45.759
And I think you know, today we're you know, Momentic is still pretty small.
00:12:45.919 --> 00:12:50.320
We're you know, 13 people, about to be 14, we're F7 engineers.
00:12:50.559 --> 00:12:56.240
The amount of parallelization we we can unlock with AI is massive.
00:12:56.320 --> 00:13:03.759
So like now instead of executing on one or two, we can execute, you know, like four or five X more actual projects that are massive.
00:13:03.840 --> 00:13:10.159
So for example, um, we just launched Android support back in uh October.
00:13:10.399 --> 00:13:12.799
Like iOS is coming in like a week.
00:13:13.039 --> 00:13:19.360
If you ask me, like, you know, two, three years ago, like how if we wanted to do this, it was like we're gonna it's gonna take like six months to a year.
00:13:19.440 --> 00:13:23.120
Now it took like you know, you know, a few weeks, maybe a month, a month and a half.
00:13:23.440 --> 00:13:24.559
It's like it's incredible.
00:13:24.960 --> 00:13:28.399
What is the most overhyped thing in AI testing right now?
00:13:29.120 --> 00:13:44.320
I think one of the most overhyped AI testing is really uh focusing on like I'm gonna crawl your whole app, we're gonna figure out every single thing your users are doing on your app, and we're gonna generate tests for you.
00:13:44.480 --> 00:13:49.679
And I think that approach is, you know, it sounds great on marketing, it's like, you know, oh, I don't have to do anything.
00:13:50.080 --> 00:13:53.519
The AI is gonna just figure out everything my user is doing, what's broken.
00:13:53.679 --> 00:14:04.879
But I think the the problem is I think there is like kind of like a chicken and egg thing, you know, like what you have live in production is you know a function of like what you what code you have deployed.
00:14:05.039 --> 00:14:14.000
And you know, just the nature of software, you know, there's going to be bugs, you know, and I anticipate there are going to be bugs for you know quite a bit, even as you know, AI continues to improve.
00:14:14.159 --> 00:14:18.399
Um, you know, you know, that's why we have all these you know code review bots, there's like 20 of them, you know.
00:14:18.720 --> 00:14:19.600
We have one, yeah.
00:14:20.240 --> 00:14:21.200
And and for sure.
00:14:21.360 --> 00:14:27.759
So like using production as your source of truth is just fundamentally flawed because production will have bugs.
00:14:28.080 --> 00:14:35.600
Saying that we're just gonna use AI to crawl your app and figure out what's wrong is just like, well, how do you actually know what's wrong?
00:14:35.679 --> 00:14:40.480
You know, because you know, what's actually live in production might not actually be what you want.
00:14:40.720 --> 00:14:41.519
This is so interesting.
00:14:41.600 --> 00:14:48.799
I've been thinking about this too, just in terms of your kind of what exists may
not be your ideal.
00:14:49.039 --> 00:14:54.720
And so kind of your opportunity space is the delta between your ideal and what's out there today.
00:14:55.120 --> 00:14:57.120
But I guess this is why you guys go back to the spec.
00:14:57.200 --> 00:15:04.399
You're like, the spec is what we're trying to get to, just because the code is this, that doesn't mean you know, that's what you were trying to achieve.
00:15:04.639 --> 00:15:04.879
Yeah.
00:15:05.039 --> 00:15:17.039
I think if anything, being specific in what you want and what you don't want, that's incredibly important because whatever you tell AI, anything that's ambiguous, it's definitely gonna go there.
00:15:17.440 --> 00:15:21.759
So I think, you know, in that sense, like we're thinking about like specs as the source of truth.
00:15:21.840 --> 00:15:27.279
Like these specs are kind of your north star, what you want your software to look like, how you want your product to behave.
00:15:27.440 --> 00:15:29.279
I think it's important to make that distinction.
00:15:29.519 --> 00:15:36.320
I think we're so used to just imagining that the thing that has been built is the thing that we meant to be building the whole time.
00:15:36.480 --> 00:15:40.080
And in fact, like we don't we may not know if we're we're trying to go.
00:15:40.399 --> 00:15:46.000
It was like, you know, when a test fails, how do you know that it's the test's fault?
00:15:46.159 --> 00:15:51.919
Or maybe the feature change was intentional, or maybe it was a breakage, and they're like, you know, we don't know.
00:15:52.080 --> 00:15:56.720
Support docs are out of date, PRDs got out of date, the Jiro ticket got implemented, you know, two months ago.
00:15:57.039 --> 00:15:59.440
There's been like a few thousand commits since then.
00:15:59.600 --> 00:16:08.960
Figuring out what it's actually supposed to do, how it's supposed to work, I think is is going to become more and more important, especially as we delegate more stuff to AI.
00:16:09.279 --> 00:16:10.960
It sounds really basic, but it's not.
00:16:11.120 --> 00:16:11.360
Yeah.
00:16:11.519 --> 00:16:11.840
Yeah.
00:16:12.159 --> 00:16:14.639
It's there's so much that's really interesting in that idea.
00:16:14.879 --> 00:16:16.960
You founded a company about quality.
00:16:17.200 --> 00:16:25.840
Um, and there's this whole conversation right now about the tension between slop and the tension between quality.
00:16:26.000 --> 00:16:30.159
Like we have so much more throughput, we can ship so much faster, we can do so much more.
00:16:30.480 --> 00:16:34.320
How should engineering leaders think about where the quality bar is?
00:16:34.480 --> 00:16:38.960
Yeah, I don't want to dictate where the bar should be set, but I think the bar is higher than before.
00:16:39.200 --> 00:16:49.039
You know, I think just because you can ship a lot more code, um, it doesn't necessarily mean you're shipping higher quality code.
00:16:49.360 --> 00:16:57.840
I think there's incredible value in kind of stepping back to think, like, you know, from first principles, like what are the problems we're actually trying to solve for our customers?
00:16:58.000 --> 00:16:59.120
How do we want to solve it?
00:16:59.279 --> 00:17:02.240
And like how we actually present it to your end user.
00:17:02.559 --> 00:17:12.640
I think one of the things that we're very excited about is that you know the ground is shifting beneath our feet and you know, quality is more important than we think.
00:17:12.960 --> 00:17:16.720
And, you know, I think, and to have high quality, you need to be specific.
00:17:16.880 --> 00:17:26.960
I find myself when I'm creating linear tickets, I just put in the title and then I'm just thinking about okay, if I gave this to say some AI agent to build it, will it actually know what I want it to build?
00:17:27.119 --> 00:17:32.400
I have this random idea in my head, but it's not like you know, my engineers or our AI can read my mind.
00:17:32.480 --> 00:17:36.400
I need to be specific about what I want and what I what it needs to look like.
00:17:36.640 --> 00:17:37.440
What do I really mean?
00:17:37.599 --> 00:17:38.079
Yeah, exactly.
00:17:38.240 --> 00:17:38.480
Exactly.
00:17:38.720 --> 00:17:41.279
You know, you have to be clear and exact to the AI.
00:17:41.519 --> 00:17:45.200
To your point, ambiguity is not is not a good thing for your agents.
00:17:45.680 --> 00:17:48.960
Yeah, you can it can spend money now, it can send emails.
00:17:49.039 --> 00:17:51.119
I'm like, I don't know if I want it to do that.
00:17:51.359 --> 00:17:53.039
You're like, how well did you prompt it?
00:17:53.440 --> 00:17:54.480
What are the guardrails?
00:17:54.720 --> 00:18:01.680
Yeah, there's all this hype about, oh, AI agents are gonna be able to do everything for us.
00:18:01.920 --> 00:18:06.160
And there's not as much thought on like, well, do you actually want it to do that for you?
00:18:06.319 --> 00:18:11.519
It's like I don't really want it to, you know, pay my rent for me, like or like sign a lease for me.
00:18:11.599 --> 00:18:14.079
Like, you know, I want to tour the apartment kind of thing, right?
00:18:14.160 --> 00:18:21.759
Um yeah, it's like, you know, I don't really want to be in like the the Wally movie, you know, sitting there on the chair and be like, think about that movie so much.
00:18:22.559 --> 00:18:23.119
Like it's a lot.
00:18:23.200 --> 00:18:24.319
It's in my head all the time.
00:18:24.640 --> 00:18:26.960
Wait, wait, it's been really fun chatting with you.
00:18:27.200 --> 00:18:27.599
Thank you.
00:18:27.839 --> 00:18:29.680
You've been listening to We Built What?
00:18:29.839 --> 00:18:34.480
If you like what you heard, please like, subscribe, share with your friends, humans, or agent.
00:18:34.640 --> 00:18:37.519
And if there's someone you think we should interview, let us know.
00:18:37.759 --> 00:18:38.640
Thanks so much.