Podcasts about Hubris

2. The debate continues with a comparison of Emperor Trump to Nero and Claudius, questioning if his current crisis is a result of bad luck or hubris. While Claudius favored low-risk, calculated campaigns, Trump's offensive is characterized as a "rash and incalculably risky gambit" that mirrors strategic failures in Ukraine. This conflict has solidified the Russia-Chinabond and left Israel "naked and exposed" due to US failures. Germanicus argues that the US ignored the "weak points" of its own coalition, turning Gulf State bases into liabilities rather than security assets. Likening Trump's overconfidence to Hitler's before the invasion of Russia, the speakers suggest that the US has "got suckered" into a war it cannot win through air power alone. They conclude that the only rational path is to accept defeat and reorganize, as the Romans did when facing superior Persian cavalry. (2)1680 CONSTANTINOPLE

“Hubris, Kate. He suffers from hubris!” We're on the cusp of spring, so full credit to Eric Carpenter for pointing out to us how egregious a gap we've had in our roster until now. Have we really and truly never done that spring book to beat all spring books Muncha Muncha Muncha??? Such a thing seems inconceivable and yet… here we are. Today Kate and Betsy discuss bunnies, munching, and the role that illustration plays when our own personal preferences come into it all. Candace Fleming's been having a stellar year (becoming the first person to receive the Children's Literature Legacy Award and the Margaret A. Edwards Award in the same year, in addition to her book Death in the Jungle winning the Award for Excellence in Nonfiction for Young Adults). Now she faces the ultimate challenge: Whether or not her picture book from 2002 is actually a classic.

Prince Andrew's 2019 interview with BBC Newsnight was intended to address the mounting controversy surrounding his relationship with Jeffrey Epstein, but it quickly became one of the most disastrous public relations moments in modern royal history. During the interview with Emily Maitlis, Andrew attempted to explain why he had remained friends with Epstein even after Epstein's 2008 conviction. Rather than distancing himself from the disgraced financier, Andrew described the relationship as a mistake but appeared to minimize the seriousness of Epstein's crimes. The interview also addressed allegations made by Virginia Giuffre, which Andrew categorically denied. Instead of quelling public concern, the interview drew widespread criticism for what many viewed as evasive answers, a lack of empathy toward Epstein's victims, and explanations that strained credibility.Several specific claims made by Andrew during the interview intensified the backlash. He asserted he had no memory of ever meeting Giuffre despite photographic evidence showing them together and suggested the photo might have been fabricated. He also offered unusual explanations—such as saying a medical condition prevented him from sweating—to challenge Giuffre's account of events. The tone of the interview, along with Andrew's continued defense of his decision to visit Epstein after the financier's conviction, was widely viewed as tone-deaf and damaging. The fallout was immediate: within days, Andrew stepped back from all public royal duties amid growing pressure from the public, media, and political figures. What had been intended as a chance to repair his reputation instead became a defining moment that cemented the perception that the scandal surrounding Epstein had permanently engulfed him.to contact me:bobbycapucci@protonmail.comBecome a supporter of this podcast: https://www.spreaker.com/podcast/the-epstein-chronicles--5003294/support.

Are we heading toward a future where the government "nationalizes" AI models? In this episode, we explore the high-stakes intersection of defense, finance, and the "nationalization" risk facing frontier AI companies.Welcome to the Alfalfa Podcast

Dr. Jason Fung is a Canadian nephrologist and leading voice in metabolic health, best known for making the science of fasting and insulin resistance simple, practical, and empowering. Through his books, lectures, and clinical work, he's helped thousands rethink weight loss, type 2 diabetes, and long-term health by focusing on hormones, not just calories. Dr. Fung is the co-founder of The Fasting Method and a sought-after educator on metabolic health. In this episode, Drs. Brian, Tro, and Jason talk about… (00:00) Intro (05:46) The new dietary guidelines and food pyramid (08:02) The Huger Code and understanding hunger (13:19) Why the calories-in/calories-out model for weight-loss is ineffective (17:44) Hedonic hunger (19:06) Conditioned hunger (24:41) Hormones and calories (28:15) Insulin and fat-burning (31:47) The process of digestion and how every step of the process impacts hormones and weight (38:08) While ultra-processed foods are SO much more obesogenic than whole foods (39:53) Food addiction and effective treatment (46:19) The 3 Golden Rules of Weight Loss (49:25) Dr. Fung's new book and masterclass! (Links below) (51:55) Human biology and flavor variety (57:09) Fasting and satiety (01:04:43) Hubris, pride, and ignorance in medicine (01:09:15) Outro For more information, please see the links below. Thank you for listening! Links:   Dr. Jason Fung: The Fasting Method: https://www.thefastingmethod.com/ Books: https://www.amazon.com/stores/author/B01BT8K6FK Website/Books: https://www.doctorjasonfung.com/ iG: https://www.instagram.com/drjasonfung/ X: https://x.com/drjasonfung YouTube: https://www.youtube.com/channel/UCoyL4iGArWn5Hu0V_sAhK2w The Hunger Code Pre-Order/Masterclass: https://www.doctorjasonfung.com/gift-with-purchase-offer Dr. Brian Lenzkes: Website: https://arizonametabolichealth.com/ Twitter: https://twitter.com/BrianLenzkes?ref_src=twsrc^google|twcamp^serp|twgr^author Dr. Tro Kalayjian: Website: https://toward.health Twitter: https://twitter.com/DoctorTro IG: https://www.instagram.com/doctortro/

Scott Anderson is a veteran foreign reporter and war correspondent, and a contributing writer for The New York Times. Over his career he has reported from Bosnia, Libya, Palestine and across the Middle East. In this episode, he spoke to host Hannah Lucinda Smith about his new book, King of Kings, a gripping account of the fall of the Shah of Iran, the 1979 Iranian Revolution and the rise of the Islamic Republic. Together, they explore the flaws that led to the Shah's downfall, and why Western powers fundamentally misunderstood what was happening in the country in the months before the revolution. They also examine how these events shaped Iran and the Middle East today, and the political future of a country whose power has been diminished in the region, but whose population is again rallying around the flag in response to external aggression. --- If you'd like to become a Member and get access to all our full ad free conversations, plus all of our Members-only content, just visit intelligencesquared.com/membership to find out more. For £4.99 per month you'll also receive: - Full-length and ad-free Intelligence Squared episodes, wherever you get your podcasts - Bonus Intelligence Squared podcasts, curated feeds and members exclusive series - 15% discount on livestreams and in-person tickets for all Intelligence Squared events  ...  Or Subscribe on Apple for £4.99: - Full-length and ad-free Intelligence Squared podcasts - Bonus Intelligence Squared podcasts, curated feeds and members exclusive series … Already a subscriber? Thank you for supporting our mission to foster honest debate and compelling conversations! Visit intelligencesquared.com to explore all your benefits including ad-free podcasts, exclusive bonus content and early access. … Subscribe to our newsletter here to hear about our latest events, discounts and much more. https://www.intelligencesquared.com/newsletter-signup/ Learn more about your ad choices. Visit podcastchoices.com/adchoices

Dans la tête des maîtres de l'iA.Que veulent vraiment ceux qui façonnent notre futur technologique ?Dans cet épisode, conversation sans filtre avec Guillaume Grallet, auteur du livre "Pionniers - Voyage aux frontières de l'intelligence artificielle" (Grasset, 2025) et rédacteur en chef sciences et tech au Point. Il a rencontré les figures les plus influentes de la tech mondiale.Il raconte ce qu'il a vu. Ce qu'il a compris. Et ce qui l'inquiète.De Mark Zuckerberg à Sam Altman, en passant par Dario Amodei, Yann LeCun, Jensen Huang ou Kai-Fu Lee : visions messianiques, doutes sincères, stratégie géopolitique, course à la puissance.Vie privée, climat, diversité linguistique, souveraineté : l'iA n'est pas qu'une course technologique, c'est une bataille culturelle et politique.Optimisme stratégique ou promesse dangereuse ?Hubris ou lucidité ?Un épisode pour comprendre ce qui se joue vraiment derrière les discours officiels.

Handel on the Law. Marginal Legal Advice.See omnystudio.com/listener for privacy information.

Bryan Cantrill is the co-founder and CTO of Oxide Computer Company. We discuss why the biggest cloud providers don't use off the shelf hardware, how scaling data centers at samsung's scale exposed problems with hard drive firmware, how the values of NodeJS are in conflict with robust systems, choosing Rust, and the benefits of Oxide Computer's rack scale approach. This is an extended version of an interview posted on Software Engineering Radio. Related links Oxide Computer Oxide and Friends Illumos Platform as a Reflection of Values RFD 26 bhyve CockroachDB Heterogeneous Computing with Raja Koduri Transcript You can help correct transcripts on GitHub. Intro [00:00:00] Jeremy: Today I am talking to Bryan Cantrill. He's the co-founder and CTO of Oxide computer company, and he was previously the CTO of Joyent and he also co-authored the DTrace Tracing framework while he was at Sun Microsystems. [00:00:14] Jeremy: Bryan, welcome to Software Engineering radio. [00:00:17] Bryan: Uh, awesome. Thanks for having me. It's great to be here. [00:00:20] Jeremy: You're the CTO of a company that makes computers. But I think before we get into that, a lot of people who built software, now that the actual computer is abstracted away, they're using AWS or they're using some kind of cloud service. So I thought we could start by talking about, data centers. [00:00:41] Jeremy: 'cause you were. Previously working at Joyent, and I believe you got bought by Samsung and you've previously talked about how you had to figure out, how do I run things at Samsung's scale. So how, how, how was your experience with that? What, what were the challenges there? Samsung scale and migrating off the cloud [00:01:01] Bryan: Yeah, I mean, so at Joyent, and so Joyent was a cloud computing pioneer. Uh, we competed with the likes of AWS and then later GCP and Azure. Uh, and we, I mean, we were operating at a scale, right? We had a bunch of machines, a bunch of dcs, but ultimately we know we were a VC backed company and, you know, a small company by the standards of, certainly by Samsung standards. [00:01:25] Bryan: And so when, when Samsung bought the company, I mean, the reason by the way that Samsung bought Joyent is Samsung's. Cloud Bill was, uh, let's just say it was extremely large. They were spending an enormous amount of money every year on, on the public cloud. And they realized that in order to secure their fate economically, they had to be running on their own infrastructure. [00:01:51] Bryan: It did not make sense. And there's not, was not really a product that Samsung could go buy that would give them that on-prem cloud. Uh, I mean in that, in that regard, like the state of the market was really no different. And so they went looking for a company, uh, and bought, bought Joyent. And when we were on the inside of Samsung. [00:02:11] Bryan: That we learned about Samsung scale. And Samsung loves to talk about Samsung scale. And I gotta tell you, it is more than just chest thumping. Like Samsung Scale really is, I mean, just the, the sheer, the number of devices, the number of customers, just this absolute size. they really wanted to take us out to, to levels of scale, certainly that we had not seen. [00:02:31] Bryan: The reason for buying Joyent was to be able to stand up on their own infrastructure so that we were gonna go buy, we did go buy a bunch of hardware. Problems with server hardware at scale [00:02:40] Bryan: And I remember just thinking, God, I hope Dell is somehow magically better. I hope the problems that we have seen in the small, we just. You know, I just remember hoping and hope is hope. It was of course, a terrible strategy and it was a terrible strategy here too. Uh, and the we that the problems that we saw at the large were, and when you scale out the problems that you see kind of once or twice, you now see all the time and they become absolutely debilitating. [00:03:12] Bryan: And we saw a whole series of really debilitating problems. I mean, many ways, like comically debilitating, uh, in terms of, of showing just how bad the state-of-the-art. Yes. And we had, I mean, it should be said, we had great software and great software expertise, um, and we were controlling our own system software. [00:03:35] Bryan: But even controlling your own system software, your own host OS, your own control plane, which is what we had at Joyent, ultimately, you're pretty limited. You go, I mean, you got the problems that you can obviously solve, the ones that are in your own software, but the problems that are beneath you, the, the problems that are in the hardware platform, the problems that are in the componentry beneath you become the problems that are in the firmware. IO latency due to hard drive firmware [00:04:00] Bryan: Those problems become unresolvable and they are deeply, deeply frustrating. Um, and we just saw a bunch of 'em again, they were. Comical in retrospect, and I'll give you like a, a couple of concrete examples just to give, give you an idea of what kinda what you're looking at. one of the, our data centers had really pathological IO latency. [00:04:23] Bryan: we had a very, uh, database heavy workload. And this was kind of right at the period where you were still deploying on rotating media on hard drives. So this is like, so. An all flash buy did not make economic sense when we did this in, in 2016. This probably, it'd be interesting to know like when was the, the kind of the last time that that actual hard drives made sense? [00:04:50] Bryan: 'cause I feel this was close to it. So we had a, a bunch of, of a pathological IO problems, but we had one data center in which the outliers were actually quite a bit worse and there was so much going on in that system. It took us a long time to figure out like why. And because when, when you, when you're io when you're seeing worse io I mean you're naturally, you wanna understand like what's the workload doing? [00:05:14] Bryan: You're trying to take a first principles approach. What's the workload doing? So this is a very intensive database workload to support the, the object storage system that we had built called Manta. And that the, the metadata tier was stored and uh, was we were using Postgres for that. And that was just getting absolutely slaughtered. [00:05:34] Bryan: Um, and ultimately very IO bound with these kind of pathological IO latencies. Uh, and as we, you know, trying to like peel away the layers to figure out what was going on. And I finally had this thing. So it's like, okay, we are seeing at the, at the device layer, at the at, at the disc layer, we are seeing pathological outliers in this data center that we're not seeing anywhere else. [00:06:00] Bryan: And that does not make any sense. And the thought occurred to me. I'm like, well, maybe we are. Do we have like different. Different rev of firmware on our HGST drives, HGST. Now part of WD Western Digital were the drives that we had everywhere. And, um, so maybe we had a different, maybe I had a firmware bug. [00:06:20] Bryan: I, this would not be the first time in my life at all that I would have a drive firmware issue. Uh, and I went to go pull the firmware, rev, and I'm like, Toshiba makes hard drives? So we had, I mean. I had no idea that Toshiba even made hard drives, let alone that they were our, they were in our data center. [00:06:38] Bryan: I'm like, what is this? And as it turns out, and this is, you know, part of the, the challenge when you don't have an integrated system, which not to pick on them, but Dell doesn't, and what Dell would routinely put just sub make substitutes, and they make substitutes that they, you know, it's kind of like you're going to like, I don't know, Instacart or whatever, and they're out of the thing that you want. [00:07:03] Bryan: So, you know, you're, someone makes a substitute and like sometimes that's okay, but it's really not okay in a data center. And you really want to develop and validate a, an end-to-end integrated system. And in this case, like Toshiba doesn't, I mean, Toshiba does make hard drives, but they are a, or the data they did, uh, they basically were, uh, not competitive and they were not competitive in part for the reasons that we were discovering. [00:07:29] Bryan: They had really serious firmware issues. So the, these were drives that would just simply stop a, a stop acknowledging any reads from the order of 2,700 milliseconds. Long time, 2.7 seconds. Um. And that was a, it was a drive firmware issue, but it was highlighted like a much deeper issue, which was the simple lack of control that we had over our own destiny. [00:07:53] Bryan: Um, and it's an, it's, it's an example among many where Dell is making a decision. That lowers the cost of what they are providing you marginally, but it is then giving you a system that they shouldn't have any confidence in because it's not one that they've actually designed and they leave it to the customer, the end user, to make these discoveries. [00:08:18] Bryan: And these things happen up and down the stack. And for every, for whether it's, and, and not just to pick on Dell because it's, it's true for HPE, it's true for super micro, uh, it's true for your switch vendors. It's, it's true for storage vendors where the, the, the, the one that is left actually integrating these things and trying to make the the whole thing work is the end user sitting in their data center. AWS / Google are not buying off the shelf hardware but you can't use it [00:08:42] Bryan: There's not a product that they can buy that gives them elastic infrastructure, a cloud in their own DC The, the product that you buy is the public cloud. Like when you go in the public cloud, you don't worry about the stuff because that it's, it's AWS's issue or it's GCP's issue. And they are the ones that get this to ground. [00:09:02] Bryan: And they, and this was kind of, you know, the eye-opening moment. Not a surprise. Uh, they are not Dell customers. They're not HPE customers. They're not super micro customers. They have designed their own machines. And to varying degrees, depending on which one you're looking at. But they've taken the clean sheet of paper and the frustration that we had kind of at Joyent and beginning to wonder and then Samsung and kind of wondering what was next, uh, is that, that what they built was not available for purchase in the data center. [00:09:35] Bryan: You could only rent it in the public cloud. And our big belief is that public cloud computing is a really important revolution in infrastructure. Doesn't feel like a different, a deep thought, but cloud computing is a really important revolution. It shouldn't only be available to rent. You should be able to actually buy it. [00:09:53] Bryan: And there are a bunch of reasons for doing that. Uh, one in the one we we saw at Samsung is economics, which I think is still the dominant reason where it just does not make sense to rent all of your compute in perpetuity. But there are other reasons too. There's security, there's risk management, there's latency. [00:10:07] Bryan: There are a bunch of reasons why one might wanna to own one's own infrastructure. But, uh, that was very much the, the, so the, the genesis for oxide was coming out of this very painful experience and a painful experience that, because, I mean, a long answer to your question about like what was it like to be at Samsung scale? [00:10:27] Bryan: Those are the kinds of things that we, I mean, in our other data centers, we didn't have Toshiba drives. We only had the HDSC drives, but it's only when you get to this larger scale that you begin to see some of these pathologies. But these pathologies then are really debilitating in terms of those who are trying to develop a service on top of them. [00:10:45] Bryan: So it was, it was very educational in, in that regard. And you're very grateful for the experience at Samsung in terms of opening our eyes to the challenge of running at that kind of scale. [00:10:57] Jeremy: Yeah, because I, I think as software engineers, a lot of times we, we treat the hardware as a, as a given where, [00:11:08] Bryan: Yeah. [00:11:08] Bryan: Yeah. There's software in chard drives [00:11:09] Jeremy: It sounds like in, in this case, I mean, maybe the issue is not so much that. Dell or HP as a company doesn't own every single piece that they're providing you, but rather the fact that they're swapping pieces in and out without advertising them, and then when it becomes a problem, they're not necessarily willing to, to deal with the, the consequences of that. [00:11:34] Bryan: They just don't know. I mean, I think they just genuinely don't know. I mean, I think that they, it's not like they're making a deliberate decision to kind of ship garbage. It's just that they are making, I mean, I think it's exactly what you said about like, not thinking about the hardware. It's like, what's a hard drive? [00:11:47] Bryan: Like what's it, I mean, it's a hard drive. It's got the same specs as this other hard drive and Intel. You know, it's a little bit cheaper, so why not? It's like, well, like there's some reasons why not, and one of the reasons why not is like, uh, even a hard drive, whether it's rotating media or, or flash, like that's not just hardware. [00:12:05] Bryan: There's software in there. And that the software's like not the same. I mean, there are components where it's like, there's actually, whether, you know, if, if you're looking at like a resistor or a capacitor or something like this Yeah. If you've got two, two parts that are within the same tolerance. Yeah. [00:12:19] Bryan: Like sure. Maybe, although even the EEs I think would be, would be, uh, objecting that a little bit. But the, the, the more complicated you get, and certainly once you get to the, the, the, the kind of the hardware that we think of like a, a, a microprocessor, a a network interface card, a a, a hard driver, an NVME drive. [00:12:38] Bryan: Those things are super complicated and there's a whole bunch of software inside of those things, the firmware, and that's the stuff that, that you can't, I mean, you say that software engineers don't think about that. It's like you, no one can really think about that because it's proprietary that's kinda welded shut and you've got this abstraction into it. [00:12:55] Bryan: But the, the way that thing operates is very core to how the thing in aggregate will behave. And I think that you, the, the kind of, the, the fundamental difference between Oxide's approach and the approach that you get at a Dell HP Supermicro, wherever, is really thinking holistically in terms of hardware and software together in a system that, that ultimately delivers cloud computing to a user. [00:13:22] Bryan: And there's a lot of software at many, many, many, many different layers. And it's very important to think about, about that software and that hardware holistically as a single system. [00:13:34] Jeremy: And during that time at Joyent, when you experienced some of these issues, was it more of a case of you didn't have enough servers experiencing this? So if it would happen, you might say like, well, this one's not working, so maybe we'll just replace the hardware. What, what was the thought process when you were working at that smaller scale and, and how did these issues affect you? UEFI / Baseboard Management Controller [00:13:58] Bryan: Yeah, at the smaller scale, you, uh, you see fewer of them, right? You just see it's like, okay, we, you know, what you might see is like, that's weird. We kinda saw this in one machine versus seeing it in a hundred or a thousand or 10,000. Um, so you just, you just see them, uh, less frequently as a result, they are less debilitating. [00:14:16] Bryan: Um, I, I think that it's, when you go to that larger scale, those things that become, that were unusual now become routine and they become debilitating. Um, so it, it really is in many regards a function of scale. Uh, and then I think it was also, you know, it was a little bit dispiriting that kind of the substrate we were building on really had not improved. [00:14:39] Bryan: Um, and if you look at, you know, the, if you buy a computer server, buy an x86 server. There is a very low layer of firmware, the BIOS, the basic input output system, the UEFI BIOS, and this is like an abstraction layer that has, has existed since the eighties and hasn't really meaningfully improved. Um, the, the kind of the transition to UEFI happened with, I mean, I, I ironically with Itanium, um, you know, two decades ago. [00:15:08] Bryan: but beyond that, like this low layer, this lowest layer of platform enablement software is really only impeding the operability of the system. Um, you look at the baseboard management controller, which is the kind of the computer within the computer, there is a, uh, there is an element in the machine that needs to handle environmentals, that needs to handle, uh, operate the fans and so on. [00:15:31] Bryan: Uh, and that traditionally has this, the space board management controller, and that architecturally just hasn't improved in the last two decades. And, you know, that's, it's a proprietary piece of silicon. Generally from a company that no one's ever heard of called a Speed, uh, which has to be, is written all on caps, so I guess it needs to be screamed. [00:15:50] Bryan: Um, a speed has a proprietary part that has a, there is a root password infamously there, is there, the root password is encoded effectively in silicon. So, uh, which is just, and for, um, anyone who kind of goes deep into these things, like, oh my God, are you kidding me? Um, when we first started oxide, the wifi password was a fraction of the a speed root password for the bmc. [00:16:16] Bryan: It's kinda like a little, little BMC humor. Um, but those things, it was just dispiriting that, that the, the state-of-the-art was still basically personal computers running in the data center. Um, and that's part of what, what was the motivation for doing something new? [00:16:32] Jeremy: And for the people using these systems, whether it's the baseboard management controller or it's the The BIOS or UF UEFI component, what are the actual problems that people are seeing seen? Security vulnerabilities and poor practices in the BMC [00:16:51] Bryan: Oh man, I, the, you are going to have like some fraction of your listeners, maybe a big fraction where like, yeah, like what are the problems? That's a good question. And then you're gonna have the people that actually deal with these things who are, did like their heads already hit the desk being like, what are the problems? [00:17:06] Bryan: Like what are the non problems? Like what, what works? Actually, that's like a shorter answer. Um, I mean, there are so many problems and a lot of it is just like, I mean, there are problems just architecturally these things are just so, I mean, and you could, they're the problems spread to the horizon, so you can kind of start wherever you want. [00:17:24] Bryan: But I mean, as like, as a really concrete example. Okay, so the, the BMCs that, that the computer within the computer that needs to be on its own network. So you now have like not one network, you got two networks that, and that network, by the way, it, that's the network that you're gonna log into to like reset the machine when it's otherwise unresponsive. [00:17:44] Bryan: So that going into the BMC, you can are, you're able to control the entire machine. Well it's like, alright, so now I've got a second net network that I need to manage. What is running on the BMC? Well, it's running some. Ancient, ancient version of Linux it that you got. It's like, well how do I, how do I patch that? [00:18:02] Bryan: How do I like manage the vulnerabilities with that? Because if someone is able to root your BMC, they control the system. So it's like, this is not you've, and now you've gotta go deal with all of the operational hair around that. How do you upgrade that system updating the BMC? I mean, it's like you've got this like second shadow bad infrastructure that you have to go manage. [00:18:23] Bryan: Generally not open source. There's something called open BMC, um, which, um, you people use to varying degrees, but you're generally stuck with the proprietary BMC, so you're generally stuck with, with iLO from HPE or iDRAC from Dell or, or, uh, the, uh, su super micros, BMC, that H-P-B-M-C, and you are, uh, it is just excruciating pain. [00:18:49] Bryan: Um, and that this is assuming that by the way, that everything is behaving correctly. The, the problem is that these things often don't behave correctly, and then the consequence of them not behaving correctly. It's really dire because it's at that lowest layer of the system. So, I mean, I'll give you a concrete example. [00:19:07] Bryan: a customer of theirs reported to me, so I won't disclose the vendor, but let's just say that a well-known vendor had an issue with their, their temperature sensors were broken. Um, and the thing would always read basically the wrong value. So it was the BMC that had to like, invent its own ki a different kind of thermal control loop. [00:19:28] Bryan: And it would index on the, on the, the, the, the actual inrush current. It would, they would look at that at the current that's going into the CPU to adjust the fan speed. That's a great example of something like that's a, that's an interesting idea. That doesn't work. 'cause that's actually not the temperature. [00:19:45] Bryan: So like that software would crank the fans whenever you had an inrush of current and this customer had a workload that would spike the current and by it, when it would spike the current, the, the, the fans would kick up and then they would slowly degrade over time. Well, this workload was spiking the current faster than the fans would degrade, but not fast enough to actually heat up the part. [00:20:08] Bryan: And ultimately over a very long time, in a very painful investigation, it's customer determined that like my fans are cranked in my data center for no reason. We're blowing cold air. And it's like that, this is on the order of like a hundred watts, a server of, of energy that you shouldn't be spending and like that ultimately what that go comes down to this kind of broken software hardware interface at the lowest layer that has real meaningful consequence, uh, in terms of hundreds of kilowatts, um, across a data center. So this stuff has, has very, very, very real consequence and it's such a shadowy world. Part of the reason that, that your listeners that have dealt with this, that our heads will hit the desk is because it is really aggravating to deal with problems with this layer. [00:21:01] Bryan: You, you feel powerless. You don't control or really see the software that's on them. It's generally proprietary. You are relying on your vendor. Your vendor is telling you that like, boy, I don't know. You're the only customer seeing this. I mean, the number of times I have heard that for, and I, I have pledged that we're, we're not gonna say that at oxide because it's such an unaskable thing to say like, you're the only customer saying this. [00:21:25] Bryan: It's like, it feels like, are you blaming me for my problem? Feels like you're blaming me for my problem? Um, and what you begin to realize is that to a degree, these folks are speaking their own truth because the, the folks that are running at real scale at Hyperscale, those folks aren't Dell, HP super micro customers. [00:21:46] Bryan: They're actually, they've done their own thing. So it's like, yeah, Dell's not seeing that problem, um, because they're not running at the same scale. Um, but when you do run, you only have to run at modest scale before these things just become. Overwhelming in terms of the, the headwind that they present to people that wanna deploy infrastructure. The problem is felt with just a few racks [00:22:05] Jeremy: Yeah, so maybe to help people get some perspective at, at what point do you think that people start noticing or start feeling these problems? Because I imagine that if you're just have a few racks or [00:22:22] Bryan: do you have a couple racks or the, or do you wonder or just wondering because No, no, no. I would think, I think anyone who deploys any number of servers, especially now, especially if your experience is only in the cloud, you're gonna be like, what the hell is this? I mean, just again, just to get this thing working at all. [00:22:39] Bryan: It is so it, it's so hairy and so congealed, right? It's not designed. Um, and it, it, it, it's accreted it and it's so obviously accreted that you are, I mean, nobody who is setting up a rack of servers is gonna think to themselves like, yes, this is the right way to go do it. This all makes sense because it's, it's just not, it, I, it feels like the kit, I mean, kit car's almost too generous because it implies that there's like a set of plans to work to in the end. [00:23:08] Bryan: Uh, I mean, it, it, it's a bag of bolts. It's a bunch of parts that you're putting together. And so even at the smallest scales, that stuff is painful. Just architecturally, it's painful at the small scale then, but at least you can get it working. I think the stuff that then becomes debilitating at larger scale are the things that are, are worse than just like, I can't, like this thing is a mess to get working. [00:23:31] Bryan: It's like the, the, the fan issue that, um, where you are now seeing this over, you know, hundreds of machines or thousands of machines. Um, so I, it is painful at more or less all levels of scale. There's, there is no level at which the, the, the pc, which is really what this is, this is a, the, the personal computer architecture from the 1980s and there is really no level of scale where that's the right unit. Running elastic infrastructure is the hardware but also, hypervisor, distributed database, api, etc [00:23:57] Bryan: I mean, where that's the right thing to go deploy, especially if what you are trying to run. Is elastic infrastructure, a cloud. Because the other thing is like we, we've kinda been talking a lot about that hardware layer. Like hardware is, is just the start. Like you actually gotta go put software on that and actually run that as elastic infrastructure. [00:24:16] Bryan: So you need a hypervisor. Yes. But you need a lot more than that. You, you need to actually, you, you need a distributed database, you need web endpoints. You need, you need a CLI, you need all the stuff that you need to actually go run an actual service of compute or networking or storage. I mean, and for, for compute, even for compute, there's a ton of work to be done. [00:24:39] Bryan: And compute is by far, I would say the simplest of the, of the three. When you look at like networks, network services, storage services, there's a whole bunch of stuff that you need to go build in terms of distributed systems to actually offer that as a cloud. So it, I mean, it is painful at more or less every LE level if you are trying to deploy cloud computing on. What's a control plane? [00:25:00] Jeremy: And for someone who doesn't have experience building or working with this type of infrastructure, when you talk about a control plane, what, what does that do in the context of this system? [00:25:16] Bryan: So control plane is the thing that is, that is everything between your API request and that infrastructure actually being acted upon. So you go say, Hey, I, I want a provision, a vm. Okay, great. We've got a whole bunch of things we're gonna provision with that. We're gonna provision a vm, we're gonna get some storage that's gonna go along with that, that's got a network storage service that's gonna come out of, uh, we've got a virtual network that we're gonna either create or attach to. [00:25:39] Bryan: We've got a, a whole bunch of things we need to go do for that. For all of these things, there are metadata components that need, we need to keep track of this thing that, beyond the actual infrastructure that we create. And then we need to go actually, like act on the actual compute elements, the hostos, what have you, the switches, what have you, and actually go. [00:25:56] Bryan: Create these underlying things and then connect them. And there's of course, the challenge of just getting that working is a big challenge. Um, but getting that working robustly, getting that working is, you know, when you go to provision of vm, um, the, all the, the, the steps that need to happen and what happens if one of those steps fails along the way? [00:26:17] Bryan: What happens if, you know, one thing we're very mindful of is these kind of, you get these long tails of like, why, you know, generally our VM provisioning happened within this time, but we get these long tails where it takes much longer. What's going on? What, where in this process are we, are we actually spending time? [00:26:33] Bryan: Uh, and there's a whole lot of complexity that you need to go deal with that. There's a lot of complexity that you need to go deal with this effectively, this workflow that's gonna go create these things and manage them. Um, we use a, a pattern that we call, that are called sagas, actually is a, is a database pattern from the eighties. [00:26:51] Bryan: Uh, Katie McCaffrey is a, is a database reCrcher who, who, uh, I, I think, uh, reintroduce the idea of, of sagas, um, in the last kind of decade. Um, and this is something that we picked up, um, and I've done a lot of really interesting things with, um, to allow for, to this kind of, these workflows to be, to be managed and done so robustly in a way that you can restart them and so on. [00:27:16] Bryan: Uh, and then you guys, you get this whole distributed system that can do all this. That whole distributed system, that itself needs to be reliable and available. So if you, you know, you need to be able to, what happens if you, if you pull a sled or if a sled fails, how does the system deal with that? [00:27:33] Bryan: How does the system deal with getting an another sled added to the system? Like how do you actually grow this distributed system? And then how do you update it? How do you actually go from one version to the next? And all of that has to happen across an air gap where this is gonna run as part of the computer. [00:27:49] Bryan: So there are, it, it is fractally complicated. There, there is a lot of complexity here in, in software, in the software system and all of that. We kind of, we call the control plane. Um, and it, this is the what exists at AWS at GCP, at Azure. When you are hitting an endpoint that's provisioning an EC2 instance for you. [00:28:10] Bryan: There is an AWS control plane that is, is doing all of this and has, uh, some of these similar aspects and certainly some of these similar challenges. Are vSphere / Proxmox / Hyper-V in the same category? [00:28:20] Jeremy: And for people who have run their own servers with something like say VMware or Hyper V or Proxmox, are those in the same category? [00:28:32] Bryan: Yeah, I mean a little bit. I mean, it kind of like vSphere Yes. Via VMware. No. So it's like you, uh, VMware ESX is, is kind of a key building block upon which you can build something that is a more meaningful distributed system. When it's just like a machine that you're provisioning VMs on, it's like, okay, well that's actually, you as the human might be the control plane. [00:28:52] Bryan: Like, that's, that, that's, that's a much easier problem. Um, but when you've got, you know, tens, hundreds, thousands of machines, you need to do it robustly. You need something to coordinate that activity and you know, you need to pick which sled you land on. You need to be able to move these things. You need to be able to update that whole system. [00:29:06] Bryan: That's when you're getting into a control plane. So, you know, some of these things have kind of edged into a control plane, certainly VMware. Um, now Broadcom, um, has delivered something that's kind of cloudish. Um, I think that for folks that are truly born on the cloud, it, it still feels somewhat, uh, like you're going backwards in time when you, when you look at these kind of on-prem offerings. [00:29:29] Bryan: Um, but, but it, it, it's got these aspects to it for sure. Um, and I think that we're, um, some of these other things when you're just looking at KVM or just looks looking at Proxmox you kind of need to, to connect it to other broader things to turn it into something that really looks like manageable infrastructure. [00:29:47] Bryan: And then many of those projects are really, they're either proprietary projects, uh, proprietary products like vSphere, um, or you are really dealing with open source projects that are. Not necessarily aimed at the same level of scale. Um, you know, you look at a, again, Proxmox or, uh, um, you'll get an OpenStack. [00:30:05] Bryan: Um, and you know, OpenStack is just a lot of things, right? I mean, OpenStack has got so many, the OpenStack was kind of a, a free for all, for every infrastructure vendor. Um, and I, you know, there was a time people were like, don't you, aren't you worried about all these companies together that, you know, are coming together for OpenStack? [00:30:24] Bryan: I'm like, haven't you ever worked for like a company? Like, companies don't get along. By the way, it's like having multiple companies work together on a thing that's bad news, not good news. And I think, you know, one of the things that OpenStack has definitely struggled with, kind of with what, actually the, the, there's so many different kind of vendor elements in there that it's, it's very much not a product, it's a project that you're trying to run. [00:30:47] Bryan: But that's, but that very much is in, I mean, that's, that's similar certainly in spirit. [00:30:53] Jeremy: And so I think this is kind of like you're alluding to earlier, the piece that allows you to allocate, compute, storage, manage networking, gives you that experience of I can go to a web console or I can use an API and I can spin up machines, get them all connected. At the end of the day, the control plane. Is allowing you to do that in hopefully a user-friendly way. [00:31:21] Bryan: That's right. Yep. And in the, I mean, in order to do that in a modern way, it's not just like a user-friendly way. You really need to have a CLI and a web UI and an API. Those all need to be drawn from the same kind of single ground truth. Like you don't wanna have any of those be an afterthought for the other. [00:31:39] Bryan: You wanna have the same way of generating all of those different endpoints and, and entries into the system. Building a control plane now has better tools (Rust, CockroachDB) [00:31:46] Jeremy: And if you take your time at Joyent as an example. What kind of tools existed for that versus how much did you have to build in-house for as far as the hypervisor and managing the compute and all that? [00:32:02] Bryan: Yeah, so we built more or less everything in house. I mean, what you have is, um, and I think, you know, over time we've gotten slightly better tools. Um, I think, and, and maybe it's a little bit easier to talk about the, kind of the tools we started at Oxide because we kind of started with a, with a clean sheet of paper at oxide. [00:32:16] Bryan: We wanted to, knew we wanted to go build a control plane, but we were able to kind of go revisit some of the components. So actually, and maybe I'll, I'll talk about some of those changes. So when we, at, For example, at Joyent, when we were building a cloud at Joyent, there wasn't really a good distributed database. [00:32:34] Bryan: Um, so we were using Postgres as our database for metadata and there were a lot of challenges. And Postgres is not a distributed database. It's running. With a primary secondary architecture, and there's a bunch of issues there, many of which we discovered the hard way. Um, when we were coming to oxide, you have much better options to pick from in terms of distributed databases. [00:32:57] Bryan: You know, we, there was a period that now seems maybe potentially brief in hindsight, but of a really high quality open source distributed databases. So there were really some good ones to, to pick from. Um, we, we built on CockroachDB on CRDB. Um, so that was a really important component. That we had at oxide that we didn't have at Joyent. [00:33:19] Bryan: Um, so we were, I wouldn't say we were rolling our own distributed database, we were just using Postgres and uh, and, and dealing with an enormous amount of pain there in terms of the surround. Um, on top of that, and, and, you know, a, a control plane is much more than a database, obviously. Uh, and you've gotta deal with, uh, there's a whole bunch of software that you need to go, right. [00:33:40] Bryan: Um, to be able to, to transform these kind of API requests into something that is reliable infrastructure, right? And there, there's a lot to that. Uh, especially when networking gets in the mix, when storage gets in the mix, uh, there are a whole bunch of like complicated steps that need to be done, um, at Joyent. [00:33:59] Bryan: Um, we, in part because of the history of the company and like, look. This, this just is not gonna sound good, but it just is what it is and I'm just gonna own it. We did it all in Node, um, at Joyent, which I, I, I know it sounds really right now, just sounds like, well, you, you built it with Tinker Toys. You Okay. [00:34:18] Bryan: Uh, did, did you think it was, you built the skyscraper with Tinker Toys? Uh, it's like, well, okay. We actually, we had greater aspirations for the Tinker Toys once upon a time, and it was better than, you know, than Twisted Python and Event Machine from Ruby, and we weren't gonna do it in Java. All right. [00:34:32] Bryan: So, but let's just say that that experiment, uh, that experiment did ultimately end in a predictable fashion. Um, and, uh, we, we decided that maybe Node was not gonna be the best decision long term. Um, Joyent was the company behind node js. Uh, back in the day, Ryan Dahl worked for Joyent. Uh, and then, uh, then we, we, we. [00:34:53] Bryan: Uh, landed that in a foundation in about, uh, what, 2015, something like that. Um, and began to consider our world beyond, uh, beyond Node. Rust at Oxide [00:35:04] Bryan: A big tool that we had in the arsenal when we started Oxide is Rust. Um, and so indeed the name of the company is, is a tip of the hat to the language that we were pretty sure we were gonna be building a lot of stuff in. [00:35:16] Bryan: Namely Rust. And, uh, rust is, uh, has been huge for us, a very important revolution in programming languages. you know, there, there, there have been different people kind of coming in at different times and I kinda came to Rust in what I, I think is like this big kind of second expansion of rust in 2018 when a lot of technologists were think, uh, sick of Node and also sick of Go. [00:35:43] Bryan: And, uh, also sick of C++. And wondering is there gonna be something that gives me the, the, the performance, of that I get outta C. The, the robustness that I can get out of a C program but is is often difficult to achieve. but can I get that with kind of some, some of the velocity of development, although I hate that term, some of the speed of development that you get out of a more interpreted language. [00:36:08] Bryan: Um, and then by the way, can I actually have types, I think types would be a good idea? Uh, and rust obviously hits the sweet spot of all of that. Um, it has been absolutely huge for us. I mean, we knew when we started the company again, oxide, uh, we were gonna be using rust in, in quite a, quite a. Few places, but we weren't doing it by fiat. [00:36:27] Bryan: Um, we wanted to actually make sure we're making the right decision, um, at, at every different, at every layer. Uh, I think what has been surprising is the sheer number of layers at which we use rust in terms of, we've done our own embedded firmware in rust. We've done, um, in, in the host operating system, which is still largely in C, but very big components are in rust. [00:36:47] Bryan: The hypervisor Propolis is all in rust. Uh, and then of course the control plane, that distributed system on that is all in rust. So that was a very important thing that we very much did not need to build ourselves. We were able to really leverage, uh, a terrific community. Um. We were able to use, uh, and we've done this at Joyent as well, but at Oxide, we've used Illumos as a hostos component, which, uh, our variant is called Helios. [00:37:11] Bryan: Um, we've used, uh, bhyve um, as a, as as that kind of internal hypervisor component. we've made use of a bunch of different open source components to build this thing, um, which has been really, really important for us. Uh, and open source components that didn't exist even like five years prior. [00:37:28] Bryan: That's part of why we felt that 2019 was the right time to start the company. And so we started Oxide. The problems building a control plane in Node [00:37:34] Jeremy: You had mentioned that at Joyent, you had tried to build this in, in Node. What were the, what were the, the issues or the, the challenges that you had doing that? [00:37:46] Bryan: Oh boy. Yeah. again, we, I kind of had higher hopes in 2010, I would say. When we, we set on this, um, the, the, the problem that we had just writ large, um. JavaScript is really designed to allow as many people on earth to write a program as possible, which is good. I mean, I, I, that's a, that's a laudable goal. [00:38:09] Bryan: That is the goal ultimately of such as it is of JavaScript. It's actually hard to know what the goal of JavaScript is, unfortunately, because Brendan Ike never actually wrote a book. so that there is not a canonical, you've got kind of Doug Crockford and other people who've written things on JavaScript, but it's hard to know kind of what the original intent of JavaScript is. [00:38:27] Bryan: The name doesn't even express original intent, right? It was called Live Script, and it was kind of renamed to JavaScript during the Java Frenzy of the late nineties. A name that makes no sense. There is no Java in JavaScript. that is kind of, I think, revealing to kind of the, uh, the unprincipled mess that is JavaScript. [00:38:47] Bryan: It, it, it's very pragmatic at some level, um, and allows anyone to, it makes it very easy to write software. The problem is it's much more difficult to write really rigorous software. So, uh, and this is what I should differentiate JavaScript from TypeScript. This is really what TypeScript is trying to solve. [00:39:07] Bryan: TypeScript is like. How can, I think TypeScript is a, is a great step forward because TypeScript is like, how can we bring some rigor to this? Like, yes, it's great that it's easy to write JavaScript, but that's not, we, we don't wanna do that for Absolutely. I mean that, that's not the only problem we solve. [00:39:23] Bryan: We actually wanna be able to write rigorous software and it's actually okay if it's a little harder to write rigorous software that's actually okay if it gets leads to, to more rigorous artifacts. Um, but in JavaScript, I mean, just a concrete example. You know, there's nothing to prevent you from referencing a property that doesn't actually exist in JavaScript. [00:39:43] Bryan: So if you fat finger a property name, you are relying on something to tell you. By the way, I think you've misspelled this because there is no type definition for this thing. And I don't know that you've got one that's spelled correctly, one that's spelled incorrectly, that's often undefined. And then the, when you actually go, you say you've got this typo that is lurking in your what you want to be rigorous software. [00:40:07] Bryan: And if you don't execute that code, like you won't know that's there. And then you do execute that code. And now you've got a, you've got an undefined object. And now that's either gonna be an exception or it can, again, depends on how that's handled. It can be really difficult to determine the origin of that, of, of that error, of that programming. [00:40:26] Bryan: And that is a programmer error. And one of the big challenges that we had with Node is that programmer errors and operational errors, like, you know, I'm out of disk space as an operational error. Those get conflated and it becomes really hard. And in fact, I think the, the language wanted to make it easier to just kind of, uh, drive on in the event of all errors. [00:40:53] Bryan: And it's like, actually not what you wanna do if you're trying to build a reliable, robust system. So we had. No end of issues. [00:41:01] Bryan: We've got a lot of experience developing rigorous systems, um, again coming out of operating systems development and so on. And we want, we brought some of that rigor, if strangely, to JavaScript. So one of the things that we did is we brought a lot of postmortem, diagnos ability and observability to node. [00:41:18] Bryan: And so if, if one of our node processes. Died in production, we would actually get a core dump from that process, a core dump that we could actually meaningfully process. So we did a bunch of kind of wild stuff. I mean, actually wild stuff where we could actually make sense of the JavaScript objects in a binary core dump. JavaScript values ease of getting started over robustness [00:41:41] Bryan: Um, and things that we thought were really important, and this is the, the rest of the world just looks at this being like, what the hell is this? I mean, it's so out of step with it. The problem is that we were trying to bridge two disconnected cultures of one developing really. Rigorous software and really designing it for production, diagnosability and the other, really designing it to software to run in the browser and for anyone to be able to like, you know, kind of liven up a webpage, right? [00:42:10] Bryan: Is kinda the origin of, of live script and then JavaScript. And we were kind of the only ones sitting at the intersection of that. And you begin when you are the only ones sitting at that kind of intersection. You just are, you're, you're kind of fighting a community all the time. And we just realized that we are, there were so many things that the community wanted to do that we felt are like, no, no, this is gonna make software less diagnosable. It's gonna make it less robust. The NodeJS split and why people left [00:42:36] Bryan: And then you realize like, I'm, we're the only voice in the room because we have got, we have got desires for this language that it doesn't have for itself. And this is when you realize you're in a bad relationship with software. It's time to actually move on. And in fact, actually several years after, we'd already kind of broken up with node. [00:42:55] Bryan: Um, and it was like, it was a bit of an acrimonious breakup. there was a, uh, famous slash infamous fork of node called IoJS Um, and this was viewed because people, the community, thought that Joyent was being what was not being an appropriate steward of node js and was, uh, not allowing more things to come into to, to node. [00:43:19] Bryan: And of course, the reason that we of course, felt that we were being a careful steward and we were actively resisting those things that would cut against its fitness for a production system. But it's some way the community saw it and they, and forked, um, and, and I think the, we knew before the fork that's like, this is not working and we need to get this thing out of our hands. Platform is a reflection of values node summit talk [00:43:43] Bryan: And we're are the wrong hands for this? This needs to be in a foundation. Uh, and so we kind of gone through that breakup, uh, and maybe it was two years after that. That, uh, friend of mine who was um, was running the, uh, the node summit was actually, it's unfortunately now passed away. Charles er, um, but Charles' venture capitalist great guy, and Charles was running Node Summit and came to me in 2017. [00:44:07] Bryan: He is like, I really want you to keynote Node Summit. And I'm like, Charles, I'm not gonna do that. I've got nothing nice to say. Like, this is the, the, you don't want, I'm the last person you wanna keynote. He's like, oh, if you have nothing nice to say, you should definitely keynote. You're like, oh God, okay, here we go. [00:44:22] Bryan: He's like, no, I really want you to talk about, like, you should talk about the Joyent breakup with NodeJS. I'm like, oh man. [00:44:29] Bryan: And that led to a talk that I'm really happy that I gave, 'cause it was a very important talk for me personally. Uh, called Platform is a reflection of values and really looking at the values that we had for Node and the values that Node had for itself. And they didn't line up. [00:44:49] Bryan: And the problem is that the values that Node had for itself and the values that we had for Node are all kind of positives, right? Like there's nobody in the node community who's like, I don't want rigor, I hate rigor. It's just that if they had the choose between rigor and making the language approachable. [00:45:09] Bryan: They would choose approachability every single time. They would never choose rigor. And, you know, that was a, that was a big eye-opener. I do, I would say, if you watch this talk. [00:45:20] Bryan: because I knew that there's, like, the audience was gonna be filled with, with people who, had been a part of the fork in 2014, I think was the, the, the, the fork, the IOJS fork. And I knew that there, there were, there were some, you know, some people that were, um, had been there for the fork and. [00:45:41] Bryan: I said a little bit of a trap for the audience. But the, and the trap, I said, you know what, I, I kind of talked about the values that we had and the aspirations we had for Node, the aspirations that Node had for itself and how they were different. [00:45:53] Bryan: And, you know, and I'm like, look in, in, in hindsight, like a fracture was inevitable. And in 2014 there was finally a fracture. And do people know what happened in 2014? And if you, if you, you could listen to that talk, everyone almost says in unison, like IOJS. I'm like, oh right. IOJS. Right. That's actually not what I was thinking of. [00:46:19] Bryan: And I go to the next slide and is a tweet from a guy named TJ Holloway, Chuck, who was the most prolific contributor to Node. And it was his tweet also in 2014 before the fork, before the IOJS fork explaining that he was leaving Node and that he was going to go. And you, if you turn the volume all the way up, you can hear the audience gasp. [00:46:41] Bryan: And it's just delicious because the community had never really come, had never really confronted why TJ left. Um, there. And I went through a couple folks, Felix, bunch of other folks, early Node folks. That were there in 2010, were leaving in 2014, and they were going to go primarily, and they were going to go because they were sick of the same things that we were sick of. [00:47:09] Bryan: They, they, they had hit the same things that we had hit and they were frustrated. I I really do believe this, that platforms do reflect their own values. And when you are making a software decision, you are selecting value. [00:47:26] Bryan: You should select values that align with the values that you have for that software. That is, those are, that's way more important than other things that people look at. I think people look at, for example, quote unquote community size way too frequently, community size is like. Eh, maybe it can be fine. [00:47:44] Bryan: I've been in very large communities, node. I've been in super small open source communities like AUMs and RAs, a bunch of others. there are strengths and weaknesses to both approaches just as like there's a strength to being in a big city versus a small town. Me personally, I'll take the small community more or less every time because the small community is almost always self-selecting based on values and just for the same reason that I like working at small companies or small teams. [00:48:11] Bryan: There's a lot of value to be had in a small community. It's not to say that large communities are valueless, but again, long answer to your question of kind of where did things go south with Joyent and node. They went south because the, the values that we had and the values the community had didn't line up and that was a very educational experience, as you might imagine. [00:48:33] Jeremy: Yeah. And, and given that you mentioned how, because of those values, some people moved from Node to go, and in the end for much of what oxide is building. You ended up using rust. What, what would you say are the, the values of go and and rust, and how did you end up choosing Rust given that. Go's decisions regarding generics, versioning, compilation speed priority [00:48:56] Bryan: Yeah, I mean, well, so the value for, yeah. And so go, I mean, I understand why people move from Node to Go, go to me was kind of a lateral move. Um, there were a bunch of things that I, uh, go was still garbage collected, um, which I didn't like. Um, go also is very strange in terms of there are these kind of like. [00:49:17] Bryan: These autocratic kind of decisions that are very bizarre. Um, there, I mean, generics is kind of a famous one, right? Where go kind of as a point of principle didn't have generics, even though go itself actually the innards of go did have generics. It's just that you a go user weren't allowed to have them. [00:49:35] Bryan: And you know, it's kind of, there was, there was an old cartoon years and years ago about like when a, when a technologist is telling you that something is technically impossible, that actually means I don't feel like it. Uh, and there was a certain degree of like, generics are technically impossible and go, it's like, Hey, actually there are. [00:49:51] Bryan: And so there was, and I just think that the arguments against generics were kind of disingenuous. Um, and indeed, like they ended up adopting generics and then there's like some super weird stuff around like, they're very anti-assertion, which is like, what, how are you? Why are you, how is someone against assertions, it doesn't even make any sense, but it's like, oh, nope. [00:50:10] Bryan: Okay. There's a whole scree on it. Nope, we're against assertions and the, you know, against versioning. There was another thing like, you know, the Rob Pike has kind of famously been like, you should always just run on the way to commit. And you're like, does that, is that, does that make sense? I mean this, we actually built it. [00:50:26] Bryan: And so there are a bunch of things like that. You're just like, okay, this is just exhausting and. I mean, there's some things about Go that are great and, uh, plenty of other things that I just, I'm not a fan of. Um, I think that the, in the end, like Go cares a lot about like compile time. It's super important for Go Right? [00:50:44] Bryan: Is very quick, compile time. I'm like, okay. But that's like compile time is not like, it's not unimportant, it's doesn't have zero importance. But I've got other things that are like lots more important than that. Um, what I really care about is I want a high performing artifact. I wanted garbage collection outta my life. Don't think garbage collection has good trade offs [00:51:00] Bryan: I, I gotta tell you, I, I like garbage collection to me is an embodiment of this like, larger problem of where do you put cognitive load in the software development process. And what garbage collection is saying to me it is right for plenty of other people and the software that they wanna develop. [00:51:21] Bryan: But for me and the software that I wanna develop, infrastructure software, I don't want garbage collection because I can solve the memory allocation problem. I know when I'm like, done with something or not. I mean, it's like I, whether that's in, in C with, I mean it's actually like, it's really not that hard to not leak memory in, in a C base system. [00:51:44] Bryan: And you can. give yourself a lot of tooling that allows you to diagnose where memory leaks are coming from. So it's like that is a solvable problem. There are other challenges with that, but like, when you are developing a really sophisticated system that has garbage collection is using garbage collection. [00:51:59] Bryan: You spend as much time trying to dork with the garbage collector to convince it to collect the thing that you know is garbage. You are like, I've got this thing. I know it's garbage. Now I need to use these like tips and tricks to get the garbage collector. I mean, it's like, it feels like every Java performance issue goes to like minus xx call and use the other garbage collector, whatever one you're using, use a different one and using a different, a different approach. [00:52:23] Bryan: It's like, so you're, you're in this, to me, it's like you're in the worst of all worlds where. the reason that garbage collection is helpful is because the programmer doesn't have to think at all about this problem. But now you're actually dealing with these long pauses in production. [00:52:38] Bryan: You're dealing with all these other issues where actually you need to think a lot about it. And it's kind of, it, it it's witchcraft. It, it, it's this black box that you can't see into. So it's like, what problem have we solved exactly? And I mean, so the fact that go had garbage collection, it's like, eh, no, I, I do not want, like, and then you get all the other like weird fatwahs and you know, everything else. [00:52:57] Bryan: I'm like, no, thank you. Go is a no thank you for me, I, I get it why people like it or use it, but it's, it's just, that was not gonna be it. Choosing Rust [00:53:04] Bryan: I'm like, I want C. but I, there are things I didn't like about C too. I was looking for something that was gonna give me the deterministic kind of artifact that I got outta C. But I wanted library support and C is tough because there's, it's all convention. you know, there's just a bunch of other things that are just thorny. And I remember thinking vividly in 2018, I'm like, well, it's rust or bust. Ownership model, algebraic types, error handling [00:53:28] Bryan: I'm gonna go into rust. And, uh, I hope I like it because if it's not this, it's gonna like, I'm gonna go back to C I'm like literally trying to figure out what the language is for the back half of my career. Um, and when I, you know, did what a lot of people were doing at that time and people have been doing since of, you know, really getting into rust and really learning it, appreciating the difference in the, the model for sure, the ownership model people talk about. [00:53:54] Bryan: That's also obviously very important. It was the error handling that blew me away. And the idea of like algebraic types, I never really had algebraic types. Um, and the ability to, to have. And for error handling is one of these really, uh, you, you really appreciate these things where it's like, how do you deal with a, with a function that can either succeed and return something or it can fail, and the way c deals with that is bad with these kind of sentinels for errors. [00:54:27] Bryan: And, you know, does negative one mean success? Does negative one mean failure? Does zero mean failure? Some C functions, zero means failure. Traditionally in Unix, zero means success. And like, what if you wanna return a file descriptor, you know, it's like, oh. And then it's like, okay, then it'll be like zero through positive N will be a valid result. [00:54:44] Bryan: Negative numbers will be, and like, was it negative one and I said airo, or is it a negative number that did not, I mean, it's like, and that's all convention, right? People do all, all those different things and it's all convention and it's easy to get wrong, easy to have bugs, can't be statically checked and so on. Um, and then what Go says is like, well, you're gonna have like two return values and then you're gonna have to like, just like constantly check all of these all the time. Um, which is also kind of gross. Um, JavaScript is like, Hey, let's toss an exception. If, if we don't like something, if we see an error, we'll, we'll throw an exception. [00:55:15] Bryan: There are a bunch of reasons I don't like that. Um, and you look, you'll get what Rust does, where it's like, no, no, no. We're gonna have these algebra types, which is to say this thing can be a this thing or that thing, but it, but it has to be one of these. And by the way, you don't get to process this thing until you conditionally match on one of these things. [00:55:35] Bryan: You're gonna have to have a, a pattern match on this thing to determine if it's a this or a that, and if it in, in the result type that you, the result is a generic where it's like, it's gonna be either the thing that you wanna return. It's gonna be an okay that contains the thing you wanna return, or it's gonna be an error that contains your error and it forces your code to deal with that. [00:55:57] Bryan: And what that does is it shifts the cognitive load from the person that is operating this thing in production to the, the actual developer that is in development. And I think that that, that to me is like, I, I love that shift. Um, and that shift to me is really important. Um, and that's what I was missing, that that's what Rust gives you. [00:56:23] Bryan: Rust forces you to think about your code as you write it, but as a result, you have an artifact that is much more supportable, much more sustainable, and much faster. Prefer to frontload cognitive load during development instead of at runtime [00:56:34] Jeremy: Yeah, it sounds like you would rather take the time during the development to think about these issues because whether it's garbage collection or it's error handling at runtime when you're trying to solve a problem, then it's much more difficult than having dealt with it to start with. [00:56:57] Bryan: Yeah, absolutely. I, and I just think that like, why also, like if it's software, if it's, again, if it's infrastructure software, I mean the kinda the question that you, you should have when you're writing software is how long is this software gonna live? How many people are gonna use this software? Uh, and if you are writing an operating system, the answer for this thing that you're gonna write, it's gonna live for a long time. [00:57:18] Bryan: Like, if we just look at plenty of aspects of the system that have been around for a, for decades, it's gonna live for a long time and many, many, many people are gonna use it. Why would we not expect people writing that software to have more cognitive load when they're writing it to give us something that's gonna be a better artifact? [00:57:38] Bryan: Now conversely, you're like, Hey, I kind of don't care about this. And like, I don't know, I'm just like, I wanna see if this whole thing works. I've got, I like, I'm just stringing this together. I don't like, no, the software like will be lucky if it survives until tonight, but then like, who cares? Yeah. Yeah. [00:57:52] Bryan: Gar garbage clock. You know, if you're prototyping something, whatever. And this is why you really do get like, you know, different choices, different technology choices, depending on the way that you wanna solve the problem at hand. And for the software that I wanna write, I do like that cognitive load that is upfront. With LLMs maybe you can get the benefit of the robust artifact with less cognitive load [00:58:10] Bryan: Um, and although I think, I think the thing that is really wild that is the twist that I don't think anyone really saw coming is that in a, in an LLM age. That like the cognitive load upfront almost needs an asterisk on it because so much of that can be assisted by an LLM. And now, I mean, I would like to believe, and maybe this is me being optimistic, that the the, in the LLM age, we will see, I mean, rust is a great fit for the LLMH because the LLM itself can get a lot of feedback about whether the software that's written is correct or not. [00:58:44] Bryan: Much more so than you can for other environments. [00:58:48] Jeremy: Yeah, that is a interesting point in that I think when people first started trying out the LLMs to code, it was really good at these maybe looser languages like Python or JavaScript, and initially wasn't so good at something like Rust. But it sounds like as that improves, if. It can write it then because of the rigor or the memory management or the error handling that the language is forcing you to do, it might actually end up being a better choice for people using LLMs. [00:59:27] Bryan: absolutely. I, it, it gives you more certainty in the artifact that you've delivered. I mean, you know a lot about a Rust program that compiles correctly. I mean, th there are certain classes of errors that you don't have, um, that you actually don't know on a C program or a GO program or a, a JavaScript program. [00:59:46] Bryan: I think that's gonna be really important. I think we are on the cusp. Maybe we've already seen it, this kind of great bifurcation in the software that we writ

“Grief happens because you don't stop loving the person who died. The person doesn't exist in your reality anymore. The everyday is not colored and shaped by this other human being, but you don't stop loving the person. So grief is a particular kind of unrequited love. And probably without that dynamic relationship with this person, I would be someone else. And he would've been someone else. I mean, Paul died before me. But we were, I think, hugely important to the drama of becoming in our own lives.”Today, we are honored to welcome a writer whose work has long explored the intimate landscapes of the mind, memory and the heart. Siri Hustvedt's writing moves between the personal and the philosophical, the literary and the deeply human. Her work bridges collections of essays, non-fiction, poetry, and seven novels, including the international bestsellers What I Loved and The Summer Without Men. Recipient of the Princess of Asturias Award for Literature and the Gabarron Prize for Thought, her work has been translated into over thirty languages. Her new memoir, Ghost Stories, is a reflection on forty-three years shared with her late husband, the writer and filmmaker Paul Auster. In its pages, we encounter not only love and loss, but the quiet persistence of presence, memory, and language itself.(0:00) Grief as Unrequited LoveSiri explores the emotional reality of living without Paul Auster, noting that grief occurs because love does not stop when a person dies.(4:00) Facing Death with CourageThe importance of not hiding from mortality and how discussing end-of-life wishes offered a necessary perspective.(12:37) Reading from Ghost StoriesSiri reads the opening passage of her memoir, detailing how the loss of her husband deranged her sense of time and bodily rhythms.(18:41) The Phantom Limb: ” The beloved is taken away and it feels as if you're amputated or gutted.”(21:50)  Grandfather, Father and Son: Generational Traumas Behind Paul Auster's Writing(24:11)  How Powerful Emotions and a Person's Life Can Play a Role in Illness(30:09) Feeding the Earth "Paul very pointedly told me that he wanted to be buried in the Jewish mode. And the phrase he used was, “I want my body to feed the earth.”(44:23) Physical Love in MarriageOn the importance of physical intimacy in long-term marriages, a reality often left out of grief memoirs.(54:00) The Philosophy of the BetweenHow relational existence is foundational to life.(1:00:16) The Hubris of Controlling Nature(1:12:00) The Dark History of Statistics(1:32:12) The Art of Learning vs. AI and Automated Outcomes“I think we have to ask ourselves, what is education? What do we want from it? How do we want people to learn?Episode Websitewww.creativeprocess.info/podInstagram:@creativeprocesspodcast

“Grief happens because you don't stop loving the person who died. The person doesn't exist in your reality anymore. The everyday is not colored and shaped by this other human being, but you don't stop loving the person. So grief is a particular kind of unrequited love. And probably without that dynamic relationship with this person, I would be someone else. And he would've been someone else. I mean, Paul died before me. But we were, I think, hugely important to the drama of becoming in our own lives.”Today, we are honored to welcome a writer whose work has long explored the intimate landscapes of the mind, memory and the heart. Siri Hustvedt's writing moves between the personal and the philosophical, the literary and the deeply human. Her work bridges collections of essays, non-fiction, poetry, and seven novels, including the international bestsellers What I Loved and The Summer Without Men. Recipient of the Princess of Asturias Award for Literature and the Gabarron Prize for Thought, her work has been translated into over thirty languages. Her new memoir, Ghost Stories, is a reflection on forty-three years shared with her late husband, the writer and filmmaker Paul Auster. In its pages, we encounter not only love and loss, but the quiet persistence of presence, memory, and language itself.(0:00) Grief as Unrequited LoveSiri explores the emotional reality of living without Paul Auster, noting that grief occurs because love does not stop when a person dies.(4:00) Facing Death with CourageThe importance of not hiding from mortality and how discussing end-of-life wishes offered a necessary perspective.(12:37) Reading from Ghost StoriesSiri reads the opening passage of her memoir, detailing how the loss of her husband deranged her sense of time and bodily rhythms.(18:41) The Phantom Limb: ” The beloved is taken away and it feels as if you're amputated or gutted.”(21:50)  Grandfather, Father and Son: Generational Traumas Behind Paul Auster's Writing(24:11)  How Powerful Emotions and a Person's Life Can Play a Role in Illness(30:09) Feeding the Earth "Paul very pointedly told me that he wanted to be buried in the Jewish mode. And the phrase he used was, “I want my body to feed the earth.”(44:23) Physical Love in MarriageOn the importance of physical intimacy in long-term marriages, a reality often left out of grief memoirs.(54:00) The Philosophy of the BetweenHow relational existence is foundational to life.(1:00:16) The Hubris of Controlling Nature(1:12:00) The Dark History of Statistics(1:32:12) The Art of Learning vs. AI and Automated Outcomes“I think we have to ask ourselves, what is education? What do we want from it? How do we want people to learn?Episode Websitewww.creativeprocess.info/podInstagram:@creativeprocesspodcast

“Grief happens because you don't stop loving the person who died. The person doesn't exist in your reality anymore. The everyday is not colored and shaped by this other human being, but you don't stop loving the person. So grief is a particular kind of unrequited love. And probably without that dynamic relationship with this person, I would be someone else. And he would've been someone else. I mean, Paul died before me. But we were, I think, hugely important to the drama of becoming in our own lives.”Today, we are honored to welcome a writer whose work has long explored the intimate landscapes of the mind, memory and the heart. Siri Hustvedt's writing moves between the personal and the philosophical, the literary and the deeply human. Her work bridges collections of essays, non-fiction, poetry, and seven novels, including the international bestsellers What I Loved and The Summer Without Men. Recipient of the Princess of Asturias Award for Literature and the Gabarron Prize for Thought, her work has been translated into over thirty languages. Her new memoir, Ghost Stories, is a reflection on forty-three years shared with her late husband, the writer and filmmaker Paul Auster. In its pages, we encounter not only love and loss, but the quiet persistence of presence, memory, and language itself.(0:00) Grief as Unrequited LoveSiri explores the emotional reality of living without Paul Auster, noting that grief occurs because love does not stop when a person dies.(4:00) Facing Death with CourageThe importance of not hiding from mortality and how discussing end-of-life wishes offered a necessary perspective.(12:37) Reading from Ghost StoriesSiri reads the opening passage of her memoir, detailing how the loss of her husband deranged her sense of time and bodily rhythms.(18:41) The Phantom Limb: ” The beloved is taken away and it feels as if you're amputated or gutted.”(21:50)  Grandfather, Father and Son: Generational Traumas Behind Paul Auster's Writing(24:11)  How Powerful Emotions and a Person's Life Can Play a Role in Illness(30:09) Feeding the Earth "Paul very pointedly told me that he wanted to be buried in the Jewish mode. And the phrase he used was, “I want my body to feed the earth.”(44:23) Physical Love in MarriageOn the importance of physical intimacy in long-term marriages, a reality often left out of grief memoirs.(54:00) The Philosophy of the BetweenHow relational existence is foundational to life.(1:00:16) The Hubris of Controlling Nature(1:12:00) The Dark History of Statistics(1:32:12) The Art of Learning vs. AI and Automated Outcomes“I think we have to ask ourselves, what is education? What do we want from it? How do we want people to learn?Episode Websitewww.creativeprocess.info/podInstagram:@creativeprocesspodcast

“Grief happens because you don't stop loving the person who died. The person doesn't exist in your reality anymore. The everyday is not colored and shaped by this other human being, but you don't stop loving the person. So grief is a particular kind of unrequited love. And probably without that dynamic relationship with this person, I would be someone else. And he would've been someone else. I mean, Paul died before me. But we were, I think, hugely important to the drama of becoming in our own lives.”Today, we are honored to welcome a writer whose work has long explored the intimate landscapes of the mind, memory and the heart. Siri Hustvedt's writing moves between the personal and the philosophical, the literary and the deeply human. Her work bridges collections of essays, non-fiction, poetry, and seven novels, including the international bestsellers What I Loved and The Summer Without Men. Recipient of the Princess of Asturias Award for Literature and the Gabarron Prize for Thought, her work has been translated into over thirty languages. Her new memoir, Ghost Stories, is a reflection on forty-three years shared with her late husband, the writer and filmmaker Paul Auster. In its pages, we encounter not only love and loss, but the quiet persistence of presence, memory, and language itself.(0:00) Grief as Unrequited LoveSiri explores the emotional reality of living without Paul Auster, noting that grief occurs because love does not stop when a person dies.(4:00) Facing Death with CourageThe importance of not hiding from mortality and how discussing end-of-life wishes offered a necessary perspective.(12:37) Reading from Ghost StoriesSiri reads the opening passage of her memoir, detailing how the loss of her husband deranged her sense of time and bodily rhythms.(18:41) The Phantom Limb: ” The beloved is taken away and it feels as if you're amputated or gutted.”(21:50)  Grandfather, Father and Son: Generational Traumas Behind Paul Auster's Writing(24:11)  How Powerful Emotions and a Person's Life Can Play a Role in Illness(30:09) Feeding the Earth "Paul very pointedly told me that he wanted to be buried in the Jewish mode. And the phrase he used was, “I want my body to feed the earth.”(44:23) Physical Love in MarriageOn the importance of physical intimacy in long-term marriages, a reality often left out of grief memoirs.(54:00) The Philosophy of the BetweenHow relational existence is foundational to life.(1:00:16) The Hubris of Controlling Nature(1:12:00) The Dark History of Statistics(1:32:12) The Art of Learning vs. AI and Automated Outcomes“I think we have to ask ourselves, what is education? What do we want from it? How do we want people to learn?Episode Websitewww.creativeprocess.info/podInstagram:@creativeprocesspodcast

“Grief happens because you don't stop loving the person who died. The person doesn't exist in your reality anymore. The everyday is not colored and shaped by this other human being, but you don't stop loving the person. So grief is a particular kind of unrequited love. And probably without that dynamic relationship with this person, I would be someone else. And he would've been someone else. I mean, Paul died before me. But we were, I think, hugely important to the drama of becoming in our own lives.”Today, we are honored to welcome a writer whose work has long explored the intimate landscapes of the mind, memory and the heart. Siri Hustvedt's writing moves between the personal and the philosophical, the literary and the deeply human. Her work bridges collections of essays, non-fiction, poetry, and seven novels, including the international bestsellers What I Loved and The Summer Without Men. Recipient of the Princess of Asturias Award for Literature and the Gabarron Prize for Thought, her work has been translated into over thirty languages. Her new memoir, Ghost Stories, is a reflection on forty-three years shared with her late husband, the writer and filmmaker Paul Auster. In its pages, we encounter not only love and loss, but the quiet persistence of presence, memory, and language itself.(0:00) Grief as Unrequited LoveSiri explores the emotional reality of living without Paul Auster, noting that grief occurs because love does not stop when a person dies.(4:00) Facing Death with CourageThe importance of not hiding from mortality and how discussing end-of-life wishes offered a necessary perspective.(12:37) Reading from Ghost StoriesSiri reads the opening passage of her memoir, detailing how the loss of her husband deranged her sense of time and bodily rhythms.(18:41) The Phantom Limb: ” The beloved is taken away and it feels as if you're amputated or gutted.”(21:50)  Grandfather, Father and Son: Generational Traumas Behind Paul Auster's Writing(24:11)  How Powerful Emotions and a Person's Life Can Play a Role in Illness(30:09) Feeding the Earth "Paul very pointedly told me that he wanted to be buried in the Jewish mode. And the phrase he used was, “I want my body to feed the earth.”(44:23) Physical Love in MarriageOn the importance of physical intimacy in long-term marriages, a reality often left out of grief memoirs.(54:00) The Philosophy of the BetweenHow relational existence is foundational to life.(1:00:16) The Hubris of Controlling Nature(1:12:00) The Dark History of Statistics(1:32:12) The Art of Learning vs. AI and Automated Outcomes“I think we have to ask ourselves, what is education? What do we want from it? How do we want people to learn?Episode Websitewww.creativeprocess.info/podInstagram:@creativeprocesspodcast

“Grief happens because you don't stop loving the person who died. The person doesn't exist in your reality anymore. The everyday is not colored and shaped by this other human being, but you don't stop loving the person. So grief is a particular kind of unrequited love. And probably without that dynamic relationship with this person, I would be someone else. And he would've been someone else. I mean, Paul died before me. But we were, I think, hugely important to the drama of becoming in our own lives.”Today, we are honored to welcome a writer whose work has long explored the intimate landscapes of the mind, memory and the heart. Siri Hustvedt's writing moves between the personal and the philosophical, the literary and the deeply human. Her work bridges collections of essays, non-fiction, poetry, and seven novels, including the international bestsellers What I Loved and The Summer Without Men. Recipient of the Princess of Asturias Award for Literature and the Gabarron Prize for Thought, her work has been translated into over thirty languages. Her new memoir, Ghost Stories, is a reflection on forty-three years shared with her late husband, the writer and filmmaker Paul Auster. In its pages, we encounter not only love and loss, but the quiet persistence of presence, memory, and language itself.(0:00) Grief as Unrequited LoveSiri explores the emotional reality of living without Paul Auster, noting that grief occurs because love does not stop when a person dies.(4:00) Facing Death with CourageThe importance of not hiding from mortality and how discussing end-of-life wishes offered a necessary perspective.(12:37) Reading from Ghost StoriesSiri reads the opening passage of her memoir, detailing how the loss of her husband deranged her sense of time and bodily rhythms.(18:41) The Phantom Limb: ” The beloved is taken away and it feels as if you're amputated or gutted.”(21:50)  Grandfather, Father and Son: Generational Traumas Behind Paul Auster's Writing(24:11)  How Powerful Emotions and a Person's Life Can Play a Role in Illness(30:09) Feeding the Earth "Paul very pointedly told me that he wanted to be buried in the Jewish mode. And the phrase he used was, “I want my body to feed the earth.”(44:23) Physical Love in MarriageOn the importance of physical intimacy in long-term marriages, a reality often left out of grief memoirs.(54:00) The Philosophy of the BetweenHow relational existence is foundational to life.(1:00:16) The Hubris of Controlling Nature(1:12:00) The Dark History of Statistics(1:32:12) The Art of Learning vs. AI and Automated Outcomes“I think we have to ask ourselves, what is education? What do we want from it? How do we want people to learn?Episode Websitewww.creativeprocess.info/podInstagram:@creativeprocesspodcast

Before new episodes resume, the Law & Order: S-Re-View podcast is covering Law & Order: SVU 27x12 "Hubris". Join Taylor Gates and Yael Tygiel as they talk all things #SVU.RAINN Hotline 1-800-656-4673Join the "Thick Ass Fire Booty Bridesmaids" and get a "Justice for Snowball" t-shirt or "Slammin' Pair of Jeans" onesie (As well as other SVU inspired swag) from S-Re-View here: https://www.redbubble.com/people/ottees/shopIn the digital world, lack of a podcast about Law and Order SVU is considered especially heinous. On the internet, the dedicated people who discuss these unforgettable episodes are members of an elite squad known as the Law & Order: S-Re-View podcast! These are their stories. DUN DUN.Join the conversation LIVE every Sunday at 2p PT/ 5p ET, here on FANVERSATION.Follow Felicia Michelle on IG at https://instagram.com/itsFeliciaMichelleFollow Taylor Gates on https://twitter.com/Elphaba_Anne​​​​​​Follow Yael Tygiel on https://instagram.com/yaeltygiel​​​​​​​Previous SVU after-show recap discussions: https://www.youtube.com/playlist?list=PL-Bpw0GYygGPRv_A4CEyyOZlZNeCQ2Ih_S-Re-View is ONLY video SVU aftershow recap & review podcast

Why 95% of planners get it wrong, how monetary policy killed Main Street, and why Chuck Marohn is optimistic about Gen Z. This wide-ranging conversation, first featured on the Yeoman podcast with Geoff Graham, explores the difference between Jane Jacobs's humble incrementalism and Robert Moses's technocratic master plans—and which approach is winning in 300+ communities.   Additional Show Notes Chuck Marohn (Substack) Geoff's Podcast https://yeomanpodcast.com/

Plans by Trump's fascist tech bros as well as Putin and Xi to build AI-run nuclear reactors on the Moon open jurisdictional dilemmas that far outpace the modest UN efforts to put a regulation regime in place for artificial intelligence. These plans are unveiled just as the Bulletin of the Atomic Scientists moves the symbolic hands of the Doomsday Clock to an unprecedented 85 seconds to midnight. The new Doomsday Clock Statement explicitly names AI, as well as nuclear weapons and climate change, as a potential threat to human survival. The International Campaign to Abolish Nuclear Weapons, in conjunction with the Doomsday Clock move, reiterated its position that "we must move beyond managing nuclear weapons and start phasing them out before midnight strikes." In Episode 316 of the CounterVortex podcast, Bill Weinberg argues that we must take a similar abolitionist position on AI and space expansionism, citing unacceptable threats on ecological, epistemological and eschatological grounds. Listen on SoundCloud or via Patreon. https://www.patreon.com/countervortex Production by Chris Rywalt We ask listeners to donate just $1 per weekly podcast via Patreon -- or $2 for our new special offer! We now have 61 subscribers. If you appreciate our work, please become Number 62!

 Ash is turning into a pretty seasoned competitor, and with that new confidence from the Mossdeep Gym, he faces off against his truest rival: Hubris. A member of the Elite Four shows up, and thinks Ash could use a little mentoring. Luckily, the second hand embarrassment is not quite as bad as it's been before, so, Character Growth! Click here to hear how it all plays out!

It's Day 2 on Radio Row and Grant talks Packers with Pete Bukowski before explaining how the Packers needed to be humbled on their approach to the OL. Lindsay Rhodes from Sumer Sports joins to talk coaching changes and the NFC North, and Kate joins the show to talk about her experience upstairs at the NBC media availability. See omnystudio.com/listener for privacy information.

Find bonus episodes at patreon.com/watchwhatcrappens and follow us on Instagram @watchwhatcrappens @ronniekaram @benmandelker Hosted on Acast. See acast.com/privacy for more information.

This is part 1 of 2Karen sits down with Andy to take…well I wouldn't call it accountability. The cake? Does that work? It was an interview, anyway. Then Heavenly finally shows up to the Married to Medicine girls trip in Miramar, and she's going to have to give an incredible stump speech to get Simone's forgiveness. Will Simone shut up long enough for her to get one out? To watch this recap on video, listen to our bonus episodes, and get ad free listening,, go to Patreon.com/watchwhatcrappens. Find bonus episodes at patreon.com/watchwhatcrappens and follow us on Instagram @watchwhatcrappens @ronniekaram @benmandelker Hosted on Acast. See acast.com/privacy for more information.

Michael Morris and Nicholas Lorimer discuss the limits of government plans and policy, the SA-Israeli relationship, and the GNU. Website · Facebook · Instagram · Twitter

There's no denying that technology plays — and will continue to play — a critical role in addressing the climate crisis. But could super-intelligent AI actually solve the problem for us, as several tech billionaires claim? Or is this over-reliance on speculative technology simply a way to distract us from tackling big, real-world problems. Manjula Selvarajah sits down with astrophysicist and author Adam Becker to separate the hype from reality. Featured in this episode: Adam Becker is an astrophysicist, journalist and the author of More Everything Forever, a book that examines the futuristic ideologies of Silicon Valley's tech titans. He is a former science journalism fellow at the Santa Fe Institute and was also a science communicator in residence at the Simons Institute for the Theory of Computing at UC Berkeley.Marcius Extavour is a scientist, creative technologist and communicator who develops solutions for climate change and clean energy. As a partner at Ode, a technology and creative design firm specializing in geospatial AI. He previously built the energy, climate and carbon removal practice at XPRIZE.Further reading: Silicon Valley is at an inflection pointTech oligarchs are gambling our future on a fantasy Travelling to Mars and beating death: The futurist creed of tech's apostles  More Everything Forever Subscribe to Solve for X: Innovations to Change the World here. And below, find a transcript to “Infinity quest.” Solve for X is brought to you by MaRS, North America's largest urban innovation hub and a registered charity. MaRS supports startups and accelerates the adoption of high-impact solutions to some of the world's biggest challenges. For more information, visit marsdd.com.

Zynga's EVP of Studio, Yaron Leyvan, shares his 13-year Zynga journey, from the early days to Zynga to today, where the company operates under Take-Two, and the acquisition strategy behind successful post-acquisition integration in mobile gaming.Yaron breaks down how Zynga builds forever franchises: sustainable games powered by live ops, repeatable game development, and disciplined iteration, where innovation is real, and data-driven decisions don't kill creativity.We also get into studio culture after an acquisition: protecting speed, talent density, and decision-making while aligning with parent-company expectations.Chapters:00:20 Yaron's Journey10:00 Creating Forever Franchises19:40 Post Acquisition Studio Management30:45 Day in the Life of a Head of Studios47:38 Hubris and Humility59:18 The Role of AI and Future Outlook

Dr. Jason Fung is a Canadian nephrologist and leading voice in metabolic health, best known for making the science of fasting and insulin resistance simple, practical, and empowering. Through his books, lectures, and clinical work, he's helped thousands rethink weight loss, type 2 diabetes, and long-term health by focusing on hormones, not just calories. Dr. Fung is the co-founder of The Fasting Method and a sought-after educator on metabolic health. In this episode, Drs. Brian, Tro, and Jason talk about… (00:00) Intro (05:46) The new dietary guidelines and food pyramid (08:02) The Huger Code and understanding hunger (13:19) Why the calories-in/calories-out model for weight-loss is ineffective (17:44) Hedonic hunger (19:06) Conditioned hunger (24:41) Hormones and calories (28:15) Insulin and fat-burning (31:47) The process of digestion and how every step of the process impacts hormones and weight (38:08) While ultra-processed foods are SO much more obesogenic than whole foods (39:53) Food addiction and effective treatment (46:19) The 3 Golden Rules of Weight Loss (49:25) Dr. Fung's new book and masterclass! (Links below) (51:55) Human biology and flavor variety (57:09) Fasting and satiety (01:04:43) Hubris, pride, and ignorance in medicine (01:09:15) Outro For more information, please see the links below. Thank you for listening! Links: Please consider supporting us on Patreon: https://www.lowcarbmd.com/ Dr. Jason Fung: The Fasting Method: https://www.thefastingmethod.com/ Books: https://www.amazon.com/stores/author/B01BT8K6FK Website/Books: https://www.doctorjasonfung.com/ iG: https://www.instagram.com/drjasonfung/ X: https://x.com/drjasonfung YouTube: https://www.youtube.com/channel/UCoyL4iGArWn5Hu0V_sAhK2w The Hunger Code Pre-Order/Masterclass: https://www.doctorjasonfung.com/gift-with-purchase-offer Dr. Brian Lenzkes:  Website: https://arizonametabolichealth.com/ Twitter: https://twitter.com/BrianLenzkes?ref_src=twsrc^google|twcamp^serp|twgr^author Dr. Tro Kalayjian:  Website: https://toward.health Twitter: https://twitter.com/DoctorTro IG: https://www.instagram.com/doctortro/ Toward Health App Join a growing community of individuals who are improving their metabolic health; together.  Get started at your own pace with a self-guided curriculum developed by Dr. Tro and his care team, community chat, weekly meetings, courses, challenges, message boards and more.  Apple: https://apps.apple.com/us/app/doctor-tro/id1588693888  Google: https://play.google.com/store/apps/details?id=uk.co.disciplemedia.doctortro&hl=en_US&gl=US Learn more: https://toward.health/community/

SEGMENT 15: GREAT POWERS VERSUS SMALL STATES IN STRATEGIC THINKING Guest: Gregory Copley Copley contrasts how great powers often act impulsively while smaller states analyze carefully before moving. Discussion examines the hubris of major nations shooting from the hip on foreign policy, the advantages smaller countries gain through meticulous strategic calculation, and lessons for American policymakers in an increasingly complex world.

As religion bleeds followers, it's looking for a digital transfusion from the high-tech elite. We're dissecting the rise of techno-cults, the Vatican's desperate attempt to regulate AI with its Antiqua et Nova policy, and why tech bros like Peter Thiel are now becoming guest speakers at megachurch revivals. It turns out that when you can't get answers from a burning bush, a large language model that tells you exactly what you want to hear is the next best thing. Silicon Valley is building the new gods of a digital age where faith and profit finally merge.News Source:Tech revival after Peter Thiel's Antichrist talks: There's hope and warinessBy Religion News ServiceJanuary 2, 2026

All of us should consider how today's helpful technologies may become tomorrow's tyranny. __________ Register for the Truth Rising showing at Colorado Christian University by visiting colsoncenter.org/ccu.

Yascha Mounk and Scott Anderson discuss how economic collapse has created the conditions for regime change—and what this could mean for the country. Scott Anderson is a veteran war correspondent and a contributing writer at The New York Times Magazine. His latest book is King of Kings: The Iranian Revolution—A Story of Hubris, Delusion and Catastrophic Miscalculation. In this week's conversation, Yascha Mounk and Scott Anderson discuss whether the current protests could finally topple Iran's theocratic regime, what role the Revolutionary Guard might play in determining the country's future, and whether a democratic Iran could emerge from the ashes of the Islamic Republic. If you have not yet signed up for our podcast, please do so now by following ⁠this link on your phone⁠. Email: ⁠leonora.barclay@persuasion.community⁠ Podcast production by Jack Shields and Leonora Barclay. Connect with us! ⁠Spotify⁠ | ⁠Apple⁠ | ⁠Google⁠ X: ⁠@Yascha_Mounk⁠ & ⁠@JoinPersuasion⁠ YouTube: ⁠Yascha Mounk⁠, ⁠Persuasion⁠ LinkedIn: ⁠Persuasion Community Learn more about your ad choices. Visit megaphone.fm/adchoices

In this week's episode, like Icarus, both our storytellers fly a little too close to the sun—and learn the hard way that confidence doesn't always equal competence.Part 1: As a kid, JR Denson is determined to master the art of homemade french fries—but then his kitchen experiment goes up in flames. Part 2: Faced with a looming Science Olympiad deadline, Adam Ruben is sure his last-minute “clock” made from a bag of water will do the trick.JR Denson --a Washington, DC native-- is a full-time college educator and a part time emergency medical technician (EMT). He has become increasingly involved in the DMV's storytelling scene ever since accidentally falling into right before the pandemic. JR has performed for both local and national storytelling organizations such as The Perfect Liar's Club, the Stone Soup Storytelling Festival, and NPR's The Moth. Adam Ruben is a writer, comedian, and molecular biologist in Washington, DC. He writes the monthly humor column “Experimental Error” in the AAAS journal Science Careers and is the author of two books: Surviving Your Stupid, Stupid Decision to Go to Grad School, and Pinball Wizards: Jackpots, Drains, and the Cult of the Silver Ball. He has appeared on the Science Channel, the Food Network, the History Channel, the Travel Channel, the Weather Channel, Discovery, Netflix, and NPR and is a writer for the preschool cartoon “Elinor Wonders Why” on PBS Kids. Adam has performed on stage in 34 states and six countries, including two solo shows. He has told stories onstage with Story Collider, Story District, and Story League, and is a five-time Moth Story Slam Champion and a Lead Producer for the DC/Baltimore chapter of Mortified. He has three kids, two cats, and a day job as a molecular biologist for the US federal government that feels less secure every day.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

In this episode, Dominic Bowen and Aidan Hehir discuss the legacy of the Srebrenica genocide, the politics of remembrance, and why, nearly thirty years later, the region continues to struggle with denial, revisionism, and rising ethnic tensions.Find out more about how competing narratives have shaped post-war identities, the role of international courts in establishing the historical record, and the impact of recent political developments in Bosnia and Herzegovina, Serbia and Republika Srpska.The conversation also addresses the fragility of peace in the Western Balkans, the limitations of international interventions, the erosion of democratic norms, and the dangers posed by nationalist rhetoric and historical distortion.Finally, they explore what meaningful remembrance should look like, how civil society can counter denial, and whether the international community is equipped or willing to prevent future atrocities in the region.Aidan Hehir is a Professor of International Relations at the University of Westminster, where he has taught since 2007 after positions at the University of Sheffield and the University of Limerick, where he also earned his PhD in 2005. He is Course Leader for the postgraduate programmes in International Relations, International Relations and Security, and International Relations and Democratic Politics, and teaches modules on humanitarian intervention and international security. His research focuses on transitional justice, humanitarian intervention, and statebuilding in Kosovo. He is the author or editor of twelve books, including Kosovo and the Internationals: Hope, Hubris and the End of History (2024) and Hollow Norms and the Responsibility to Protect (2019) - winner of the British International Studies Association's prize for best book on intervention and R2P.  His publications include over fifty book chapters and journal articles in leading outlets such as Ethics and International Affairs, and Cooperation and Conflict. He is co-editor of the Routledge Intervention and Statebuilding series, a founding co-convenor of the BISA Working Group on the Responsibility to Protect, and has delivered more than a hundred conference papers worldwide. The International Risk Podcast brings you conversations with global experts, frontline practitioners, and senior decision-makers who are shaping how we understand and respond to international risk. From geopolitical volatility and organised crime to cybersecurity threats and hybrid warfare, each episode explores the forces transforming our world and what smart leaders must do to navigate them. Whether you're a board member, policymaker, or risk professional, The International Risk Podcast delivers actionable insights, sharp analysis, and real-world stories that matter.The International Risk Podcast is sponsored by Conducttr, a realistic crisis exercise platform. Visit Conducttr to learn more.Dominic Bowen is the host of The International Risk Podcast and Europe's leading expert on international risk and crisis management. As Head of Strategic Advisory and Partner at one of Europe's leading risk management consulting firms, Dominic advises CEOs, boards, and senior executives across the continent on how to prepare for uncertainty and act with intent. He has spent decades working in war zones, advising multinational companies, and supporting Europe's business leaders. Dominic is the go-to business advisor for leaders navigating risk, crisis, and strategy; trusted for his clarity, calmness under pressure, and ability to turn volatility into competitive advantage. Dominic equips today's business leaders with the insight and confidence to lead through disruptTell us what you liked!

Alan and Steve respond to a listener question about ensemble pride and dig into the fine line between healthy confidence and toxic hubris in competitive groups—whether it's show choir, marching band, jazz band, or orchestra. They connect ideas like humility, empathy, narcissism, the Dunning–Kruger effect, and imposter syndrome to the way we talk about our own programs and other ensembles, offering practical questions directors can use to check the culture they're building.

Too many men today aren't struggling because they lack information. They're struggling because they're drowning in noise. And, I think it's time we start unpacking why the "modern masculinity" space has become obsessed with hot takes, call-outs, online outrage, and performative "accountability" - and why none of it builds strong men, meaningful connection, or lasting improvement. Today I'm joined by my friend, Jack Donovan, to talk about why gossip masquerades as moral authority, how "calling men out" often replaces real accountability, the difference between integrity, honor, and reputation, why social media rewards division, not leadership, the dangers of pedestalizing others—and why men need a code to live by. SHOW HIGHLIGHTS 00:00 - Studio Setup & Creative Work 02:24 - Why the Right Needs to Create Culture 04:22 - The Problem With Hot Takes 06:06 - Engagement vs. Building a Movement 08:17 - Writing as Intellectual Discipline 10:16 - AI Art, Aesthetics, and Snobbery 12:01 - Giving People the Benefit of the Doubt 14:11 - Funding Art and Leaving a Legacy 17:07 - Storytelling as Masculine Power 19:33 - Integrity as Aesthetic Congruence 21:09 - Integrity vs. Disintegration 23:14 - Faith, Ritual, and Mental Wholeness 25:16 - Philosophy as a Code of Conduct 26:50 - Honor as Reputation 30:13 - Tribalism and Dehumanization 33:18 - Why Men Gossip 36:49 - Malicious Gossip vs. Accountability 41:14 - Reality TV Culture and Privacy 44:43 - Judging Without Context 46:22 - The Danger of Moral Pedestals 49:32 - Hubris and Public Failure 52:31 - The Trust Recession 55:29 - Projection and False Narratives 58:51 - Redemption and Change Battle Planners: Pick yours up today! Order Ryan's new book, The Masculinity Manifesto. For more information on the Iron Council brotherhood. Want maximum health, wealth, relationships, and abundance in your life? Sign up for our free course, 30 Days to Battle Ready  

Prof. Jeffrey Sachs : Trump's Empire of Hubris.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

We hit a new (and disturbing!) failure mode recently when a production rack that had been up for several months saw every (!) compute sled's service processor become simultaneously unresponsive. Bryan and Adam were joined by the members of the Oxide team who debugged the vexing issue -- and reached its surprising root cause.In addition to Bryan Cantrill and Adam Leventhal, we were joined by Oxide colleagues, Cliff Biffle, Matt Keeter, and Will Chandler.Previously, on Oxide and Friends:OxF s05e03 – Holistic Engineering with Robert MustacchiOxF s04e14 – Rebooting a datacenter: A decade laterOxF s01e26 – The Pragmatism of HubrisOxF s05e20 – Debugger-Driven Development (omdb)OxF s05e07 – Transparency in Hardware/Software InterfacesOxF s05e31 – FuturelockOxF s05e33 – A Grown-up ZFS Data Corruption BugSome of the topics we hit on, in the order that we hit them:hubris #2304: STM32H7 Ethernet driver stops yielding CPU after many packetsgist — Summarizing the Hubris side of investigationsMatt's blog: Hunting a spooky ethernet driver bugIf we got something wrong or missed something, please file a PR! Our next show will likely be on Monday at 5p Pacific Time on our Discord server; stay tuned to our Mastodon feeds for details, or subscribe to this calendar. We'd love to have you join us, as we always love to hear from new speakers!

Ah, there you are, my dear. Unknown Broadcast arrives with old-time radio horror stories, classic OTR chills, and the kind of radio suspense that leans close enough to fog the glass. Tonight, six shadows take attendance:

The Jeffrey Epstein non-prosecution agreement (NPA) of 2007-08, reviewed by the U.S. Department of Justice's Office of Professional Responsibility (OPR), detailed how federal prosecutors in the U.S. Attorney's Office for the Southern District of Florida negotiated a deal that effectively ended an active federal investigation into Epstein's alleged trafficking and abuse of underage girls. The agreement granted broad immunity to Epstein and unnamed “potential co-conspirators,” allowed him to plead guilty to state charges instead of facing major federal sex-trafficking counts, and did so without informing or consulting the victims before the deal was executed. The OPR found that while no evidence of corruption or impermissible influence was uncovered, the decision represented “poor judgment” by the prosecutors.Further, the report underscored significant procedural deficiencies: victims were not made aware of the NPA, the USAO did not meaningfully engage with them in accordance with the Crime Victims' Rights Act's principles, and the immunity granted in the NPA curtailed future federal prosecution of Epstein's associates—even as investigation into other victims and broader criminal conduct may have persisted. In short, the OPR concluded that the case resolution was legally within the prosecutors' discretion, but deeply flawed in its execution and fairness to those harmed.to contact me:bobbycapucci@protonmail.comsource:dl (justice.gov)

Thalassophobia and Heeby Jeeby WARNING!!Steven dives into some deep ocean trivia that may frighten those of you who sweat when playing Subnautica. Cooper, Aidan, and Cameron compete in for DEEP coin in this evolution of the Fish episode. But what lurks in the depths of the aphotic zone? Find out this week.

The Jeffrey Epstein non-prosecution agreement (NPA) of 2007-08, reviewed by the U.S. Department of Justice's Office of Professional Responsibility (OPR), detailed how federal prosecutors in the U.S. Attorney's Office for the Southern District of Florida negotiated a deal that effectively ended an active federal investigation into Epstein's alleged trafficking and abuse of underage girls. The agreement granted broad immunity to Epstein and unnamed “potential co-conspirators,” allowed him to plead guilty to state charges instead of facing major federal sex-trafficking counts, and did so without informing or consulting the victims before the deal was executed. The OPR found that while no evidence of corruption or impermissible influence was uncovered, the decision represented “poor judgment” by the prosecutors.Further, the report underscored significant procedural deficiencies: victims were not made aware of the NPA, the USAO did not meaningfully engage with them in accordance with the Crime Victims' Rights Act's principles, and the immunity granted in the NPA curtailed future federal prosecution of Epstein's associates—even as investigation into other victims and broader criminal conduct may have persisted. In short, the OPR concluded that the case resolution was legally within the prosecutors' discretion, but deeply flawed in its execution and fairness to those harmed.to contact me:bobbycapucci@protonmail.comsource:dl (justice.gov)

Meet my friends, Clay Travis and Buck Sexton! If you love Verdict, the Clay Travis and Buck Sexton Show might also be in your audio wheelhouse. Politics, news analysis, and some pop culture and comedy thrown in too. Here’s a sample episode. Give the guys a listen and then follow and subscribe wherever you get your podcasts. Hubris, the Fatal Flaw A major theme throughout the hour is the fallout from the recent government shutdown, which lasted 40 days and ended with bipartisan Senate action. Clay and Buck dissect the political consequences, particularly the backlash against Senate Minority Leader Chuck Schumer. They explore Schumer’s declining popularity, citing polling data and commentary from CNN and David Axelrod, and speculate on the possibility of Alexandria Ocasio-Cortez challenging him in 2028. The hosts also discuss the broader implications of internal Democratic Party tensions, including potential challenges to House Minority Leader Hakeem Jeffries. Incredible Veterans Day Stories Clay and Buck hear stories from the audience about Veterans. David “Rut” Rutherford, Former Navy SEAL and host of The David Rutherford Show, calls in to share his thoughts on this particular Veterans Day, including the uptick in enlistment under President Trump and Secretary of War Hegseth. The hour also includes a fascinating listener call from a man whose father was reportedly driving the car during General George Patton’s fatal accident, offering a firsthand rebuttal to conspiracy theories surrounding Patton’s death. This leads into a teaser for an upcoming conversation with Bill O’Reilly about the topic. Make sure you never miss a second of the show by subscribing to the Clay Travis & Buck Sexton show podcast wherever you get your podcasts! ihr.fm/3InlkL8 For the latest updates from Clay and Buck: https://www.clayandbuck.com/ Connect with Clay Travis and Buck Sexton on Social Media: X - https://x.com/clayandbuck FB - https://www.facebook.com/ClayandBuck/ IG - https://www.instagram.com/clayandbuck/ YouTube - https://www.youtube.com/c/clayandbuck Rumble - https://rumble.com/c/ClayandBuck TikTok - https://www.tiktok.com/@clayandbuck YouTube: https://www.youtube.com/@VerdictwithTedCruzSee omnystudio.com/listener for privacy information.

The Jeffrey Epstein non-prosecution agreement (NPA) of 2007-08, reviewed by the U.S. Department of Justice's Office of Professional Responsibility (OPR), detailed how federal prosecutors in the U.S. Attorney's Office for the Southern District of Florida negotiated a deal that effectively ended an active federal investigation into Epstein's alleged trafficking and abuse of underage girls. The agreement granted broad immunity to Epstein and unnamed “potential co-conspirators,” allowed him to plead guilty to state charges instead of facing major federal sex-trafficking counts, and did so without informing or consulting the victims before the deal was executed. The OPR found that while no evidence of corruption or impermissible influence was uncovered, the decision represented “poor judgment” by the prosecutors.Further, the report underscored significant procedural deficiencies: victims were not made aware of the NPA, the USAO did not meaningfully engage with them in accordance with the Crime Victims' Rights Act's principles, and the immunity granted in the NPA curtailed future federal prosecution of Epstein's associates—even as investigation into other victims and broader criminal conduct may have persisted. In short, the OPR concluded that the case resolution was legally within the prosecutors' discretion, but deeply flawed in its execution and fairness to those harmed.to contact me:bobbycapucci@protonmail.comsource:dl (justice.gov)Become a supporter of this podcast: https://www.spreaker.com/podcast/the-epstein-chronicles--5003294/support.

What does it take to change an entire industry? Thirty years ago, Jomo Tariku, then an industrial design student, noticed something profound missing in his university library: contemporary African furniture designers. This observation sparked a decades-long journey of persistence and vision. I sit down with Jomo to discuss his path from sketching designs in his garage while working other jobs to having his celebrated work featured in The Metropolitan Museum of Art and the film Black Panther: Wakanda Forever. He shares how his father's incredible story as a refugee gave him the hubris to persist through a 27-year wait for recognition. Tune in to learn how he translates his heritage (from the horns of the Nyala antelope to the powerful symbolism of the Afro-comb) into functional, modern art. Tune in to this story about patience, process, and the fight to redefine the creative canon. Chapters 02:22 The Collector's Home: Early Influences from a Father's Travels 05:13 Breadcrumbs: From Drawing Objects to Industrial Design 09:34 The Missing Narrative: A Thesis on African Furniture 14:14 The "Hubris" of an Orphan: A Father's Legacy of Courage 18:59 The Story of the Mito Chair: Connecting Continents with an Afro-Pick 24:37 A Commission for Seneca Village: The Met Afrofutures Room 26:08 The Designer's Process: Collaboration and Master Craftsmanship 31:40 The Balance of Beauty and Function 33:41 How 3D Printing Changed the Game 39:36 The Cost of a Prototype 42:18 The Nyala Chair: "The One That Put Me on the Map" 42:48 The 27-Year Wait and the Rise of BADG 45:10 Advocating for a More Inclusive Canon 47:33 Redefining Success: Joy, Research, and Community   Connect with Jomo: Follow Jomo on Instagram: https://www.instagram.com/jomotariku Jomo's Website: https://jomotariku.com/   Support the Show Website: http://www.martineseverin.comFollow on Instagram: @martine.severin | @thisishowwecreate_ Subscribe to the Newsletter: http://www.martineseverin.substack.com This is How We Create is produced by Martine Severin. This episode was edited by Daniel Espinosa.   Subscribe wherever you get your podcasts Leave a review Follow us on social media Share with fellow creatives  

The Gales of November is very real on the Great Lakes, known as the “Month of Storms.”Some 550 wrecks lie on the bottom of Lake Superior, at least 200 along Superior's Shipwreck Coast, a treacherous 80-Mile stretch with no safe harbor between Munising and Whitefish Point. On November 10, 1975, the Edmund Fitzgerald, a 728 foot freighter went down in a storm described as both blizzard and hurricane taking all 29 crew members to their grave. Made famous by the Gordon Lightfoot song, the wreck has remained a mystery for fifty years.In this episode of the Lake Superior Podcast, Walt Lindala and Frida Waara talk with maritime historian, author and lecturer Fred Stonehouse about that tragic night and what we have learned since her sinking and how her legacy has shaped maritime safety. Key TakeawaysThe Edmund Fitzgerald Sank Fifty Years Ago — But Its Mystery EnduresMaritime historian Fred Stonehouse recounts how the 729-foot freighter Edmund Fitzgerald sank on November 10, 1975, about 15 miles northwest of Whitefish Point. The ship went down without a distress signal, and all 29 crew members were lost—leaving one of the Great Lakes' most haunting mysteries.A Storm Described as Both a Blizzard and a HurricaneThe night the Fitzgerald went down, Lake Superior raged with winds exceeding 75 miles per hour—stronger than a Category 1 hurricane. As Fred explains, the storm “exceeded 75 miles an hour in wind, and a cat one hurricane's only 74.”Hubris and Hard Lessons on the Great Lakes“This was a time when ships had the attitude that they can't sink.”Fred reflects on how the culture of Great Lakes shipping in the 1970s—driven by confidence and schedules—left little room for caution. The Fitzgerald's loss changed that mindset forever, ushering in a new era of safety, respect, and humility toward Lake Superior.The Edmund Fitzgerald at 50: A Tragedy That Changed Everything“The world had changed in that instance when the Fitzgerald disappeared.” The tragedy sparked widespread reforms—from new navigation technology and onboard stress monitoring systems to emergency response protocols. The Ship That Became a Legend“She has sailed from fact into legend of the Great Lakes.”Fred explains how the Edmund Fitzgerald became immortalized through Gordon Lightfoot's ballad, cultural memory, and even merchandise—from ornaments to craft beer. The ship's story transcended history, turning into one of the most iconic Great Lakes legends.An Underwater Graveyard and a Place of ReverenceFred describes the Fitzgerald's final resting place, protected by the Canadian government and closed to divers since 1989. It remains a solemn memorial to the men who perished that night and a reminder of Lake Superior's power.Connect With Us:Lake Superior Podcast Page – https://nplsf.org/podcastFacebook – https://www.facebook.com/NationalParksOfLakeSuperiorFoundationLinkedIn – https://www.linkedin.com/company/national-parks-of-lake-superior-foundationSponsors:Cafe Imports – Minneapolis-based importers of specialty green coffees since 1993, focused on sustainability. Learn more: https://cafeimports.comNational Parks of Lake Superior Foundation – Donate to protect Lake Superior's five national parks: https://nplsf.org/donate

“It is not the content. It is the intention behind it.” – Courtney   CBQ: What is the difference between doom-scrolling and researching on your phone?   Summary: Juan and Courtney dissect the blurry line between learning and avoidance—why “research” can be productive curiosity or just another flavor of self-distraction.   HIGHLIGHTS “Doom-scrolling is when I am not actually going to apply what I learned.” – Courtney “Body-doubling helps neurodiverse people get things done.” – Courtney “Investing in yourself is different from retail therapy.” – Juan “I do not deserve this notebook? Yes you do. Start using it.” – Juan “Repurpose something you already have - intention beats novelty.” – Juan   CareerBlindspot.com  LinkedIn | Instagram | Youtube Juan | Courtney  → Your listening perspective matters - 5 min survey.

Voices of Oxide on the pod! Cliff Biffle (engineer), Dave Pacheco (engineer), and Ben Leonard (designer) are on the show today. Jerod and I were invited to Oxide's annual internal conference called OxCon to meet the people and to hear the stories of what makes Oxide a truly special place to work right now. Cliff Biffle is working on all Hubris and firmware. Cliff says "There's a lot that happens before the 'main CPU' can even power on." Dave Pacheco is leading the efforts on Oxide's "Update" system. And Ben Leonard in charge of all things brand and design at Oxide.

This is a fan fav episode. Are there times when we can get a better result by letting go? What role does pain tolerance play in addiction? Is a plant-based diet really that restrictive? For endurance athlete, author, and podcaster Rich Roll, these kinds of questions are just the tip of the iceberg. In today's episode of Impact Theory, Rich and Tom explore the landscape of ideas ranging everywhere from spirituality and his experience with 12 Steps, all the way to plant-based protein, vegan bodybuilders, and everywhere in between. So whether you or someone you love is struggling with addiction, you're feeling out of touch with your purpose, or you simply want to know where to find the best vegan cheese on the planet, then this episode is for you. ORIGINAL AIR DATE: 3-29-22 SHOW NOTES: 00:00 | Introduction 00:56 | Spirituality and Trusting Your Intuition 08:16 | Solving Problems by Letting Go 21:21 | The Importance of Creative Constraints 27:26 | Hubris and Self-Understanding 47:53 | Relapse and Dealing With Failure 58:36 | The Path to Recovery From Addiction 1:05:36 | SriMu and Rich's Experience With Veganism 1:17:52 | Plant-Based Dietary Choices and Longevity Follow Rich Roll: Website - https://bit.ly/1lTmUBQ Twitter - https://bit.ly/1Rpn19v YouTube - https://bit.ly/2ROrM2G Instagram - https://bit.ly/2PuIWAU Facebook - https://bit.ly/2A9vDAB LinkedIn - https://bit.ly/2A9Pbop What's up, everybody? It's Tom Bilyeu here: If you want my help... STARTING a business: join me here at ZERO TO FOUNDER SCALING a business: see if you qualify here. Get my battle-tested strategies and insights delivered weekly to your inbox: sign up here. ********************************************************************** If you're serious about leveling up your life, I urge you to check out my new podcast, Tom Bilyeu's Mindset Playbook —a goldmine of my most impactful episodes on mindset, business, and health. Trust me, your future self will thank you. ********************************************************************** Join me live on my Twitch stream. I'm live daily from 6:30 to 8:30 am PT at www.twitch.tv/tombilyeu ********************************************************************** LISTEN TO IMPACT THEORY AD FREE + BONUS EPISODES on APPLE PODCASTS: apple.co/impacttheory ********************************************************************** FOLLOW TOM: Instagram: https://www.instagram.com/tombilyeu/ Tik Tok: https://www.tiktok.com/@tombilyeu?lang=en Twitter: https://twitter.com/tombilyeu YouTube: https://www.youtube.com/@TomBilyeu Learn more about your ad choices. Visit megaphone.fm/adchoices

(If you're wondering what the "dam" is about, or why it's mispelt (it's not), just listen...) After a short intro, we jump into the first headline of the week: China Celebrates 80th Anniversary of Defeat of Japan and End of WW2 (1:16). Next, we jump right into China’s 60th Anniversary celebration of subjugating Tibet (12:01), followed by a look at the “run-of-the-river” dam being built in Tibet along a stretch of the river that flows through the world’s deepest canyon (16:51). Finally, today’s show ends with an extended interview with my buddy Jake, who tells some stories after working with us in China a little more than a decade ago.(22:51). Welcome to China Compass on the Fight Laugh Feast Network! I'm your China travel guide, Missionary Ben. Follow me (@chinaadventures) on Twitter/X where I post new/unique Chinese city prayer profiles every single day. Also, you can email me any questions or comments (bfwesten at gmail dot com) and find everything else, including my books, at PrayGiveGo.us! NEW! China Compass is finally on iTunes: https://app.dropwave.io/feed/show/china-compass China Communist Party Appropriates WWII Victory As Its Own https://www.straitstimes.com/asia/east-asia/with-grand-parade-china-projects-its-version-of-war-history-and-its-place-in-the-world https://en.wikipedia.org/wiki/Operation_Beleaguer Tibet “Celebrates” 60 Years of Chinese Rule (1965-2025) https://www.deccanherald.com/world/chinas-tibet-marks-anniversary-with-songs-dances-reminders-of-communist-rule-3690809#google_vignette Some Things Never Change: Annie Taylor’s Failed Venture to Lhasa (1800s) https://web.archive.org/web/20110929041743/http://www.omf.org/omf/us/resources__1/omf_archives/china_inland_mission_stories/a_lady_s_adventures_in_tibet Yarlung Tsampo Dam and Grand Canyon https://en.m.wikipedia.org/wiki/Medog_Hydropower_Station https://en.m.wikipedia.org/wiki/Run-of-the-river_hydroelectricity https://en.m.wikipedia.org/wiki/Yarlung_Tsangpo_Grand_Canyon Pray for China Interceding for all the Cities of China PrayforChina.us Pray for China places of the week (Or, follow @chinaadventures daily…) https://chinacall.substack.com/p/pray-for-china-sep-8-14-2025 Subscribe to China Compass and leave a review on your preferred podcast platform. Follow us on Twitter/X (@chinaadventures), and find much more @ PrayGiveGo.us. Luke 10, verse 2, the harvest is plentiful but the workers are few. Talk again soon!

REALIGNMENT NEWSLETTER: https://therealignment.substack.com/PURCHASE BOOKS AT OUR BOOKSHOP: https://bookshop.org/shop/therealignmentEmail Us: realignmentpod@gmail.comScott Anderson, author of King of Kings: The Iranian Revolution: A Story of Hubris, Delusion, and Catastrophic Miscalculation, joins The Realignment. Marshall and Scott discuss the historical legacy of the rise and fall of the Shah of Iran, how the rise of religious fundamentalism reshaped America's relationship with Iran and the broader Middle East, President Carter's misread of the Iranian Revolution in the context of the Cold War, and survey the aftermath of the joint U.S.-Israel strikes on Iran's nuclear program this past June.