This pattern is crazy, or I'm an idiot - Learning Domain-Driven Design by Vlad K [48:00-53:04]

a react template. I bought two, it is completely overkill. Oh, yeah. Well, just so you know, I just introduced, I just introduced search ranking. So this is another ridiculous thing where I'm glad we have transcripts from the episodes, which you can full text search those on the website. So if you want to see every time Carter's mentioned Disney, you know, you can find it and it tells you down to like the times did only a couple times. And um, or but but the the more important thing though is if we want to say, uh, I want to look up John Osterholt, right? Right before it would basically sort it by any mention of his last name, uh, from most recent episode back. And that's not actually probably what you want. You probably want the relevant score. So if I look up Osterholt, I probably want to see the episodes that he was in or the times of the episode that we had books by him that were read. And so now, if you type in Osterholt, that's exactly what happens. So there's a relevant score. If you're listed as an author as a guest, that gets listed higher than if you were just listed inside of like the, the text of the, this was just for me to be like, I don't know how to actually build this and write down and thought about it. And I was able to do it all with Postgres and some other kind of cool stuff. Um, and yeah, I'm learning as we go. And it's like, it's just been a really funny and fun thing of being like, wait, you can, we also have a public backlog now. And if you're a discord member, you can vote on books that you want to see next, which, um, right now, I think it's, I think it's the, uh, the tanya. Oh, what is it? Is it overdoing a tanya Riley next? Yeah, tanya Riley, the staff engineers path. That's the most popular book on a couple of backlogs. Or did I read staff and you write Will Larson? I can't remember which one I read. We read Will Larson one. Uh, but we, I think we were, we, so the thing is that you can propose books in our discord. And no, this is the other thing that's ridiculous. The proposed books in our discord have now made a discord bot that can go through and scrape all of those proposed books. And then I can decide whether we actually put them in the backlog or not. We keep, we keep track of the state of the ingest of like, did I accept it? Did I reject it? Did I defer it? It's so ridiculous. Um, I'm, I'm having a blast. Please, uh, please understand that all backlog boats are purely advisory. They are, and they are, and, and, and Carter and I both get 20 votes each, by the way. And so, um, early members, I think at five votes, we get 20 votes each. And these are advisory. Like we just, I, what I wanted to see was, is there public sentiment on books that we already had in our backlog, right? So, um, systems Bible by John Gaul, we know we want to read that at some point. Well, it's, it's number three on our, on our backlog booting system. So, we can look at this and, you know, prioritize, uh, based on that. And we know that at least some subset of our audience is going to be excited to have us cover it. Something else that you talk about in chapter 10 is this idea of like, you talk about heuristics, right? Which is like, okay, how do you know, like, we'll talk about bounded contexts, like subdomains in particular, right? Like, where does subdomain begin? Where does it end? Right? And the answer to that a lot is it depends. And I think his buddy was like, he quoted a friend of his who basically said like, there are lots of heuristics when trying to determine like what a subdomain is. He says, size is one of the least useful heuristics. Like, I like that. Subdomains just might be really big. Some might be really small, right? Um, I like this idea of heuristics. I, I think, um, judgment is, has always been important in software engineering, but again, taking a page out of Fred Books's, worldview, um, with medical man month, like, there's essential complexity and there's accidental complexity. And essential complexity is where a lot more judgment is required. You know, we actually had, it's interesting. We have now seen the same failure mode twice with our database during our big migration because we switched from Mongo to Postgres and so we had to write a bunch of SQL queries where, and like we've been using cloud to do all of this, right? We've been, we've been verifying, but like, you know, cloud's been writing a lot of code where cloud wrote two SQL queries that were so awful that if they got called in any sort of, you know, elevated capacity, it could take down the entire database. Um, and it was really interesting, like, because like some of the engineers are like, well, humans can write bad SQL queries. Like, of course, humans can write bad SQL queries. But the two failure modes we saw with this, a human wouldn't have made because the first one was just like this insanely complicated query to like get all this information we needed to, to return it all in the, in the right shape that we wanted. And at some point