Reddit CTO Chris Slowe: The Engineering Decisions That Built the Front Page of the Internet

Reddit primarily exists as a platform for criticizing Reddit. It took the scenic route to becoming a major part of the internet. Tech debt is the sign of a not-dying startup. There is still a lot of code in our stack which still has my git blame on it from a much earlier vintage of me, and that guy didn't know what he was doing. So I'm, I am both proud and terrified that it's passed the test of time.

Today, the CTO of Reddit and technical architect behind the 6th most visited website on the internet Chris shares the engineering decisions that have led the platform from a scrappy startup to a global giant, navigating massive rewrites and building for a deeply opinionated community of millions. We dig into the reality of scaling technical teams, why hope is not a strategy, and what it really takes to keep the front page of the internet running for two decades. Chris, thank you for coming.

Glad to be here.

I was telling you on the way up as we were coming that I, trace back the start of my Reddit journey to 2011, peak neuroplasticity. So I trace a lot of my theory—

So you're saying we've corrupted an entire generation?

Because I remember I watched a talk and you said it's hard for me to take myself seriously and it might be because I grew up on Reddit. So I have a little bit of that as well. And then founding engineer and current CTO of Reddit, Chris joined Reddit in its earliest days back in 2005 as the first hire, earning a PhD in physics at Harvard. Architect behind some of Reddit's most foundational systems, including the hotness ranking algorithm and the early anti-spam infrastructure that helped keep the platform usable as it scaled. And then left to work with Steve on another startup, the CEO, the current CEO of Reddit. And how did Perplexity Deep Research do?

Did pretty good. It was actually 2016, but close enough. And at this point, that's, you know, who cares, 8 or 9 years either way. But no, overall, like, good, good LLM summary there. I think there might be something to this technology. I'm not sure. Getting a hint it's not just a fad.

Well, so one of the things that was the most interesting for me to put myself into your shoes as I was thinking about some of the things I want to talk to you about in this is thinking about the redesign of Reddit and at the time, top 10 most used website in the world. And so I think something that would be an interesting place to start is, in retrospect, any words of wisdom, things for a team who's about to go through a massive rollout?

Well, okay, to start with, I'll say what I always say in situations where a redesign is involved. Congratulations. It's going to be, it'll be fun and harrowing and terrifying. I also keep in mind that Reddit took a very, it took the scenic route to becoming a major part of the internet. I remember going back, like way back in the day, I'm sure no one here remembers, like originally there was these rankings called Alexa, predating the Amazon service, where it was just effectively the rankings of all of the sites on the internet. And in the early days, we used to track our Alexa ranking and just kind of like watch us break into new, like, you know, new tiers. And I just remember the same, roughly the same summer that Reddit launched, YouTube also launched. And I just remember seared in my memory is like our lovely, like we're making progress. And then you overlay YouTube and it's just like vertical line and just appears right in the middle of it. So there's always somebody who's going to grow faster, but like compounding growth over 20 years actually gets you somewhere is the lesson we learned. For the specific redesign, oh man, I have lots of opinions. Okay, so I'd say start with where I've seen things go terribly, horribly wrong. The discussion usually starts with, well, while we're in there, and then usually you make a decision that starts to push you towards overreaching how much you're going to do in the redesign. So what's good to try to do is just try to separate out, I mean, I don't know the scope of your redesign, but try to separate out as much as you can, UI changes and user experience changes from drastic backend rearchitectures. Now they're going to be coupled because you can't just usually slap a coat of paint on the frontend. And of course, modern practices as they are, everyone likes to build web apps in such a way that they are absolutely transparent from server to client. And that's really great from a velocity standpoint, but it's really tough from like a separation of concern standpoint. Make sure you can revert, honestly, would be my starting point. Or make sure that you're at least starting with small scale ramping up. The way that we did the redesign back in '18, and actually the way we've been doing it ever since when we do like a major rebuild, is we, it's a little bit beyond just doing simple A/B testing. It's actually starting to identify user cohorts that are gonna get the new experience, which is difficult in Reddit 'cause you know, Reddit primarily exists as a platform for criticizing Reddit. So you can't just secretly launch things and have people be like, oh, this is a great novel experience. I love this so much. Instead it's like, what is Reddit doing? But what we did was we, for the redesign, we actually broke it into like, we did a private beta where we had users involved in playing with the beta. And then as we had success with the beta, we pulled in more users. And then the nice thing about that is you get a nice little flywheel where it's not like You're not trying to educate the users. The users could educate one another. And then also you get some advocacy for the actual thing. So you get, everyone gets a little bit of like, the people who start to use it start to realize that it's not horrible and you're not trying to destroy the product they love. And they can actually advocate for it as much as you can.

Wanna go deeper? Talk to Chris's digital mind at delphi.ai/chris-slow. Another thing that I've also heard you speak a lot about is processes and systems start to become culture. They're a lover for culture. And I'm wondering what were some of the things that you found that started to break once you got to that level and the corrective measures you took?

So, um, I would say that, um, one of my learnings over the years has been, um, you do need to, when you set up a startup, you have to start by minting at least a starter set of values that you can share with the team. And you can think of values as being a couple of different things. So one way I like to think of them as they're kind of like verbal shortcuts for behaviors. So they're a good way to, you know, when you have a discussion or a debate or an argument, if you can resolve that by invoking a value, it saves everyone a whole bunch of time and it kind of immediately gives you alignment or at least grudging alignment of like, okay, that's how we operate and therefore we're going to kind of move on from this point. It also means that as the company gets larger and you can no longer rely on just the simple social graph of the people in the company, that you can still have some notion of almost common culture to be able to align to. There's a whole set of these dumb— I don't know if you know of Dunbar numbers, but there's a whole set of them. It's actually not just one, there's actually tiers effectively. And the tiers break down the size of the group relative to the overall intimacy level you can have with them. And so when you're talking about a room this big, which is around a dozen people or so, This is effectively a family, like to be kind of, and not in a condescending business, we're all a business family, but effectively you can know each other's stories, each other's names, you have a whole bunch of backstory, a whole bunch of context. And so if somebody rolls in and looks really pissed off, you probably can make some guesses or you want to check in with them because you're actually on a much more familiar relationship. When you get up to about 50 people, Well, that's the point where you start being able to, you lose track of individual stories and individual people. You can keep track of names, but from 50 to 150, you're at the range of casual acquaintance. You might know them, you probably run into each other in the kitchen, you get to say hi, but you don't have any shared context. You might even know what, you probably don't even know what each other's doing. And then when you get past 150, it's like all bets are off. It's like you're effectively strangers. You run into somebody, it's like, I mean, one of the startup problems you end up at the 150, you start having these problems of Well, why is that team messing with our stuff? And the answer is like, that team doesn't even know you exist, let alone like messing with their stuff. They just found a service that they had to change and be like, you run that service. But, and yeah, they should have reached out to you, but like, did they reach out to you? Did you answer them when they reached out to you? Like, you know, and so, so back to that, like the point of culture is now to start to set up some, just some habits and some behaviors that are transferable across the entire group, even when you don't have any shared context beyond that.

And so one of the ones that you guys have, Remember the Human.

Yes, the oldest one, the one that actually stuck around for a very long time.

I was going to ask what was the origin of that?

So this is most things. So Steve does a sort of like usually once every 2 or 3 years he goes through and does a refresh on our values. And Remember the Human was, so when he came back in 2015, first thing he did and one of the things we learned at our intermediate startup was this whole thing about values are important. So he came back and he basically built the first set of values and that was one them. And the intent was to be, I think, cover a bunch of things. So on the one hand, it's remember that you are building a product and there are humans on the other side of that screen, and therefore your work is affecting their life. And then third thing is internally, it's nice because it's like, remember, assume good intent. There's other people here. You're not just acting alone. You have to work together as a team. And so it's actually been the one value that's had the most broadly applicable use. Which has actually helped out a lot. We've had other values that I think over the years have varied. And so like actually when we were a startup that wasn't much larger than this size, we had one that was everyone does the dishes. And the intent of that was both literally, hey, we all share a kitchen, please don't leave dishes in the sink because we're like effectively roommates here when we're working during the day. But it also covered on the way through engineering, it's like, Yeah, don't leave shit around. Like if you're gonna go clean something up, finish cleaning it up. Don't leave a mess for somebody else to have to come along and clean up. And of course that value actually, that lasted for a while and then we ended up sunsetting it. And in part it's because the parts you want become part of the culture and they become automatic. And in part it's because, well, at some point you actually just need to hire somebody whose job is to do the dishes. Like you don't assume, you know, tragedy of the commons is a real thing. It works unless you have like some sort of social pressure to make sure nobody's like, you know, some people are not leaving their stuff in the sink. You probably need to hire a janitor sometimes.

And so one of the things also that sticks around for a long time, we're talking about cleaning up messes and hope not being a strategy, is tech debt that you've incurred. And I'm wondering, I'm sure you have some interesting stories. What has been the longest running piece of tech debt? Maybe one that's even now or You already have things that are coming to mind.

Okay, so before I answer that question directly, I will say that what I've learned is that tech debt is like any other sort of debt. You take out debt because you want to have a short-term speed-up and you just know that whatever you've, with those choices you've made, you have to pay it down at some point in the future and it compounds. So it's going to stack up. You all know this. I think I've also learned that when tech debt Tech debt is the sign of a not-dying startup. If tech debt is your biggest problem, you probably have gotten far enough past product-market fit to have other problems to deal with, or at least your existential problems are handled, right? You probably have a sales cycle. You probably have a product that's working. You're now working on like maybe iterations and new versions. It means that you're not just going to do a pivot where you're just going to rip the bandaid off and greenfield a new product. Oh man, I mean, we have, okay, so it's actually getting really good right now, but we are about in year 6 of the Decommission the Monolith project, which I think everyone at some point goes through, at least from a certain genre of startups when, you know, it's like, ah, of course we do. So you only have 18 people, right? So like, so you only need one codebase, right? You'll need like, you don't need microservices when you don't have teams to break the micro across, right? You don't need separation of concerns. You just build all in the same pile. And the nice thing about monoliths are they're easy to deploy because they're effectively global. They're also easy to red-green if you want to do experiments because you can just have two partitions. Traffic routing straightforward, like hundreds of reasons why monoliths are great. Monoliths are annoying when you have more than about 50 people and they get really, they get impossible when you get past about 150, just you can't scale up. So everyone goes through this of having to break off services. The problem is that the monolith is just a it's a pile of business logic over time. So my point was, there is still a lot of code in our stack, which still has my git blame on it from a much earlier vintage of me. And that guy didn't know what he was doing. So I am both proud and terrified that it's passed the test of time. And in fact, my running joke has been like, I cannot leave Reddit until there is no more code that I have minted in the stack. My legacy should be a net zero diff. But no, that's probably some like disentangling our very old, I should mention Python 2 monolith has been a big deal. And then on top of it all, we had a couple of cases of intermediate attempts at building, we actually had a service called the Gateway, which was a way to sort of put an API break on top of our monolith and start to reroute traffic properly. And that thing turned into another monolith that was kind of codependent with it. So We've definitely fallen down the, we've made mistakes, we made some saying, but it is a game of just kind of like for that kind of stuff, you have to actually have teams dedicated to chipping away and building the right thing. It can't be a side project.

Yeah. Well, so one of the super interesting push and pulls that Reddit has with its community is that people get super fixated on the way that it currently is. And so—

But it is currently perfect. I don't know if you knew that. Any change, if it's perfect, any change from perfection, it's not perfect.

You're trying to destroy it. It's very straightforward when you look at it that way.

Also, why did you change that feature when there's another feature much more near and dear to me that I want?

You should just think about that.

Yeah, clearly you have to think about it. So clear when you say it like that.

And how, how are you guys straddling the that dichotomy where there's so much opportunity right now to make features that are especially driven by AI. I texted you about the AI search feature that you guys released.

Reddit Answers.

Reddit Answers. And there's a lot of opportunity for that, for new features, but also not trying to alienate the strong active user base you guys have.

Well, I think the nice thing about specifically Answers is that it is a it's a complement to existing flows, right? It's not in and of itself a destination. It's a way to rethink how could search be on a platform like Reddit where there's tons of good content and the discovery of that content is a difficult problem. And so we're taking the bend of effectively not just providing you with an LLM summary, but actually citations included as first-class, easy way to get to the content that actually shows the conversations. I think that the balancing act, and this has been something that we've not nailed ever, and I don't think any, I think very few companies have nailed it, is like finding the balance between doing experimental features and making sure that you're not just like creating a ton of debt in the process of launching all those little features, right? Like, you know, if you think about like, if you have like 1,000 random experiments happening on your platform, Well, first off, in that situation, you don't even have a common experience for the users. There's a whole bunch of variants that you're seeing. So it's very hard to talk about what's the average experience. And then, you know, most experiments are no results if you're lucky, right? That's the net result. The accumulation of a ton of little experiments can actually be like, all those little epsilons can add up and become something actually non-trivial and negative because you're getting a kind of a weird experience for every user. So I think what we've been trying to focus on in the most recent years has been, well, actually let's just get back to good old-fashioned, like what's the craftsmanship version of this look like? Like what's the first principles? Like what are the experiences we want to have? Where are we actually building things that help users and help them find what they want or engage and enjoy? And when are we just kind of like faffing about because it feels like we should be fiddling with pixels and making sure we kind of like Don't let that part win. But it's not easy. I mean, it's like, it's because like, you know, every, I mean, the other hard part is that with a sufficiently advanced experimental toolkit, you can convince yourself you've created a positive ROI, right? Because you can always look in the experiment and say like, oh man, this moved like D2 comment generation by 0.1%. It's a win. It's like, were you trying to move that? It's like, did you just happen to look through and look for something green? Like what was exactly your plan? Well, I mean, one thing, one choice we made is, um, we still have, um, like old.reddit still exists. It's still up and, um, it, it's consistent sustained, um, engagement from effectively the same group that's been using it for 10 years running now. Cause we actually, you know, we, we did our last major redesign was in 2018 and then we just did another web redesign in the last couple of years and deprecated that one. So it's actually outlasted. 2 or 3 other web platforms in its process. There is something to be said about if it's not hurting anybody, keep a separate version. But of course, there is going to be overhead in maintaining that separate version.

So another thing that AI, outside of the opportunity to produce a bunch of new products, is changing is probably people are putting a lot of AI-generated content onto Reddit. And so one of the things that I'm interested in is how models— have you played with v03?

Yes, that's pretty cool. I think the hard part right now is like every 6 months there's a new model that comes out that's like, wow, this is like the best thing ever. And it just kind of keeps coming. So it's really impressive. Also, I'd say like, yeah, the posts about using v0.3 on Reddit have been really hilarious for quite a while now.

I mean, I saw a, someone sent me a tweet of Moses livestreaming the Exodus. With VO3. He's like, "We're going to talk to the Pharaoh, see what he says." And so now I'm super excited. There'll be a subreddit probably of historical livestreams using models. And so there's the very positive creative aspect that I'm super excited for because of the insane amount of creativity that comes out of it. But what do you think is the best way to, or a way to help people know when they're looking at AI-generated things if it isn't intended, like it's not in the AI movie subreddit.

So we've thought a lot about this one and it's actually been like, it's definitely been also years in the making, right? Like deepfakes as a concept, go back a good 5 years now, give or take. The models are just getting better with time. I do feel like there's a couple of elements here. So I think one thing is there is like, there's just the good old-fashioned cultural element of like, humans are good at calling bullshit on things if you let them. And you go back 20 years and the same arguments were being had with Photoshop. It's like, well, how do we know any photo is real if you can Photoshop it? And now it's just kind of like, well, everyone assumes photos are like face-tuned and slightly tweaked. And it's just kind of like, you can look at it and be like, yeah, it doesn't actually look like that. Those eyebrows don't look right. But I think with things like, with the whole bevy of tools from LLMs, it's just an extremely powerful tool to create extreme creativity. And at the same time, you can use the tools to help you detect the tools in any other arms race that you would see anywhere. I think for us, we try to think more about the kind of incentives and the motivations for why you would do that in the first place and work back from that, as opposed to just trying to directly say, let's go through and try to target, label everything that we think might be from an LLM. The one that came up actually recently that I was actually amused at was there's an article about how I guess ChatGPT tends to use em dashes a lot. And so em dashes are everywhere now all of a sudden. Well, first off, I also happen to use em dashes because if you just type in dash dash, it turns into an em dash in basically every editor known to man. So the fact that ChatGPT uses it more preferentially was kind of a funny thing. Second, it's like, well, you could also figure out like, okay, a lot of people also now use LLMs to help them write. So if I'm going to take something and basically copy it out of an LLM, it doesn't mean that I wasn't writing it. It just means I was using a different tool than I have in the past. I didn't just go to my editor and use all my thumbs to type the answer. I actually wanted to write something cohesive and therefore I'm doing my normal editing loop. And then I think for the actual abuse cases here, we think of it in terms of the same way we think about honestly historical spam problems, right? Like, why are you trying to push content on a platform? Well, you're probably trying to either run an influence campaign or you're trying to make a bunch of money. And those two things are not necessarily separate. They're almost the same thing in a lot of times. Those kinds of behaviors are a tale as old as time on a social platform. And so it does fall into the category of looking for what we would just label as inauthentic behavior or the class of like spam problems where it's like you're trying to build a reputation so you can deploy pull your payload later and make a bunch of money off of it and then move on, right? That can come from signals beyond the actual literal text and the literal image that's being posted. And then I think the last leg of this stool here is like we work via communities. So to some extent, like the, I think watching communities wrestle with this particular, like you can call it a problem, you can call it an opportunity, and figure out where they align. Like you see a whole bunch of like art communities who'll basically be like, none of that AI slap, only like hand-drawn, artisanal drawings, right? And then the flip side of that is you have like entire communities dedicated to specific tools showing how crazy you can build like the Moses crossing the Red Sea livestreaming. And so we want to, again, we want to attack the behaviors and the outcomes and let the communities wrestle with the, how does that tool fit into the ecosystem of what other tools they have available?

Very interesting. I haven't thought about categorizing it in, I mean, two things. One, in the same vein as just traditional spam, and then also thinking about going back to incentives instead of trying to attack the behavior. I was going to say maybe this is the on-ramp for crypto and we put—

What are we buying and selling now?

And we put watermarks that are cryptographically verified in every photo. And then the platform Reddit make sure that the picture doesn't have—

And it's all backed by a zero-knowledge proof somewhere on a blockchain.

Okay, exactly.

So when do you want to start? You guys want to pivot? I'm joking. No, I think, so I do think that for a platform like Reddit, there's a bunch of text. It's just a bear in a box. And so the point is the conversation. And so the point is to create a system where there is trust in the, there's at least trust in the underlying community. There's trust in the interaction. And then we're able as a platform to kind of keep the jerks at bay for all definition of jerk, right? Or we provide the community with tools to keep the jerks at bay even better, right? One of the things that is actually novel about Reddit is we do have an ecosystem of self-identifying bots who run around and try to be helpful. And that goes back well before the existence of LLMs. Like this is 15, 20 years old, as soon as we opened up our API, all of a sudden people started writing agents against it. And all the way from the metric to English and back and forth bot that exists that runs around, or there's one that'll identify when you've accidentally written a haiku in your comment. I think that's always kind of funny. But the fact that those are self-identified means that there's trust in the system because you know you're dealing with a bot. Where the line gets kind of blurry is like, are you like, dude, are you real? Is when you have to start getting into the thinking about the systems and the incentives and how do you make sure that the, that there is policing for that kind of behavior.

I mean, something that I am continually blown away by with Reddit is the amount of time that people will spend making very high-quality creative posts that are well-researched and the amount of the volume of quality content that people put on it. There's been a couple times in my life where I was about to, I was preparing for a long trip or something else and people would have just insane guides. And then the other thing is in the comments, the self-policing where people will say, oh, that was a mean comment or this is AI generated and just you'll open the comments and people are very, very passionate. And so I think it's a very unique thing about Reddit.

The funny thing or the funny discovery was, we made a decision early on that we wanted to stick with the kind of like, not really anonymous, but this kind of like pseudo-anonymous setup of you create a username and you just kind of like post a bunch of content and you're off to the races arguing over effectively stupid internet points, right? And the nice thing about that is it feels like the first principles and most of the social platforms pivoted the other way and saying like, no, no, you should attach your name, you should have skin in the game, you'll behave better if it's associated with you. And I think we found it's actually the opposite. It's like people no longer care about their name being attached to things, but at the same time, they do put a lot of effort into posing and posturing and influencing and trying to create personas that are kind of false. Whereas on Reddit, since it is all synonymous, you don't really have any, you're not trying to prove anything. It's like you're going to be helpful or not. And like, yes, there is an abuse vector, but there's an abuse vector on every social platform because you're dealing with people. Um, but the, the positives definitely outweigh the negatives, right? The positives are, yeah, you might just be some guy who happens to be like a big fan of horticulture and like some obscure thing. And like, there's a question that appears and it's like, oh, this is like my jam. And you just write a long answer and you're not expecting anything out of that than just like this kind of altruistic, like, I want to be altruistic or I want to feel good by being a part of this community, or I care about this community, I'm helping it. And that's a lovely virtuous cycle. It's also extremely difficult as a product to explain, by the way.

I have rapid questions and then we'll open it up to everyone else. So first thing is React versus Lit, why?

Oh, we have done both. Lit gets heavier the more people you have developing on it and it gets to be really hard to debug. There's something really nice about server-side rendering of HTML.

Okay.

It's almost like the entire system was built on top of that as an idea.

Favorite AMA, Dona Rabbit?

Oh man. I think that there was a tradition we had of honestly, Bill Gates would come by like once a year and he always was just so funny and engaging. I think I can't not name the fact that at one point President Obama came and did an AMA. That was a terrifying experience because that was definitely like, you know, harrowing. There's been some really good ones. Also like Keanu Reeves, exactly what you'd expect. Just like such a cool, chill dude.

I just found that one.

Isn't he great? Like, it's like a, he's just, it's always fun to find, it's always fun to be reassured that there are people who are just awesome people. Like there's no secret. They're not just like, they're not secretly like breathing fire and eating babies. They're just like, nope. He lives the life that he acts like he lives.

Craziest idea to come out of Crazy Idea Friday during your redesign.

Oh man, you're digging deep into the well on this one. I gotta go back and remember those periods. Um, we had a lot of, we had a lot of fun ideas for projects that never really took off that we've had to since unwind. I think the one that actually still, I still believe could have worked was we tried to set up an entire, um, and we've, I think we've iterated on since then. We had this idea of like helping to set up like an event flow for communities that are around like fan bases of like TV shows. So it's like, you know, automatically trigger the post when the, when the episode drops and kind of get that whole thing going. It's, it, it was, that one was, that one was tricky to kind of land.

This, like, to the point of people who are super invested, this happens, the mega threads.

Yeah, yeah, yeah. Mega thread, we have to, we have to, we still have a problem right now that we have to do, like, for a certain size of thread, they're hard to manage. And actually the easiest thing to do is just have them auto-roll new ones and like substitute them. But megathread management is definitely like a, I would go out on a limb and say it's an underinvested area right now. It ends up being, the hard part is it's such a small slice of the overall traffic profile. But when they're up, they're just like so, they're such a big deal.

Yeah. Because I found myself, I found myself looking at Reddit every day during the Lakers playoff run because I'm a Lakers fan and they're always megathreads, you know, whenever they're playing or people are talking about the game. So the next one is worst architecture decision at Reddit.

Oh man, okay, so going back in the well here, I'm gonna diss an entire probably technology. We decided really early on to move to Cassandra and this was like Cassandra version 0.6. So bad choices were made by going to some sub-integer version. And we started using that to, basically the quick version of it is we use it as a way to build not quite a data store, but almost like a persistence layer persisted cache. Most of Reddit ends up being materialized views of content and you want to basically have that be fast and perky and updated and you can rebuild it from the canonical source, which is a database. And when originally we put it together, we had it running behind a cache and then we dropped a cache and we had to go straight with it. We had to go into Cassandra to do those queries and we discovered that it wasn't actually performant enough to run. So our, I think our longest downtime was like 24 hours back in 2010. And that was pretty brutal.

Okay, Cassandra.

We dug a big old hole in that one for a while too. And we've modernized since then. It's been like back and forth. We know how to hold it now. I think that that was the, actually the biggest mistake, I can summarize the class of biggest mistakes we've made is, wow, look at this cool new shiny technology. It's gonna solve all of our problems. It clearly has some really great maintainers and they know what they're doing. And it's gonna be great.

To that point, picked a beta version of an ORM wrapper adapted from TypeScript to build our entire backend on that got sunsetted 2 months ago.

Oh yeah. Okay. Yeah. Yep. That sounds about right. That's the breaks. Them's the breaks. Oh, actually I thought it would've been better, but better dumb decision we made now that we mentioned Postgres, really, really far back. We're going back into first couple years of Reddit. We had this random, we had this idea of building an entire version of Reddit that was, I shit you not, based on Postgres triggers. So every time a vote would come in, it would like recompute all stuff on the backend. It was almost like, you can imagine this machine was like flicks, like, you know, switches flicking. And like most things that are designed like that, it worked really well until it didn't. As soon as you scale past the ability to have enough compute to do that, it broke really spectacularly. It was really funny.

How do you guys keep your materialized views up to date?

Oh man, it's layers and layers of CQRS models. So what we do is we have, most of it is like, Reddit is mostly not real time and it's mostly eventually consistent. And so there's just a lot of like, you take an event, you put it on a queue somewhere and you fake it until it actually gets computed. So for that user, that vote happened immediately. And then actually what's happening is, there's a whole bunch of, there's a whole Rube Goldberg of things of like 20 years of technology that are processing that vote and making sure all the views are updated properly.

Best architecture decision?

Using Postgres. No, I mean, seriously, it's been like rock solid for, actually, I think I've just started hearing from my infrastructure team that they are looking around a little bit, but it's only because we have just scaled the shit out of Postgres over the years.

Is it still just Postgres all the way down?

Well, so it's like if you've gotten down to Postgres, something drastic has happened, right? There's not very many paths, like, The issue with Reddit is that we have an extremely long fat tail. And so at any given time, there's probably a request that's not in the hot path. But of course the name of the game is to get as much in the hot path as possible, right? Like, you know, we have like terabytes and terabytes of cache everywhere. And then underneath the cache, we have like an equivalent amount of almost like, you know, Cassandra-like persistent storage that you're not building things from scratch. You're actually fetching them like materialized.

What is the cache?

Largely these days Redis, which is super solid. Cool. That's great, great. I think actually though, I'd say with the current, with the current now, like someone said, kerfuffle about open source Redis, we have been looking at Avalky as an option as well and trying to decide on which way that community is going to go. Favorite subreddit? This changes a lot with time. I think that I'll give examples from my own history. So like they change based on my life, like where I am in my life. Among other things. And so I definitely am still a big subscriber to a bunch of like, maker-y kind of communities. I got my start doing experimental physics. I love building things. I don't have access to machine shop. I have a 3D printer and a laser cutter and a bunch of tools. So I love all of the fix my print, Ender 3, functional prints, all those are fun communities. I've got 2 kids. I've got a now 14 and a now 11-year-old. When my youngest was going through his terrible twos, there was a community that happened to hit at the same time and it was called Fuck You, I'm a Toddler. It was just good examples of just like, we used to joke that he was like, he would sort things into things that he could push over and things that would push him over. And that was all. Never the twain shall meet. So yeah.

Martin? You were part of one of the first YC batches.

Where all of them still used to cook food. Are there any furries of the year around? Oh yeah, I mean, those are really fun. So this is like Reddit. Actually, I was in that batch before I was in Reddit. I was actually in the first YC batch in another startup. So I already had a failed startup behind my belt when I joined Reddit. That first batch was 10 people or 10 startups working out of Cambridge, out of an office there. And the weekly dinners were the way to kind of connect with the fellow co-founders and basically trade war stories. And it was a lot of fun just because like it was a, at the time, 2005, there just wasn't much of a startup ecosystem. The whole idea of like Web2 was relatively new. And so it was almost like everyone in that room was kind of learning it, learning it as you go. At that point it was highly contested. Like, should we, is Ruby like a language we should try to learn? Do we go back to do some PHP? So really just that camaraderie of just talking about building a company from scratch. Also, this is a point where in that first batch, there were very few companies that had products to show when that batch started. It was an idea pitch to start with more than anything else. So it really was that first summer with building the first startup. Oh yeah, and also Paul used to refer to the food as glop specifically because there's always some sort of like a rice with like a curry kind of thing. And therefore you get your tray of gruel and then go sit down. He's actually a really good cook.

I mean, that batch was, you see a picture of it, the amount of talent density.

Well, with time it's amazing. Yeah, it's like, so in that batch, there was, okay, let me try to remember the names of the companies then. So there was a company called Loopd, started by a gentleman by the name of Sam Altman. There was a calendaring company by the name of Kiko. That was started by Justin Kan and Emmett Shear, later of Twitch. And then Aaron Schwartz was in that group doing Infogami, which later merged with Reddit for a time. So yeah, a bunch of really smart people.

All right, cool. I think that's everything. Thank you so much.

Thank you.

Thanks for tuning in. For personalized advice from Chris, head to delphi.ai/chrislowe and ask his digital mind.