Zach Lloyd

First thing from rewriting Google Sheets is I would say don't rewrite things.

We rewrote Google Sheets because it's at crazy scale.

And so if you have something that has

hundred million plus users, which is what it had at the time.

I think it's now like a billion users.

It really matters that the thing is awesome.

And so it's worth the effort of like 30 to 40 engineers for a couple of years to like get it right.

Right.

But I would say for the audience, for this show, which assumes more founders, like rewriting is like a horrible idea.

It's like pausing time.

So for the startup people out there, I think try to pick the right thing to start is a little bit better advice.

One lesson I did take for this is for warp.

For instance, we built it the hard way to start meaning like, you know, I could kind of see around the corner, like if we built it on sort of web tech or whatever, we're going to run into a bunch of performance problems, which is a lot of what we were trying to fix with the, the sheets rewrite, like good engineering matters.

But I think it's highly dependent on like where you're at in the stage of building a thing.

And so yeah, rewrite, if you have like crazy product market fit and you know, a hundred million plus users, it needs to be perfect.

If you're really early, I think rewrite is a little scary.

I guess if you literally have no one, fine.

But my take is like in startup land speeds everything.

And the anti-pattern that I'm looking out for is like, okay, I was a Google engineer building for tons of scale and then go to a, found a company.

And like, it's very easy to get like,