Podcasts about Bios

It's almost time for Taylor Frankie Paul's journey on “The Bachelorette” to officially begin, which means that it's time for us to dive into the cast bios. Twenty-two strapping men who fall broadly into the categories of Former Athlete, Surf Guy, Cowboy and self-proclaimed Mama's Boy (with a side of Dakota Mortensen lookalikes), will be wooing TFP. And turns out, we had a lot to say about them, despite knowing very little. We also discuss the “Bachelorette” reunion / season preview that aired after The Oscars, as well as the social media rollout of the official cast announcements. This season might end up being a trainwreck, but it absolutely won't be boring. To learn more about listener data and our privacy practices visit: https://www.audacyinc.com/privacy-policy Learn more about your ad choices. Visit https://podcastchoices.com/adchoices

20 out of 22 of these guys are here for television, but so is Taylor: so let's put on a show! This episode is brought to you by Quince. To get the softest towels, the best sheets, and the chicest accessories, go to ⁠⁠⁠⁠⁠⁠www.quince.com/2bg1r⁠⁠⁠⁠⁠⁠ for free shipping and returns on us! Let 1-800 Contacts get you the contact lenses you need right now. Order online at ⁠https://1800contacts.com⁠ or download the free 1-800 Contacts app today! Chime is not just smarter banking, it is the most rewarding way to bank. Join the millions who are already banking fee free today. It just takes a few minutes to sign up. Head to Chime.com/ROSE. Listen to our PRE-SHOW and watch us on VIDEO only on Patreon. ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Join the Rose Garden today⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠! CONNECT WITH US: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Instagram⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Twitter⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠TikTok⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Merch⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ EMAIL: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠2blackgirls1rose@gmail.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Follow Natasha's Substack The Nite Owl: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠theniteowl.substack.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Learn more about your ad choices. Visit podcastchoices.com/adchoices

In This Episode: Apple's Cheapest MacBook Ever.  When AI makes friends with AI. Tech Bubble Insights. This week the TEH Podcast is hosted by Leo Notenboom, the “Chief Question Answerer” at Ask Leo!, and Gary Rosenzweig, the host and producer of MacMost, and mobile game developer at Clever Media. (You’ll find longer Bios on the Hosts page.) Top Stories 1:00 GR: MacBook Neo I wasn't right, but that's OK Why this is more interesting than I thought The tablet-replaces-the-PC future is now dead Low power opens possibilities 19:31 LN: What is the point behind moltbook? Meta to Acquire AI-Only Social Media Platform Moltbook https://www.wsj.com/tech/ai/meta-to-acquire-ai-only-social-media-platform-moltbook-0d9cd9d6 https://www.moltbook.com/  29:00 Why does Meta want this? 30:20 GR: AI Psychosis https://www.404media.co/ai-psychosis-help-gemini-chatgpt-claude-chatbot-delusions/?ref=daily-stories-newsletter 32:50 People think the AI is talking to them 50:00 LN: The car wash test Gemini: meh Claude: fail OpenAI GPT 5: fail 57:00 GR: Holding AI in check 59:00 LN: Frustrating surveys Ain’t it Cool 1:00:00 LN: The AI Fix podcast –  5 ways the AI bubble could burst VC with some very interesting perspectives on AI Random for flavor of the discussion: The number of hours worked by the average knowledge worker has only increased due to technology. We use AI. Across every part of the business at my new firm. I think there’s the potential that if we end up getting more efficient models, which everyone wants, that actually makes all of the infrastructure spend that has happened Less. 1:03:00 GR: Anaconda (movie 2025) The Bridgerton X Naked Gun spoof that Leo was talking about is “Farkham Hall”. BSP: Blatant Self-Promotion 1:05:00 LN: How Do I Gain Administrative Access to a Secondhand Computer? – https://askleo.com/12356 1:06:00 GR: 15 Ways the MacBook Neo Is Different From Other MacBooks Transcript 263 Video https://youtu.be/_ekuvBlQXTs

Config OpenDNS on my System, Should I turn off the BIOS updates? My Dell keeps getting stuck at 0%, Datacenter energy costs pledge, AI caused a man to kill himself, I think I love Gemini, New MS Edge feature is VPNish, Laplink software still exists!

In This Episode: Apple announcements. Coding with AI. Copyright and AI. This week the TEH Podcast is hosted by Leo Notenboom, the “Chief Question Answerer” at Ask Leo!, and Gary Rosenzweig, the host and producer of MacMost, and mobile game developer at Clever Media. (You’ll find longer Bios on the Hosts page.) Top Stories 0:00 GR: New Apple Stuff Might be a new low-end Macbook. 8:00 Lightweight? 13:00 GR: Vibe Coding Limits Coding with AI 20:00 LN: Learning how to ask for what you want Different possibilities for the future 30:00 GR & LN: Let's talk about why we use AI art again in light of https://www.theverge.com/policy/887678/supreme-court-ai-art-copyright  38:00 Faking real 40:00 How will it apply to video? How about using AI as a CGI tool? 46:00 LN: Server moves. Very geeky, but kinda interesting maybe. And how I took 50 sites offline with a single click. Oops. Ain’t it Cool 55:00 LN: The Collected Stories of Arthur C. Clarke – (Audio) 56:00 GR: Rental Family (Disney+) BSP: Blatant Self-Promotion 58:00 LN: How Does Cloud Storage Work? – https://askleo.com/75658   59:00 GR: 10 Ways To Start Recording Video With Your iPhone Fast https://macmost.com/10-ways-to-start-recording-video-with-your-iphone-fast.html Transcript teh_262 Video https://youtu.be/E5OqViJQREk

In this episode, we welcome Naureen Hunani, a registered dietitian, educator, and the founder of Registered Dieticians or RDs for Neurodiversity, a group dedicated to changing how healthcare and mental health providers can support neurodivergent people with feeding and eating challenges. Her work focuses on the lived experiences of autistic and neurodivergent people and the intersection of feeding differences, feeding challenges, eating disorders, and Avoidant/Restrictive Food Intake Disorder or ARFID. By supporting disability and neurodiversity, Naureen challenges harmful, compliance-based feeding models and advocates for healthcare rooted in personal choice, access, and dignity. She is widely known for connecting clinical nutrition, disability rights, and social justice to help families, clinicians, and systems rethink what truly supportive, ethical feeding care looks like. https://adalive.org/episodes/episode-151/-Archive, Bios, Description, and Transcripts for Episode 151: When Eating Is a Disability Rights Issue

Jorge Rodrigues considera que ainda não é possível perceber de forma clara quais os objetivos dos EUA com a intervenção militar em curso. Admite que seja "intencional".See omnystudio.com/listener for privacy information.

Jorge Rodrigues considera que ainda não é possível perceber de forma clara quais os objetivos dos EUA com a intervenção militar em curso. Admite que seja "intencional".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

  Neste episódio, Mayra Trinca fala sobre duas pesquisas que, ao seu modo, usam o som para estudar maneiras de enfrentamento à crise climática. Na conversa, Susana Dias, pesquisadora do Labjor e Natália Aranha, doutoranda em Ecologia pela Unicamp contam como os sons dos sapos fizeram parte das mesas de trabalho desenvolvidas pelo grupo de pesquisa para divulgação sobre esses anfíbios. Participa também Lucas Forti, professor na Universidade Federal Rural do Semi-Árido do Rio Grande do Norte. Ele conta como tem sido a experiência do projeto Escutadô, que estuda a qualidade do ambiente da caatinga através da paisagem sonora. ____________________________________________________________ ROTEIRO [música] Lucas: É incrível a capacidade que o som tem de despertar a memória afetiva. Mayra: Você aí, que é ouvinte de podcast, provavelmente vai concordar com isso. O som consegue meio que transportar a gente de volta pros lugares que a gente associa a ele. Se você já foi pra praia, com certeza tem essa sensação quando ouve um bom take do barulho das ondas quebrando na areia. [som de ondas] Mayra: O som pra mim tem um característica curiosa, na maior parte do tempo, ele passa…  despercebido. Ou pelo menos a gente acha isso, né? Porque o silêncio de verdade pode ser bem desconfortável. Quem aí nunca colocou um barulhinho de fundo pra estudar ou trabalhar? Mayra: Mas quando a gente bota reparo, ele tem um força muito grande. De nos engajar, de nos emocionar. [música de violino] Mayra: Também tem a capacidade de incomodar bastante… [sons de construção] Mayra: Eu sou a Mayra Trinca e você provavelmente já me conhece aqui do Oxigênio. Mayra: No episódio de hoje, a gente vai falar sobre som. Mais especificamente, sobre projetos de pesquisa e comunicação que usam o som pra entender e pra falar sobre mudanças climáticas e seus impactos no meio ambiente. [música de fundo] Natália: E as paisagens sonoras não são apenas um conjunto de sons bonitos. Elas são a própria expressão da vida de um lugar. Então, quando a gente preserva uma paisagem sonora, estamos preservando a diversidade das espécies que vocalizam naquele lugar, os modos de vida e as relações que estão interagindo. E muitas vezes essas relações dependem desses sons, que só existem porque esses sons existem. Então, a bioacústica acaba mostrando como os sons, os sapos também os mostram, como que esses cantos carregam histórias, ritmos, horários, temperaturas, interações que não aparecem ali somente olhando o ambiente. [Vinheta] João Bovolon: Seria triste se músicos só tocassem para músicos. Pintores só expusessem para pintores. E a filosofia só se destinasse a filósofos. Por sorte, a capacidade de ser afetado por um som, uma imagem, uma ideia, não é exclusividade de especialistas. MAYRA: Essa frase é de Silvio Ferraz, autor do Livro das Sonoridades. O trecho abre o texto do artigo “A bioacústica dos sapos e os estudos multiespécies: experimentos comunicacionais em mesas de trabalho” da Natália. Natália: Olá, meu nome é Natália Aranha. Eu sou bióloga e mestra pelo Labjor, em Divulgação Científica e Cultural. Durante o meu mestrado, eu trabalhei com os anfíbios, realizando movimentos com mesas de trabalhos e com o público de diferentes faixas etárias. Atualmente, eu sou doutoranda no Programa de Pós-Graduação em Ecologia pelo Instituto de Biologia da Unicamp. MAYRA: A Natália fez o mestrado aqui no Labjor na mesma época que eu. Enquanto eu estudava podcasts, ela tava pesquisando sobre divulgação científica de um grupo de animais muitas vezes menosprezado. [coaxares] Susana: Os sapos, por exemplo, não participam da vida da maioria de nós. Eles estão desaparecidos dos ecossistemas.  Eles estão em poucos lugares que restaram para eles. Os brejos são ecossistemas muito frágeis. São os lugares onde eles vivem. Poucos de nós se dedicam a pensar, a se relacionar, a apreciar, a cuidar dessa relação com os sapos. Mayra: Essa que você ouviu agora foi a Susana, orientadora do trabalho da Natália. Susana: Meu nome é Susana Dias, eu sou pesquisadora do Laboratório de Estudos Avançados em Jornalismo, o Labjor, professora da pós-graduação em Divulgação Científica e Cultural, do Labjor/IEL/Unicamp. E trabalho com comunicação, artes, ciências, desenvolvendo várias metodologias de experimentação coletiva com as pessoas. Mayra: Mas, o interesse da Natália pelos sapos não começou no mestrado. Ela já era apaixonada pela herpetologia antes disso. [som de ícone] Mayra: Herpetologia é a área da biologia que estuda répteis e anfíbios. E eu posso dizer que entendo a Natália. Pra quem não sabe, eu também sou bióloga. E durante a faculdade cheguei a fazer um estágio na mesma área, porque também era um tema que me interessava muito. Mayra: Só que eu trabalhei mais com répteis, que são as cobras e os lagartos. E eu acabei desistindo da área em pouco tempo, apesar de ainda achar esses bichinhos muito legais. Já a Natália descobriu o amor pelos sapos num congresso de herpetologia que foi durante a graduação e, diferente de mim, ela segue trabalhando com eles até hoje. Natália: E eu me apaixonei. Eu digo que me apaixonei a partir da abertura do congresso, porque foi uma experiência muito legal que fizeram a partir dos sons, a partir de fotos e vídeos de vários pesquisadores realizando trabalhos de campo com esses animais. E, a partir desse momento, eu falei que era isso que eu queria fazer na minha vida. Mayra: Ah, e é importante dizer, que antes mesmo disso tudo, a Natália já tinha um interesse artístico por esses animais. Natália: E, como eu amo desenvolver pinturas realistas, esses animais são maravilhosos, quando você pensa nas cores, nos detalhes, nas texturas que eles trazem. Mayra: Porque foi dessa experiência que surgiu a ideia de trabalhar com divulgação científica, que acabou levando a Natália  até a Susana. Mas como ela também tinha interesse de pesquisa com esses animais, ela acabou participando dos dois grupos ao longo do mestrado: o de divulgação e o de herpetologia, com o pessoal da biologia. Susana: Foi muito legal justamente pela possibilidade da Natália habitar esse laboratório durante um tempo, acompanhar o trabalho desses herpetólogos e a gente poder conversar junto com o grupo de pesquisa, que é o Multitão, aqui do Labjor da Unicamp, que é o nosso grupo, sobre possibilidades de conexão com as artes, e também com a antropologia, com a filosofia. A gente começou a tecer esses emaranhados lentamente, devagarzinho. Mayra: Quando a Natália chegou no mestrado, ela tinha uma visão muito comum da divulgação científica, que é a ideia de que os divulgadores ou os cientistas vão ensinar coisas que as pessoas não sabem. Mayra: É uma visão muito parecida com a que a gente ainda tem de escola mesmo, de que tem um grupo de pessoas que sabem mais e que vão passar esse conhecimento pra quem sabe menos. Natália: E daí a Susana nos mostrou que não era somente fazer uma divulgação sobre esses animais, mas mostrar a importância das atividades que acabam gerando afeto. Tentar desenvolver, fazer com que as pessoas criem movimentos afetivos com esses seres. Mayra: Se você tá no grupo de pessoas que tem uma certa aversão a esses animais, pode achar isso bem esquisito. Mas criar essas relações com espécies diferentes da nossa não significa necessariamente achar todas lindas e fofinhas. É aprender a reconhecer a importância que todas elas têm nesse emaranhado de relações que forma a vida na Terra. Mayra: Pra isso, a Natália e a Susana se apoiaram em uma série de conceitos. Um deles, que tem sido bem importante nas pesquisas do grupo da Susana, é o de espécies companheiras, da filósofa Donna Haraway. Natália: Descreve esses seres com os quais vivemos, com os quais aprendemos e com os quais transformam como seres em que a gente não habita ou fala sobre, mas a gente habita e escreve com eles. Eles nos mostram que todos nós fazemos parte de uma rede de interações e que nenhum ser nesse mundo faz algo ou vive só. Então, os sapos, para mim, são essas espécies companheiras. Mas não porque eles falam na nossa língua, mas porque nós escutamos seus cantos e somos levados a repensar a nossa própria forma de estar no mundo. Mayra: Uma coisa interessante que elas me explicaram sobre esse conceito, é que ele é muito mais amplo do que parece. Então, por exemplo, bactérias e vírus, com quem a gente divide nosso corpo e nosso mundo sem nem perceber são espécies companheiras. Ou, as plantas e os animais, que a gente usa pra se alimentar, também são espécies companheiras Susana: E uma das características do modo de viver dos últimos anos, dos últimos 50 anos dos humanos, são modos de vida pouco ricos de relações, com poucas relações com os outros seres mais que humanos. E a gente precisa ampliar isso. Trazer os sapos é muito rico porque justamente abre uma perspectiva para seres que estão esquecidos, que pertencem a um conjunto de relações de muito poucas pessoas. Mayra: Parte do problema tem a ver com o fato de que as espécies estão sumindo mesmo. As mudanças climáticas, o desmatamento e a urbanização vão afastando as espécies nativas das cidades, por exemplo, que passam a ser povoadas por muitos indivíduos de algumas poucas espécies. Pensa como as cidades estão cheias de cães e gatos, mas também de pombas, pardais, baratas. Ou em áreas de agropecuária, dominadas pelo gado, a soja e o capim onde antes tinha uma floresta super diversa. Susana: Eu acho que um aspecto fundamental para a gente entender esse processo das mudanças climáticas é olhar para as homogeneizações. Então, como o planeta está ficando mais homogêneo em termos de sons, de imagens, de cores, de modos de vida, de texturas. Uma das coisas que a gente está perdendo é a multiplicidade. A gente está perdendo a diversidade. Mayra: Pensa bem, quando foi a última vez que você interagiu com um sapo? (Herpetólogos de plantão, vocês não valem). Provavelmente, suas memórias com esses animais envolvem pouco contato direto e você deve lembrar mais deles justamente pelo… som que eles fazem. [coaxares, música] Lucas: Eu comecei a pensar na acústica como uma ferramenta de entender a saúde do ambiente, e queria aplicar isso para recifes de coral, enfim, a costa brasileira é super rica. Mayra: Calma, a gente já volta pra eu te explicar como a Natália e a Susana relacionaram ciências e artes na divulgação sobre os sapos. Antes, eu quero te contar um pouco sobre outro projeto que tem tudo a ver com o tema. Deixa o Lucas se apresentar. Lucas: Pronto, eu me chamo Lucas, eu sou biólogo de formação, mas tive uma vertente acadêmica na minha profissão, em que eu me dediquei sempre a questões relacionadas à ecologia, então fiz um mestrado, doutorado na área de ecologia. Mayra: Sim, o Lucas, assim como eu, a Natália e mesmo a Susana, também fez biologia. Lucas: Os biólogos sempre se encontram em algum lugar. Mayra: A gente ainda vai dominar o mundo…[risadas] Mayra: Tá, mas voltando aqui. O Lucas esteve nos últimos anos trabalhando no Nordeste. Eu conversei com ele durante um estágio de professor visitante aqui na Unicamp. Lucas: Então estou passando um estágio de volta aqui às minhas raízes, que eu sou daqui do interior de São Paulo, então vim passar frio um pouquinho de volta aqui em  Campinas. Mayra: Essa entrevista rolou já tem um tempinho, em agosto de 2025. E realmente tava fazendo um friozinho naquela semana. Mayra: Eu fui conversar com o Lucas sobre um projeto que ele faz parte junto com o Observatório do Semiárido, da Universidade Federal Rural do Semi-Árido, no Rio Grande do Norte. Mayra: A ideia dessa pesquisa é criar um banco de dados sonoros e construir um algoritmo. Lucas: testar algoritmos, né, conseguir ter uma ferramenta na mão que possa ajudar a gente a detectar níveis de degradação no Semiárido com base em informação acústica. Mayra: Esse projeto é o Escutadô. Lucas: O projeto Escutadô, ele nasceu… assim, tem a história longa e a história curta. Mayra: Óbvio que eu escolhi a longa. E ela começa escuta só, com os anfíbios. Mayra: Coincidência? Lucas: Não, não tem coincidência nenhuma. Lucas: Mas eu comecei sim estudando o comportamento de anfíbios, e uma característica muito peculiar dos anfíbios é a vocalização, né? Então, os anfíbios me levaram para a acústica, e aí a acústica entrou na minha vida também para tornar as abordagens da minha carreira, de como eu vou entender os fenômenos através desse ponto de vista sonoro, né? Mayra: Isso é uma coisa muito comum na biologia. Tem muitos animais que são complicados de enxergar, porque são noturnos, muito pequenos ou vivem em lugares de difícil acesso. Então uma estratégia muito usada é registrar os sons desses animais. Vale pra anfíbios, pra pássaros, pra baleias e por aí vai. [sons de fundo de mar] Mayra: Inclusive, lembra, a ideia original do projeto do Lucas era usar a bioacústica, essa área da biologia que estuda os sons, pra investigar recifes de corais. Ele tava contando que elaborou essa primeira proposta de pesquisa pra um edital. Lucas: Aí a gente não venceu essa chamada, mas a gente reuniu uma galera com colaboração, escrevemos um projeto super lindo, e aí por alguma razão lá não foi contemplado o financiamento. Mayra: Isso também é algo muito comum na biologia. E em várias outras áreas de pesquisa. Mas, vida que segue, novas oportunidades apareceram. Lucas: O projeto Escutadô começou no mar, mas a gente conseguiu ter sucesso com a ideia mesmo, a hora que eu cheguei em Mossoró, como professor visitante na Universidade Federal Rural do Semiárido, abriu um edital da FINEP, voltado para a cadeias produtivas, bioeconomia, e a gente identificou que a gente poderia utilizar essa ideia, né, e aplicar essa ideia, mas aí eu já propus que a gente fosse atuar no ecossistema terrestre. Mayra: FINEP é a Financiadora de Estudos e Projetos do Ministério da Ciência, Tecnologia e Inovação. O Lucas quis alterar a proposta inicial, primeiro, porque fazia mais sentido dentro do contexto que ele tava trabalhando. E, depois, porque a região tem uma forte dependência do ecossistema da caatinga pro sustento da população e pra preservação do seu modo de vida, a tal bioeconomia que ele citou. Mayra: Além disso, Lucas: a caatinga é o bioma que certamente tá sentindo mais os extremos, né, das mudanças climáticas, então isso trouxe uma contextualização muito interessante para o projeto, especialmente porque casava com a questão da bioeconomia, né, então a gente tentou embarcar nessa linha e transformamos essa tecnologia para pensar como ela poderia detectar níveis de degradação para a região do Semiárido, né, e aí deu certo. Mayra: Funciona mais ou menos assim, a equipe de pesquisa instalou uma série de gravadores espalhados, mais de 60 pontos no estado do Rio Grande do Norte e alguns pontos na Paraíba e no Ceará. Lucas: Então, quando a gente instala o gravador no ambiente, ele grava três minutos, dorme sete, grava três minutos, dorme sete e fica assim rodando, a gente tem duas rodadas de amostragem, uma que é feita durante a estação seca e outra que é feita durante a estação chuvosa, então o gravador fica em cada ponto por 20 dias e nesses 20 dias ele fica continuamente gravando três minutos e dormindo sete. Mayra: Essas gravações viram uma grande biblioteca sonora. O próximo passo é reconhecer quais sons representam áreas mais conservadas… [captação de área preservada] Mayra: E quais gravações foram feitas em áreas mais degradadas, principalmente com mais alterações antrópicas no ambiente. [captação de área antropizada] Mayra: Pra gente, até que é fácil reconhecer a diferença entre os sons. Agora, como a gente transforma isso, por exemplo, num aplicativo, capaz de identificar o nível de degradação do ambiente usando só o som daquele lugar? Lucas: Pois é, agora você tocou no ponto que eu acho que é o maior desafio do projeto e também o que torna o projeto, assim, inovador. A gente já tem hoje mais ou menos 16 mil horas de gravação, então a gente não tem como não usar uma ferramenta de aprendizado de máquina para ajudar no processamento desses dados. Mayra: A essa altura, você já deve saber o básico de como funcionam as inteligências artificiais. Elas comparam bases de dados gigantescas pra achar padrões. Mas, isso funciona bem pra texto ou pra imagens. Lucas: E a gente introduziu um conceito de aprendizado de escuta de máquina, ou seja, a gente não vai trabalhar sobre o ponto de vista da imagem, vai trabalhar sobre o ponto de vista da escuta, opa, pera aí, mas como é que a gente faz isso? Mayra: O Lucas explicou que o que eles tiveram que fazer foi, de certa forma, realmente transformar esses sons em imagens. Pra isso, eles usam os espectrogramas, que são aquelas representações visuais do som, eu vou deixar um exemplo lá no site e no nosso Instagram, depois você pode procurar pra ver. Mayra: Essa etapa do projeto, o treinamento da IA, tá sendo feita em parceria com o BIOS, o Centro de Pesquisa em Inteligência Artificial aqui da Unicamp. A gente já falou um pouco desse projeto no episódio 201 – Um bate-papo sobre café. Se você ainda não ouviu, tem mais essa lição de casa pra quando acabar esse episódio, vale a pena, porque tá bem legal. [divulgação podcast SabIA!] [música] Mayra: Os sons captados pelo Escutadô, projeto que o Lucas faz parte, ou as gravações dos anfíbios que a gente tava falando com a Natália, nunca são sons isolados. Mayra: Esse conjunto de sons de um ambiente forma o que a gente chama de paisagem sonora. Lucas: Esses sons podem ter origens geofísicas, então o som do vento, o som da chuva, o som dos fluxos de corrente, riachos, cachoeiras, você tem os sons da própria biodiversidade, né, que é baseado nos sistemas de comunicação acústica da fauna, por exemplo, quando as aves produzem as vocalizações, os anfíbios, os insetos, os mamíferos, você tem todo ali um contexto de produção de sinais acústicos que representam assinaturas da presença da biodiversidade no ambiente. E você ainda tem a assinatura da presença das tecnofonias ou antropofonias, né, que são os sons que são produzidos pelos seres humanos, né, seja os sons das rodovias, das construções, das obras, das edificações, ou seja, que tem toda uma contextualização. Mayra: A ideia de usar o som, ou a paisagem sonora, pra entender a saúde de um ambiente, não é nada nova. Um dos livros mais importantes, praticamente fundador do movimento ambientalista nos Estados Unidos, é o Primavera Silenciosa, da Rachel Carson, e ele foi publicado em 1962. Lucas: Então ela já estava alertando para a sociedade acadêmica, especialmente, que o uso de pesticidas, né, as mudanças que o ser humano está promovendo na paisagem estão causando extinções sonoras, né, porque está alterando a composição das espécies na natureza, então a gente está embarcando um pouco nessa ideia que influenciou o que hoje a gente chama de soundscape ecology, que é a ecologia da paisagem sonora, ou ecologia da paisagem acústica. Natália: As pessoas automaticamente imaginam que o silêncio seja algo bom. Mas, esse silêncio é um sinal de alerta, porque ele mostra que as espécies estão desaparecendo e como os seus ciclos e modos de interação estão mudando. E que o habitat, o lugar, já não está dando mais condições impostas pelo clima. Eu acredito que os sons funcionam como uma espécie de termômetro da vida. Quando eles diminuem, é porque a diversidade está ali diminuindo. Mayra: A gente vai ver que a Natália usou noções de paisagem sonora pra criar atividades imersivas de divulgação, onde as pessoas puderam experimentar com diferentes sons e ver como era possível criar novas relações com os sapos a partir deles. Mayra: No caso do Lucas, a paisagem sonora funciona bem como a Natália descreveu, é um termômetro que mede a qualidade de um ambiente da Caatinga. Talvez você imagine esse bioma como um lugar silencioso, um tanto desértico, mas isso tem mais a ver com a imagem comumente divulgada de que é uma região de escassez. Lucas: Do ponto de vista das pessoas interpretarem ela como um ambiente pobre, enquanto ela é muito rica, em termos de biodiversidade, em termos de recursos naturais, em termos de recursos culturais, ou seja, a cultura das populações que vivem lá é extremamente rica. Mayra: Pra complicar ainda mais a situação, a Caatinga está na área mais seca do nosso país. Lucas: Ou seja, a questão da escassez hídrica é extremamente importante. E torna ela, do ponto de vista das mudanças climáticas, ainda mais importante. Mayra: A importância de se falar de grupos menosprezados também aparece na pesquisa da Natália com os sapos. Vamos concordar que eles não tão exatamente dentro do que a gente chama de fofofauna, dos animais queridinhos pela maioria das pessoas, mas não por isso projetos de conservação são menos importantes. Pelo contrário. Mayra: Pra dar uma ideia, na semana que eu escrevia esse roteiro, estava circulando nas redes sociais um estudo que mostrou que, em cinquenta anos, as mudanças climáticas podem ser responsáveis pelo desaparecimento completo dos anfíbios na Mata Atlântica. Mayra: Daí a importância de envolver cada vez mais pessoas em ações de preservação e enfrentamento às mudanças climáticas. Susana: Que a gente pudesse trazer uma paisagem sonora da qual os humanos fazem parte e fazem parte não apenas produzindo problemas, produzindo destruição, mas produzindo interações, interações ecológicas. [música] Mayra: Voltamos então à pesquisa da Natália. Mayra: Ela usou uma metodologia de trabalho que tem sido muito utilizada pela Susana e seu grupo de pesquisa, que são as mesas de trabalho. Susana: E elas foram surgindo como uma maneira de fazer com que a revista ClimaCom, que é uma revista que está tentando ensaiar modos de pensar, de criar, de existir diante das catástrofes, a revista pudesse ter uma existência que não fosse só online, que fosse também nas ruas, nas praças, nas salas de aula, nos outros espaços, que ela tivesse uma existência fora das telas. E que, com isso, a gente se desafiasse não apenas a levar para fora das telas e para as outras pessoas algo que foi produzido na universidade, mas que a gente pudesse aprender com as outras pessoas. Mayra: A ideia das mesas é reunir pessoas diversas, de dentro e de fora da universidade, pra criarem juntas a partir de um tema. Susana: Então, quando chegou a proposta dos anfíbios, a gente resolveu criar uma mesa de trabalho com os sapos. E essa mesa de trabalho envolvia diversas atividades que aconteciam simultaneamente. Essas atividades envolviam desde fotografia, pintura, desenho, colagem, grafismo indígena, até estudo dos sons. Mayra: A Susana estava explicando que durante essas mesas, elas conseguem fazer com que as pessoas interajam com os sapos de uma forma diferente, mais criativa. Criativa aqui tanto no sentido de imaginar, quanto de criar e experimentar mesmo. Susana: A gente propôs a criação de um caderno de estudo dos sons junto com as pessoas. A gente disponibilizou vários materiais diferentes para que as pessoas pudessem experimentar as sonoridades. Disponibilizamos um conjunto de cantos da fonoteca aqui da Unicamp, de cantos dos sapos, para as pessoas escutarem. E pedimos que elas experimentassem com aqueles objetos, aqueles materiais, recriar esses sons dos sapos. E que elas pudessem depois transpor para um caderno essa experiência de estudo desses sons, de como esses sons se expressavam. Mayra: Esse é um exemplo de como a gente pode aproximar as pessoas do trabalho dos cientistas sem que isso coloque a pesquisa feita nas universidades como algo superior ou mais importante do que outros conhecimentos. Escuta só a experiência da Natália: Natália: Através de diferentes materiais, de diferentes meios, é possível criar um movimento afetivo que vai além daquele movimento do emissor-receptor que traz uma ideia mais generalista, mais direta, de que você só fala e não escuta. Então, uma das coisas que mais marcou o meu trabalho nessa trajetória foi a escuta. Onde a gente não apenas falava com os anfíbios, mas também a gente escutava as histórias que as pessoas traziam, os ensinamentos de outros povos, de outras culturas. Então, essa relação entre arte e ciências possibilitou todo esse movimento que foi muito enriquecedor (6:14) Susana: As mesas de trabalho foram um lugar também onde as pessoas acessaram um pouco do trabalho dos herpetólogos. Entraram em relação com a maneira como os herpetólogos estudam os sapos. Interessa para eles se o som do sapo é mais amadeirado, é mais vítreo, é mais metálico. O tipo de som, se ele tem uma pulsação diferente da outra, um ritmo diferente do outro. Eles fazem várias análises desses sons, estudam esses sons em muitos detalhes. Mayra: Trazer essa possibilidade de experimentação é um dos principais objetivos das ações e das pesquisas realizadas pelo grupo da Susana aqui no Labjor. E o encontro com as práticas artísticas tem sido um meio de trabalhar essas experimentações. [música de fundo] Susana: Eu acho que a gente tem pensado muito ciências e artes no plural, com minúsculas, justamente para trazer uma potência de multiplicidade, de possibilidades não só de pesquisa e produção artística, mas de pensamento, modos diferentes de viver no mundo e de praticar a possibilidade de pensar, de criar, de se relacionar com os outros seres. Mayra: Mas, segundo a Susana, tem um desafio grande nesse tipo de trabalho… Susana: Porque é muito comum as pessoas, sobretudo os cientistas, acharem que as artes são uma embalagem bonita para as ciências. Então, o que as artes vão fazer vai ser criar uma maneira das pessoas se seduzirem por um conteúdo científico, de se tornar mais belo, mais bonito. A gente não pensa que esse encontro entre artes e ciências pode tornar as ciências mais perturbadoras, pode questionar o que é ciência, pode gerar coisas que não são nem arte nem ciência, que a gente ainda não conhece, que são inesperadas, que são produções novas. Mayra: Quando a Natália fala da possibilidade de criar relações afetivas com os sapos, ela não quer dizer apenas relações carinhosas, mas também de sensibilidade, de se deixar afetar, no sentido de se permitir viver aquela experiência.  De entrar em contato com essas espécies companheiras e, realmente, sair desses encontros diferente do que a gente entrou. Susana: Então, a gente está tentando pensar atividades de divulgação científica e cultural que são modos de criar alianças com esses seres. São modos de prestar atenção nesses seres, de levar a sério suas possibilidades de existir, suas maneiras de comunicar, suas maneiras de produzir conhecimento. É uma ideia de que esses seres também produzem modos de ser e pensar. Também produzem ontopistemologias que a gente precisa aprender a se tornar digno de entrar em relação. Mayra: Em tempos de crise climática, isso se torna especialmente importante. Quando a gente fala de comunicação de risco, sempre existe a preocupação de falar com as pessoas de uma forma que a informação não seja paralisante, mas que crie mobilizações. Mayra: Eu aposto que você, assim como eu, de vez em quando se sente bem impotente quando pensa na catástrofe ambiental em curso. A gente se sente pequeno diante do problema. Só que é necessário fazer alguma coisa diferente do que a gente tem feito ou veremos cada vez mais eventos naturais extremos que têm destruído tantas formas de vida. [encerra música] Susana: Acho que a gente tem pensado nesses encontros justamente como aquilo que pode tirar a gente da zona do conforto e pode gerar uma divulgação científica e cultural nesses encontros entre artes e ciências, que experimentem algo que não seja massificado, algo que escape às abordagens mais capitalizadas da comunicação e mais massificadas, e que possam gerar outras sensibilidades nas pessoas, possam engajá-las na criação de alguma coisa que a gente ainda não sabe o que é, que está por vir. Mayra: A única forma de fazer isso é efetivamente trazendo as pessoas para participar dos projetos, aliando conhecimentos locais e tradicionais com as pesquisas acadêmicas. Isso cria um senso de pertencimento que fortalece os resultados dessas pesquisas. Mayra: O projeto Escutadô, que o Lucas faz parte, também trabalha com essa perspectiva de engajamento. Lucas: A gente usa uma abordagem chamada ciência cidadã, onde a gente se conecta com o público, e os locais onde a gente vai fazer as amostragens são propriedades rurais de colaboradores ou de voluntários do projeto. Então, a gente tem toda essa troca de experiências, de informação com esse público que vive o dia a dia ali no semiárido, ali na Caatinga. Tudo isso enriquece muito a nossa visão sobre o projeto, inclusive as decisões que a gente pode ter em relação a como que essa tecnologia vai ser empregada ou como que ela deveria ser empregada. Mayra: Lembra que o projeto foi financiado a partir de um edital que considerava a bioeconomia? Então, pro Lucas, a pesquisa só se torna inovadora e significativa de verdade se tiver efeitos práticos pra população que ajudou a construir esse conhecimento. Lucas: Senão é só uma ideia bacana, né? Ela precisa se transformar em inovação. Então, a gente tem toda essa preocupação de criar essa ferramenta e de que essa ferramenta seja realmente interessante para mudar a forma com que a gente vai entender ou tomar as decisões de forma mais eficiente, né? E que isso se torne um recurso que seja possível, né? Para que as pessoas utilizem. Mayra: A ideia do projeto é que, a partir de um aplicativo com aquele algoritmo treinado, as pessoas consigam por exemplo avaliar as condições ambientais da região em que vivem. Ou que esses dados possam ser usados pra ajudar a identificar áreas prioritárias de conservação e com isso, contribua diretamente pra qualidade do cuidado com a Caatinga. [música] Mayra: As mudanças climáticas estão aí faz tempo, infelizmente. Mas seus efeitos têm se tornado mais perceptíveis a cada ano. É urgente pensarmos em outras formas de estarmos no mundo, diminuindo os impactos ambientais, antes que esse planeta se torne inabitável, porque, como a gente também tem falado aqui no Oxigênio, não é tão simples assim achar outro planeta pra morar. Susana: Então, acho que isso tem sido fundamental para a gente criar uma comunicação científica em tempos de mudanças climáticas, que não apenas fica na denúncia dos problemas, mas que apresenta possibilidades de invenção de outros modos de habitar essa terra ferida, essa terra em ruínas. [encerra música] Mayra: Eu sou a Mayra Trinca e produzi e editei esse episódio. A revisão é da Lívia Mendes. A trilha sonora tem inserções do Freesound e de captações do projeto Escutadô e do João Bovolon, que também leu o trecho do Livro das Sonoridades. Mayra: Esse episódio é parte de uma bolsa Mídia Ciência e também conta com o apoio da FAPESP. Mayra: O Oxigênio é coordenado pela Simone Pallone e tem apoio da Secretaria Executiva de Comunicação da Unicamp. Estamos nas suas plataformas de áudio preferidas e nas redes sociais como Oxigênio Podcast. Te espero no próximo episódio! [Vinheta encerramento]

In This Episode: Solving Server Headaches With AI, Age Verification Dilemmas, and the Software Subscription fight. This week the TEH Podcast is hosted by Leo Notenboom, the “Chief Question Answerer” at Ask Leo!, and Gary Rosenzweig, the host and producer of MacMost, and mobile game developer at Clever Media. (You’ll find longer Bios on the Hosts page.) Top Stories LN: More Claude tricks 1:00 Slow server log analysis 11:00 Ask Leo! Question repository analysis 19:00 Journal recovery https://leo.notenboom.org/my-writing-journey/  21:00 LN: Age verification & Discord? https://www.techradar.com/computing/software/what-a-great-way-to-kill-your-community-discord-users-are-furious-about-its-new-age-verification-checks-and-are-now-hunting-for-alternatives 24:00 GR: Protecting children vs protecting privacy: https://9to5mac.com/2026/02/24/reddit-and-discord-are-both-in-trouble-over-controversial-age-verification-service/  To protect kids: age verification But then that violates privacy as you have to confirm your ID Another aspect: blocking kids from social media makes it harder for them to have a political voice (organize for protests, etc) 30:00 Some call for Google and Apple to take this over 34:00 Maybe we need some sort of special org? But even then how would they do both? 49:00 GR: Software subscriptions (again) You don't “own” your software Software needs updating, it isn't a consumable or physical product 1:06:00 Gary’s journal is transcribed while we talk! Ain’t it Cool 1:09:00 GR: Knight Of the Seven Kingdoms 1:10:00 LN: same BSP: Blatant Self-Promotion 1:11:00 GR: Using Text Files As a Productivity Tool 1:12:00 LN: The Nirvana Fallacy https://askleo.com/179344 Transcript teh_261 Video https://youtu.be/rqqqs9D96ZY

First guest episode of the new year with Bios Update! Listen to us babble and rabble about whether or not Meta Triangles exist, if they do exist how LSS is forcing them down our throats, and if that's actually maybe a good thing but probably not.Bios Update LinksBios Update - YouTube@biosupdate.bsky.social — BlueskyDiscord Link: https://discord.gg/JMjxmkMDSsPatreon Link: https://patreon.com/PitchItToMe?utm_medium=clipboard_copy&utm_source=copyLink&utm_campaign=creatorshare_fan&utm_content=join_linkYou can follow us at the following socials:Bluesky: https://bsky.app/profile/pitchittomepod.bsky.socialInstagram: https://www.instagram.com/pitchittomepodcastYoutube: https://www.youtube.com/@PitchItToMePodcastTimestamps:00:00 Introduction00:31 Turn Zero06:41 Defining the Meta Triangle22:50 Limited Set Design41:30 Are Meta Triangles Good1:00:30 Arsenal Zone1:16:41 OutroCredits:Host #2 -- Fuzzy DelpHost #2 -- Joel RecinosHost #2 -- Clark MooreGuest Host -- Grant "Bios Update"Executive Producer -- Talon StradleyMusic -- Dillon HulseLogo -- Han ViMix -- Christopher MooreAudio Editor -- Fuzzy DelpVideo Editor -- Clark MooreThank you to Legend Story Studios for allowing the use of their card art through their Content Creator policies and for making the game of Flesh and Blood.#fleshandbloodtcg #tradingcards #gamedesign #podcast #legendstorystudios #fabtcg #pitm #pitchittome #meta #draft #fabtcg

LEITURA BÍBLICA DO DIA: SALMO 13 PLANO DE LEITURA ANUAL: LEVÍTICO 26–27; MARCOS 2   Já fez seu devocional hoje? Aproveite e marque um amigo para fazer junto com você! Confira:  O Reino Unido transborda história. Onde quer que se vá, há placas homenageando figuras históricas ou comemorando locais de eventos importantes. Mas um desses locais exemplifica o senso de humor britânico. Em uma placa desgastada do lado de fora de uma pousada na Inglaterra, uma mensagem diz: “Neste local, 5 de setembro de 1782, nada aconteceu”. Às vezes, parece-nos que nada acontece em relação às nos sas orações. Oramos e oramos, levando os nossos pedidos ao Pai na expectativa de que Ele os responderá de imediato. O salmista Davi expressou tal frustração ao orar: “Até quando, Senhor, te esquecerás de mim? Será para sempre?” (SALMO 13:1). Podemos ecoar esses mesmos pensamentos: “Quanto tempo, Senhor, antes de responder-me?”. No entanto, Deus não é apenas perfeito em Sua sabedoria, mas também em Seu tempo. Davi pôde dizer: “Eu, porém, confio em teu amor; por teu livramento me alegrarei” (v.5). Eclesiastes 3:11 nos relembra: “Deus fez tudo apropriado para seu devido tempo”. A palavra apropriado pode significar “belo” ou “fonte de deleite”. Talvez Deus nem sempre responda às nossas orações na hora que desejamos, mas Ele está sempre cumprindo os Seus sábios propósitos. Tenhamos certeza de que, quando Deus responder, será no tempo certo, será bom e será belo.   Por: BILL CROWDER  

Another week, another series of distressing developments in the world of PC hardware. But maybe the end of the madness is near?  Or at least hotter with 700W Intel CPUs.  BTW, you're probably not getting an RTX 5090Ti, another week where DIMMs are bling, some questionable choices from Microsoft and scary security issues with certs, 7-Zip, OpenClaw, and "Approve or Deny?" questions.  Thanks Zapier for sponsoring our show this week!   Get AI orchestration going on your workflows for improvements you can really help, for free!Timestamps:0:00 Intro01:05 Patron01:37 Food with Josh03:54 ASRock BIOS update to combat reported Ryzen failures05:47 Intel's potential processor power09:35 No RTX 5090 Ti this year11:35 G.Skill memory speed settlement14:44 The Discord drama19:21 HP will rent you an Omen gaming laptop24:48 Microsoft failed to communicate about 26H131:36 Homelab bling32:58 Podcast sponsor - Zapier34:26 (In)Security Corner48:37 Gaming Quick Hits55:19 Picks of the Week1:09:55 Outro ★ Support this podcast on Patreon ★

In This Episode: The Internet Archive saves an old car. AI Bird IDs. Claude code. Ringing Lost Dogs. This week the TEH Podcast is hosted by Leo Notenboom, the “Chief Question Answerer” at Ask Leo!, and Gary Rosenzweig, the host and producer of MacMost, and mobile game developer at Clever Media. (You’ll find longer Bios on the Hosts page.) Top Stories 0:00 LN: Internet Archive to the rescue My wife is visiting my sister-in-law, and the parking brake in her 2000 Honda CRV (originally my mother’s car) froze up. The pull-lever i the center wouldn't budge. I got messaged for help. I searched for “2000 honda crv maintenance manual”. The second entry is The Internet Archive's scan of the ~1400 page manual. https://archive.org/details/HondaCRV19972000  I was able to send her images from the manual about how to access and lubricate the pull lever. This isn't the first time IA has popped up randomly to help. It's an amazing resource. 5:45 LN: What bird is  that? Another story of things coming together. My wife takes a photo with her phone (Pixel 4a) of a hawk sitting on a fence in our neighborhood. https://flic.kr/p/2rVhrLG  The photo is auto-uploaded to her Google Photos account. I grab a copy and crop it. Original is 4032×3024, so there are lots of opportunities. Not bad. https://flic.kr/p/2rVjh8d  7:00 I fire up Topaz Gigapixel AI, and, with a little adjustment of settings, upscale the image 4x. I then crop it further to focus more closely on the bird. Also not bad, though there are some tell-tale signs that this was AI upscaled. https://flic.kr/p/2rVisjk  9:15 My wife asks me what kind of hawk that might be. No clue. So I decided to try … ChatGPT. I upload the upscaled image, and ask simply, “What kind of bird is this?” Likely ID: Red-tailed Hawk (juvenile) Based on the bulky buteo shape, overall brown upperparts, the pale “checkerboard” pattern on the wings, and the strongly banded tail (common in young birds before they develop the classic red tail), this looks most consistent with a juvenile Red-tailed Hawk. We do indeed have red-tailed hawks around here. It’s interesting that it ID'd a juvenile. 15:00 Identify birds. https://merlin.allaboutbirds.org/  18:00 LN: Claude Code Installed on my PC because it promised to be able to work on local data 20:00 Non-trivial install (at least for Windows – WSL, and then you're running in an Ubuntu bash shell). 21:10 Scenario 1: My Obsidian vault – all plain text (.md) files. I can now ask questions and run analyses across the entire collection of notes. 24:00 Scenario 2a: My personal blog. Pointed it at leo.notenboom.org – did OK, but incomplete. 25:00 Scenario 2b: exported by personal blog content from WordPress as an XML file. Dense, lots of cruft. Gave that to Claude and got a very complete, detailed analysis / summary of what I've been doing there since 2004. 27:00 Scenario 3: downloaded the contents of 23 years of Ask Leo! Articles. https://askleo.com/ask-leo-analysis-via-claude-code/  38:00 GR: Ring Doorbell Superbowl Ad ? Pretty sure I was “ringing this bell” many years ago right here LN: We Rate Dogs take on it: https://www.tiktok.com/@weratedogs/video/7605333665031245069 Ain’t it Cool GR: Dungeon Crawler Carl LN: Archive.org BSP: Blatant Self-Promotion LN: Managing Windows File Explorer's Navigation Pane – https://askleo.com/188995 GR: How To Keep Using Pages, Numbers and Keynote If You Don’t Want Apple Creator Studio Transcript teh_260 Video https://youtu.be/Q7JXOLNvLi4

Love Is Blind has traveled back to the Midwest and this time we're in Ohio! Lord, please let this season give us better men than Joey, Devin, David, and Judas… Let 1-800 Contacts get you the contact lenses you need right now. Order online at ⁠1800CONTACTS.COM or download the free 1-800 Contacts app today. This episode is brought to you by Quince. To get the softest towels, the best sheets, and the chicest accessories, go to ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠www.quince.com/2bg1r⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ for free shipping and returns on us! Listen to our PRE-SHOW and watch us on VIDEO only on Patreon. ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Join the Rose Garden today⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠! CONNECT WITH US: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Instagram⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Twitter⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠TikTok⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Merch⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ EMAIL: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠2blackgirls1rose@gmail.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Follow Natasha's Substack The Nite Owl: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠theniteowl.substack.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Learn more about your ad choices. Visit podcastchoices.com/adchoices

Send us a textA surprising number of security leaders admit they're flying blind on hardware and firmware. We start by exposing how shared BIOS passwords, slow maintenance cycles, and careless e‑waste practices create avoidable risk, then lay out the fixes: privileged vaulting, disciplined asset disposition, and practical ways to repurpose gear without leaking data. That real-world foundation sets the stage for a focused tour through CISSP Domain 5—Identity and Access Management—built for practitioners who want clarity over jargon.We break down least privilege in plain terms and show how to reduce the initial friction with cleanly defined roles and entitlement catalogs. From there, we compare RBAC and ABAC: when baseline roles are enough, and when context-aware attributes like device, location, and data sensitivity should drive policy. Authentication gets the same treatment. Multi-factor authentication, biometrics, and phishing-resistant methods raise the bar, while single sign-on and identity federation streamline access across cloud apps using standards like OAuth, OpenID Connect, and SAML. In modern cloud environments, token-based models win for scalability and security, and we explain why.Governance ties it all together. We walk through identity proofing for solid onboarding, separation of duties to curb fraud, and IGA workflows that make approvals, recertifications, and audits far less painful. Regular access reviews emerge as the unsung hero that prevents privilege creep before it becomes an incident. If you're prepping for the CISSP—or just tightening your IAM program—this episode gives you the why behind the what, with steps you can apply today.Enjoyed the conversation and want more deep dives? Subscribe, share with a teammate who needs a quick IAM refresher, and leave a review to help others find the show.Gain exclusive access to 360 FREE CISSP Practice Questions at FreeCISSPQuestions.com and have them delivered directly to your inbox! Don't miss this valuable opportunity to strengthen your CISSP exam preparation and boost your chances of certification success. Join now and start your journey toward CISSP mastery today!

professorjrod@gmail.comAre you preparing for the CompTIA exam or looking to boost your IT skills development? This episode dives deep into Windows troubleshooting with a focus on network diagnostics — a crucial topic for any tech exam prep. We guide you through validating a Windows machine's network identity using IPConfig, performing a strict ping sequence to verify communication scope, and utilizing NSLookup to troubleshoot DNS issues. Following this disciplined order ensures clarity and efficiency, making every fix both defensible and effective. Whether you're studying solo or in a study group, this step-by-step approach to Windows networking will enhance your technology education and help you succeed in your IT certification journey.We dig into why a 169.254 APIPA address narrows the culprit to DHCP or network infrastructure, not the NIC or OS. Then we connect the dots between ports and services using Netstat, making it clear when a service is misconfigured rather than the network being “down.” From web ports 80 and 443 to SMB 445 and RDP 3389, you'll see how listening states reveal the true problem fast.Powerful remote access demands restraint. We break down when RDP makes sense, why Network Level Authentication should be non-negotiable, and how consent-based Remote Assist reduces risk when users need to stay in control. For scale, we highlight WinRM over HTTPS and SSH as secure, script-friendly options that keep credentials protected and GUIs out of the attack surface.Performance complaints need evidence, not guesswork. We show how Task Manager, Resource Monitor, Performance Monitor, and Event Viewer combine to reveal bottlenecks, crashes, and policy blocks. When things get critical—no boot, blue screens—we map BIOS vs UEFI realities, then use WinRE tools in the safest order to recover without data loss. By the end, you'll have a repeatable framework: identity, routing, names, services, performance, platform, recovery. Subscribe, share with a teammate who still starts with the browser, and tell us: what's your first command when “nothing works”?Support the showArt By Sarah/DesmondMusic by Joakim KarudLittle chacha ProductionsJuan Rodriguez can be reached atTikTok @ProfessorJrodProfessorJRod@gmail.com@Prof_JRodInstagram ProfessorJRod

Register your feedback here. Always good to hear from you!I'm joined by two eminently honorable preachers of the gospel – Noah Diestelkamp and BJ Sipe. Bios and links are provided below; make sure you check out their outstanding work in the kingdom. I asked them to comment on Biblical honor, starting with the way we show honor to one another as Christians. I think you'll be blessed by what they have to say. A word of caution first: it may wind up hitting you in your wallet.Noah Diestelkamp, husband and father of three, works with the Cedar Park church of Christ in the Austin area. He and Paul White host the Stand Strong Podcast. Check it out at https://standstrong.buzzsprout.com/BJ Sipe, also a husband and father of three, is with the church of Christ in Danville, Kentucky. Go to https://www.youtube.com/watch?v=rl3Ug77n1gc for links to simulcasts from the work at Danville and to https://setyourmindabove.buzzsprout.com/ to find the Set Your Mind Above podcast.Check out Hal on YouTube at https://www.youtube.com/@halhammons9705Hal Hammons serves as preacher and shepherd for the Lakewoods Drive church of Christ in Georgetown, Texas. He is the host of the Citizen of Heaven podcast. You are encouraged to seek him and the Lakewoods Drive church through Facebook and other social media. Lakewoods Drive is an autonomous group of Christians dedicated to praising God, teaching the gospel to all who will hear, training Christians in righteousness, and serving our God and one another faithfully. We believe the Bible is God's word, that Jesus died on the cross for our sins, that heaven is our home, and that we have work to do here while we wait. Regular topics of discussion and conversation include: Christians, Jesus, obedience, faith, grace, baptism, New Testament, Old Testament, authority, gospel, fellowship, justice, mercy, faithfulness, forgiveness, Twenty Pages a Week, Bible reading, heaven, hell, virtues, character, denominations, submission, service, character, COVID-19, assembly, Lord's Supper, online, social media, YouTube, Facebook.

Pete Cherry VK2LP the Returning Officer of the Wireless Institute of Australia. - Lee Moyle VK3GK WIA Director. - Roger Harrison VK2ZRH, Editor-in-Chief of Amateur Radio magazine. - Following on from last few weeks "BIOS" of candidates for this years WIA AGM Election we here from Justin VK7TW. - And the tragic news which swept the airwaves this week, the death of Mobile Ones VK4BBX.

In This Episode: AI is still dumb. Who’s in charge of TikTok? The death of Gmail Import. This week the TEH Podcast is hosted by Leo Notenboom, the “Chief Question Answerer” at Ask Leo!, and Gary Rosenzweig, the host and producer of MacMost, and mobile game developer at Clever Media. (You’ll find longer Bios on the Hosts page.) Top Stories 0:30 LN: Been playing with Jan https://www.jan.ai/  2:15 So MANY online AIs: ChatGPT, Copilot, Claude, Gemini, & others 3:35 Privacy-focused: Proton's Lumo Self-hosted: Jan (ultimate privacy?) – biggest complication is figuring out what LLM model to use 9:00 GR: Claud bot 10:00 Don’t let AI decide things for you 14:40 GR: Who owns TikTok now? 15:50 TikTok is now owned (80%) by an investor group Oracle houses data (Larry Ellison)  Was owned by Chinese ByteDance before (still 20%) Should you keep watching? (honestly can't decide) 21:00 Alternatives: YouTube Shorts is getting better, Instagram 26:00 GR: mobile journalism tips 30:00 Practice “quick draw” filming with your mobile phone Familiarize yourself with your camera resolution and upload settings LN: auto-backup to cloud 37:00 Remember if a friend is filming, you film too. Heck, film them filming things. 44:00 LN: The death of “Check mail from other accounts:” took me down a path FastMail  48:00 Proton mail for security 53:00 Google Workspace for Nonprofits Ain’t it Cool 55:10 GR: Sinners (HBO Max) BSP: Blatant Self-Promotion 1:00:06 LN: Why Am I Seeing So Many CAPTCHAs? – askleo.com/187517 1:01:10 GR: https://macmost.com/10-secrets-of-the-mac-dock.html Transcript teh_259 Video https://youtu.be/XBe01I-Flmg

In This Episode: Brief episode description This week the TEH Podcast is hosted by Leo Notenboom, the “Chief Question Answerer” at Ask Leo!, and Gary Rosenzweig, the host and producer of MacMost, and mobile game developer at Clever Media. (You’ll find longer Bios on the Hosts page.) Top Stories 0:00 LN: Gravity always wins 6:00 LN: My new machine (you know, a “present” for getting sick?) AMD Ryzen Threadripper 9960X 24-Cores, 4200 Mhz 128GB NVIDIA GeForce RTX 5090 (and how I backed into this) 12:00 Davinci Resolve “speed editor” 13:00 GR: Apple Creator Studio https://www.apple.com/apple-creator-studio/ Is it “freemium?” 24:00 LN: Afinity and Canva 25:00 So many subscriptions! Good and bad 28:00 GR: Strudel.cc  https://www.youtube.com/watch?v=iu5rnQkfO6M 33:00 GR: AI fakes aren't always going to be someone talking and saying something they didn't.  https://www.snopes.com/fact-check/renee-good-car-ice-image 35:00 Believe what you want to believe 37:00 GR: Subscribe to Snopes Snopes Newsletters: https://www.snopes.com/newsletters/ 41:00 Studying media bias 42:00 GR: Connections in the wilderness Satellite text messages, not just for emergrncies 45:00 LN: Recent outage when everyone's phone only said SOS? Ain’t it Cool 46:00 LN: Google Recorder (Pixel) – a tool I relied on 49:00 GR: Mark Twain by Ron Chernow (Audible) BSP: Blatant Self-Promotion 53:00 LN:  An Unexpected Way Videos Can Expose Your Location – askleo.com/167448 56:00 GR: https://macmost.com/why-ai-cant-replace-tech-help-yet.html Why AI Can't Replace Tech Help (Yet) Transcript teh_258 Video https://youtu.be/MwCkLv4RjLY

The theme for today's episode is familiarity. We all love familiarity, it's comforting, it feels safe, and it gives us a sense of belonging, which has a huge impact on your online presence. We'll look at real examples from creators that cultivate this sense of familiarity through scenarios, locations, and identifiers, making their audience instantly feel seen and at home. We'll also discuss the viral 2016 Instagram trend and the psychology behind why we tend to gravitate towards scenarios we recognize. In this episode we'll be covering:Making your content feel familiar to your audience and the impact it has on trust and engagement.The emotional safety and belonging that comes from familiar relationships, and how to evoke a similar feeling through your content.The role that nostalgia and simpler times plays in content right now, reminiscing about significant or everyday moments and the feelings that it creates.Why familiarity works in content, attracting and retaining viewers, offering connection and belonging.How to create familiarity in your content with trial reels, identifiers, and crafting scenarios that are relevant to everyday and lived experiences.Featured content in this episode:Inside Edition Interview on YouTubeKay.harike: Stranger Things New Years Eve PartySmillagrundholm: One day closer…Everythingemili: New taco night favAshroedl: Road trip and 2016 playlistEverydaywithmandy: Mom to momShannonmckinstrie: 2016 Trend PostRecommended episodes:Episode 081: Your Next Powerful Piece of Content is Already on Your PhoneEpisode 085: Start Thinking Like a Marketer So People See Themselves in Your ContentEpisode 087: How to Get New Followers on Instagram: Trial Reels, Bios, and More!Episode 091: Here's What Good Content Will Look Like in 2026Episode 095: Building Real Community with Stories and Shared MomentsSend a message!If you use the send a message option above, be sure to include your email address if you would like a reply! (Please allow 3-5 business days for a response) Join me in the Reels Lab! Love this conversation? Make sure to follow and subscribe so you never miss an episode. Connect with me on Instagram!

Computer Talk with TAB starting its 30th year on WTIC News Talk 1080! My Smart lock got stupid, My laptop will not charge, What do I do with OpenDNS not able to configure on my Win 11 system. How do I get access to my AT&T email account? Should I consider Proton Mail? Win 10 to Win 11 upgrade but can't get Bios to Post after change.

In deze aflevering hebben we het over de man die nu al de machtigste bankier van de wereld genoemd wordt, maar niet de machtigste man van de financiële markten wil worden. Een baan waar de meeste mensen (in de VS) een moord voor zouden doen. Maar niet Jamie Dimon, over wie dit gaat. Hij wil niet de opvolger worden van Fed-baas Jerome Powell. Powell die overigens nog steeds moet vrezen voor een strafrechtelijk onderzoek. Verder hebben we het over enorme deals. Over de handelsdeal tussen Taiwan en de VS. Taiwan gaat maar liefst 250 miljard dollar investeren. Een deal die mogelijk ook de toekomst van het land kan redden. Taiwan vreest namelijk nog steeds voor een invasie van China. Over China gesproken: dat sluit een handelsdeal met Canada. Ben je al klaar met deals? Jammer dan, want we hebben het ook nog even over de miljardendeal die Netflix sluit. Geen overname dit keer, maar een dealtje met Sony. Waardoor je binnenkort nog meer films kan gaan streamen. Verder deze aflevering: Amerikaanse banken verdienen gigantisch veel aan het onzekere beleid van Trump Paramount lobbyt in Europa voor de overname van Warner Bros. Autobouwers moeten stoppen met hun prijzenoorlog, zegt de toezichthouder De hoogte- en dieptepunt uit ruim 40 jaar AEX-handel Te gast: Nico Inberg, van De AandeelhouderSee omnystudio.com/listener for privacy information.

Sábios vivem melhor. Alguns têm expectativas boas quando o novo ano chega, mas isso só se concretiza por meio de atos de sabedoria. Às vezes não entendemos como comportamentos ruins nos acompanham mesmo com muitas coisas tendo mudado em nossas vidas. Mas a verdade é que não basta apenas bênçãos se não somos capazes de observar nossos erros e buscar corrigi-los.

An airhacks.fm conversation with Alvaro Hernandez (@ahachete) about: discussion about LLMs generating Java code with BCE patterns and architectural rules, Java being 20-30% better for LLM code generation than python and typescript, embedding business knowledge in Java source code for LLM context, stackgres as a curated opinionated stack for running Postgres on kubernetes, Postgres requiring external tools for connection pooling and high availability and backup and monitoring, StackGres as a Helm package and Kubernetes operator, comparison with oxide hardware for on-premise cloud environments, experimenting with Incus for system containers and VMS, limitations of Ansible for infrastructure automation and code reuse, Kubernetes as an API-driven architecture abstracting compute and storage, Custom Resource Definitions (CRDs) for declarative Postgres cluster management, StackGres supporting sharding with automated multi-cluster deployment, 13 lines of YAML to create 60-node sharded clusters, three interfaces for StackGres including CRDs and web console and REST API, operator written in Java with quarkus unlike typical Go-based operators, Google study showing Java faster than Go, GraalVM native compilation for 80MB container images versus 400-500MB JVM images, fabric8 Kubernetes client for API communication, reconciliation cycle running every 10 seconds to maintain desired state, pod local controller as Quarkus sidecar for local Postgres operations, dynamic extension installation without rebuilding container images, grpc bi-directional communication between control plane and control nodes, inverse connection pattern where nodes initiate connections to control plane, comparison with Jini and JavaSpaces leasing concepts from Sun Microsystems, quarter million lines of Java code in the operator mostly POJOs predating records, PostgreSQL configuration validation with 300+ parameters, automated tuning applied by default in StackGres, potential for LLM-driven optimization with clone clusters for testing, Framework Computer laptop automation with Ubuntu auto-install and Ansible and Nix, five to ten minute full system reinstall including BIOS updates Alvaro Hernandez on twitter: @ahachete

Happy New Year! In this episode, Automox cybersecurity experts Ryan Braunstein and Seth Hoyt break down the security vulnerabilities you need to know heading into 2026.First up: a ticking time bomb. Microsoft's 2011 Secure Boot certificates expire in June and October 2026, making this your top patching priority for the year. If your BIOS and OS aren't both updated, you're leaving the door wide open for rootkit attacks. Start auditing your hardware now. You have six months.Next up: a Windows Installer Elevation of Privilege Vulnerability that exploits a time-of-check to time-of-use (TOCTOU) race condition. Think of it like swapping wristbands after the bouncer checks you at the door.Finally, an actively exploited flaw in Desktop Window Manager that can leak sensitive information and even break out of sandboxes.Patch your systems. Patch your BIOS. See you next month.

Para empezar, diré que es el final. El final de este año 2025 que muchos pensamos que se puede ir muy lejos a tomar por c* y a ver si el 26 remonta. En este programa empezamos hablando de cómo Javi ha hecho magia en la BIOS para que su PC funcione como debe, Jorge habla de juegos de mesa, leemos correos y comentarios, Javi expone su teoría sobre las trabajadoras de Mercadona (fácilmente malinterpretable si tienes la piel fina), Jorge nos cuenta cuánto le gusta el ARC RIDERS y cómo fue el Salón del Videojuego... en fin, un programa de fin de año cargadito. Esperamos que tengáis un genial 2026 y nos podamos seguir escuchando por mucho tiempo.

Be sure to visit https://dwtbpodcast.com for more information and add your name to start receiving their newsletter. If you'd like to support this show, rate, subscribe and leave a review on your podcast app.Books/Resources Mentioned:Children's Illustrator (My Money Bunnies and others), Eevi JonesThe Biology of Trauma, by Aimie ApigianAJ's Authorship Planning WorkshopConnect with AJ & Mike:AJ Harper, website Write A Must-Read  Free resourcesAJ's Socials:FacebookLinkedInMike Michalowicz, websiteAll books Mike's Socials: IGFBLinkedIn

Por Pr. Silvanir Alves. | https://bbcst.net/B9486M

Trump signs the National Defense Authorization Act for 2026. Danish intelligence officials accuse Russia of orchestrating cyberattacks against critical infrastructure.  LongNosedGoblin targets government institutions across Southeast Asia and Japan. A new Android botnet infects nearly two million devices. WatchGuard patches its Firebox firewalls. Amazon blocks more than 1,800 North Korean operatives from joining its workforce. CISA releases nine new Industrial Control Systems advisories. The U.S. Sentencing Commission seeks public input on deepfakes. Prosecutors indict 54 in a large-scale ATM jackpotting conspiracy. Our guest is Nitay Milner, CEO of Orion Security, discussing the issue with data leaking into AI tools, and how CISOs must prioritize DLP. Riot Games finds cheaters hiding in the BIOS. Remember to leave us a 5-star rating and review in your favorite podcast app. Miss an episode? Sign-up for our daily intelligence roundup, Daily Briefing, and you'll never miss a beat. And be sure to follow CyberWire Daily on LinkedIn. CyberWire Guest Nitay Milner, CEO of Orion Security, discusses the issue with data leaking into AI tools, and how CISOs must prioritize DLP. Selected Reading Trump signs defense bill allocating millions for Cyber Command, mandating Pentagon phone security (The Record) Denmark blames Russia for destructive cyberattack on water utility (Bleeping Computer) New China-linked hacker group spies on governments in Southeast Asia, Japan (The Record) 'Kimwolf' Android Botnet Ensnares 1.8 Million Devices (SecurityWeek) New critical WatchGuard Firebox firewall flaw exploited in attacks (Bleeping Computer) Amazon blocked 1,800 suspected DPRK job applicants (The Register) CISA Releases Nine Industrial Control Systems Advisories (CISA.gov) U.S. Sentencing Commission seeks input on criminal penalties for deepfakes (CyberScoop) US Charges 54 in Massive ATM Jackpotting Conspiracy (Infosecurity Magazine) Riot Games found a motherboard security flaw that helps PC cheaters (The Verge) Share your feedback. What do you think about CyberWire Daily? Please take a few minutes to share your thoughts with us by completing our brief listener survey. Thank you for helping us continue to improve our show. Want to hear your company in the show? N2K CyberWire helps you reach the industry's most influential leaders and operators, while building visibility, authority, and connectivity across the cybersecurity community. Learn more at sponsor.thecyberwire.com. The CyberWire is a production of N2K Networks, your source for strategic workforce intelligence. © N2K Networks, Inc. Learn more about your ad choices. Visit megaphone.fm/adchoices

This week on Destination Linux, we are joined by a special guest host: Craig Rowland, the CEO of Sandfly Security! We're diving deep into the reality of modern security—specifically when third-party code knocks over your castle. From malicious VSCode extensions to the "React2Shell" vulnerability, we discuss why "Open Source" doesn't automatically mean "Safe" and how to protect your supply chain. Then, is it possible to have the macOS experience without the Apple ecosystem? Ryan explores ravynOS, a daring new project with "macOS vibes and a BSD soul." It's attempting to bring the Aqua interface—and eventually Mac app compatibility—to the open-source world. Plus, Jill brings us massive news from Canonical and AMI. You might soon be installing Ubuntu directly from your motherboard's BIOS without ever needing a USB drive. We break down how this partnership changes the game for hardware. Finally, we read an incredible listener story. Show Notes: 00:00:00 Intro 00:02:39 Extended Intro: Open Source or Bust 00:03:08 Community Feedback: A Pentester's Origin Story 00:10:03 Guest Host: Sandfly Security & Agentless Protection 00:15:53 Security Deep Dive: Supply Chain Attacks, Malicious VSCode Extensions & React2Shell 00:44:31 ravynOS: The Open Source Mac Killer? 00:56:05 News: Canonical + AMI: Installing Ubuntu from the BIOS 01:08:07 Outro 01:09:33 Post-Show Shenanigans Support the Show: Sponsored by Sandfly Security: destinationlinux.net/sandfly - Get 50% off the Home Edition with code DESTINATION50 Special Guest: Craig Rowland.

What happens when coaching meets improv? In this episode, Cathy Sykora speaks with Betsy Salkind and Amy Warshawsky, co-authors of Coaching with a Twist: Improv for Coaches. With backgrounds in health coaching, leadership, somatics, and comedy, Betsy and Amy have created a dynamic and experiential approach to coach training that blends improv exercises with foundational coaching skills. They explain how play and presence deepen learning, increase client connection, and make coaching more effective—and more fun. Whether you're a seasoned coach or just starting out, their fresh take on training and development is both practical and transformative. In this episode, you'll discover: How Betsy and Amy transitioned from mentor coaches to co-creators of an improv-based coaching model The similarities between improv and motivational interviewing Why experiential learning is more "sticky" than traditional training methods How play and improvisation enhance presence, creativity, and emotional regulation Why they created a safe, supportive environment for learning through coaching with a twist A powerful improv exercise called "three-word coaching" you can try today The benefits of supervision and their monthly BNA Coaching Salon Memorable Quotes: "Ultimately, if we are coaching well, we're improvising." "No rules, only happy accidents." "When you're playing and having fun, you are not in fear." Bios:  Betsy Salkind, PCC, NBC-HWC, is a health and mentor coach with expertise in team, group, and leadership coaching. A professional standup comic and TV writer, she trained at the Mayo Clinic and holds an MS in Organization Studies from MIT Sloan. Amy J. Warshawsky, MCC, NBC-HWC, is a leadership and mentor coach known for integrating somatic practices into coaching. She has held roles in nonprofit and higher education, and holds degrees from Northwestern University and Cornell. Together, they co-founded BNA Mentor Coaching and co-authored Coaching with a Twist: Improv for Coaches. Mentioned in This Episode: BNA Mentor Coaching Coaching with a Twist: Improv for Coaches Links to Resources: Health Coach Group Website: thehealthcoachgroup.com (https://www.thehealthcoachgroup.com) Special Offer: Use code HCC50 to save $50 on the Health Coach Group website Leave a Review: If you enjoyed the podcast, please consider leaving a five-star rating or review on Apple Podcasts.

Holly and Alexis are LIVE from Children's Theatre Company, joined by Managing Director Ryan. They also share the appeal of trendy Instagram bios.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Archive, Bios, Description, and Transcripts for Episode 148: Housing, Disability Rights, and Planning Accessible Communities available at https://adalive.org/episodes/episode-148/ Professor Robin Malloy and Dr. Peter Blanck discussed the complexities of housing rights for people with disabilities, emphasizing the intersection of the Americans with Disabilities Act (ADA) and zoning laws. Robin highlighted the challenges of obtaining reasonable accommodations, such as ramps and therapeutic pools, and the importance of creating a legal record. He shared examples of zoning board decisions and the impact of neighbor objections. Robin also discussed the broader implications of accessibility, including the need for government to address homelessness without infringing on disability rights. The conversation underscored the need for better education and collaboration between disability rights advocates and land use professionals.

"And then he found something else to beat him with and that as the first time I almost vomited during this movie."Miki and Phil are back to discuss biopics (or do you pronounce it "biopics"?)! Turns out people have bleak lives! Bleak!0:00 -- Intro7:51 -- 12 Years a Slave40:05 -- The Imitation Game1:27:39 -- I, Tonya2:10:36 -- Contact information2:11:24 -- Awards and rankings3:16:49 -- Future business3:20:26 -- Outro and outtakes {ymt 182}!Hey! Be sure to watch Miracle on 34th Street, Elf, and The Family Stone for next time!Hey! We have a Patreon (Ours, Ours, & Ours))!Hey! DON'T leave us a voicemail at (801) 896-####!Hey! Shop the Zazzle store! Hey! Hear In Memoriam! Hey! Hear Fantasy Murder Love Triangle! Hey! Hear J.R. Watches Star Trek for the first time!Hey! Auditions for 12 Years a Slave (not really though)!Hey! Randy Newman's 12 Years a Slave theme song (actually a parody song from Eric D. Snider)!Hey! You're Wrong About Tonya Harding!Hey! Sarah Marshall's Tonya Harding essay!Hey! Subscribe in iTunes! Hey! Check out the Facebook page and vote on the next category! Hey! Check out Jon's YM&T Letterboxd list!Hey! Check out Roy's YM&T Letterboxd list! Hey! Email us at yoursminetheirspodcast@gmail.com! Send new topics! Send new theme songs!

In This Episode: When the Internet Was Not Down: Cloudflare, Outages, and Automatic Buying. This week the TEH Podcast is hosted by Leo Notenboom, the “Chief Question Answerer” at Ask Leo!, and Gary Rosenzweig, the host and producer of MacMost, and mobile game developer at Clever Media. (You’ll find longer Bios on the Hosts page.) Top Stories 0:00 LN: Cloudflare, and reliance on large providers Is it inevitable? 5:00 How good are services at fixing and acknowledging 6:30 Go to the internet to announce the internet is down 7:00 GR: Finding Cloudflare down Bot detection 11:00 VPNs 13:30 False consensus… what’s really wrong? 17:10 LN: Amazon versus Perplexity and agents Shopping agents I don't yet trust AI agents. At all. Certainly not with my credit card. 26:00 GR: Cosmetic changes 27:40 OCD? 31:00 Windows desktop 34:00 Spam! 35:00 LN: Over-reliance on vibe coding? Is there a HUGE data breach or other security issue in our future due to someone's over-reliance on vibe coding? Ain’t it Cool 39:50 GR: Flybot by Dennis E Taylor – https://www.goodreads.com/book/show/232957226-flybot 42:35 LN: Pluribus – Apple TV – https://www.imdb.com/title/tt22202452/ – New take on “Invasion of the Body Snatchers” BSP: Blatant Self-Promotion 45:00 LN: What Happens If I Don't Update to Windows 11? – https://askleo.com/186512 45:50 GR: Using Apple Intelligence and Shortcuts To Rename Files  https://macmost.com/using-apple-intelligence-and-shortcuts-to-rename-files.html  Video https://youtu.be/_fG_giYg4AE Transcript teh_257

What an awesome opportunity we have today to chat with Jay Paterno, the son of legendary Penn State University Coach, Joe Paterno. With his most recent book, "Blitzed" coming out recently, we'll chat with Jay about the contents of the book and how the landscape of college football continues to change, which is leaving coaches and players alike with a need to adapt!  There are so many additional pressures with NIL coming into play. The money brings so many pressures. Do coaches have shorter leashes while coaching now? Do the expectations change from fanbases and donors now with all this money playing a factor?  How does this impact recruiting? How does this impact retention and keeping rosters intact?  What does Jay think about potentially having a collective bargaining agreement in college athletics?  What about betting? How has gambling had an impact on sports? Fans, coaches, players, referees alike? We get to hear some of his favorite memories and some of the great lessons he learned along with his father!  Come checkout this awesome conversation and snag your copy of the book so you can dive into it even deeper!  Follow Jay:  SOCIAL MEDIA: https://www.facebook.com/jaypaternoforpa/ https://twitter.com/JayPaterno https://www.linkedin.com/in/jaypaterno/ https://www.youtube.com/@nittanygameweek4442/featured https://www.instagram.com/jayvpaterno/ BIOS: https://jaypaterno.onlinepresskit247.com/about.html IMAGES: https://jaypaterno.onlinepresskit247.com/image-gallery.html WEBSITE: https://www.jayvpaterno.com/ BLITZED on Amazon: https://www.amazon.com/Blitzed-All-Out-Pressure-College-Footballs/dp/B0DFW82ZT5/ Thanks for tuning in and if you enjoy this episode, please consider giving me a follow here on YouTube to help me build out this platform!  #JayPaterno #PennStateFootball #Coaching #Author 

If you're going to spend time on social media, {{ subscriber.first_name | default: “my friend” }}, make it count. As you've liiiiikely experienced, social media is a major time suck by design. No one is immune. One minute I'm looking at a business owner's account for tips on hiring, and the next thing I know it's been 30 minutes and I've watched:

Let's talk about real strategies for getting new Instagram followers, especially as social media has evolved and people have become a lot more selective when it comes to hitting that follow button. I'm breaking down what actually makes someone want to follow you, including how to optimize your bio, pinned posts, and stories to create a magnetic profile, and why trial reels are still one of the best tools for attracting fresh eyes, even if they don't go viral. In this episode we'll be covering:How to think like a user, what makes you hit follow on an account? The strategy I use for trial reels that consistently brings in new followers to my account.Why is Instagram really giving those warning messages and should you be worried?How to prevent a trial reel from sharing to your account. Creating an irresistible Instagram profile with an optimized account bio, purposeful pinned posts, and daily engaging stories.Don't have access to Trial Reels yet? Try this hack and let us know if it works for you!​​Step 1: Go to this URL on your phone (https://creators.instagram.com/blog/instagram-trial-reels?locale=en_GB)Step 2: Click the ‘Create Reel' buttonStep 3: This will open IG to upload or create a video. Press next, make any edits, etc., then press next again to fill out the caption etc. You should see a toggle to select “Trial Reel” (This is a trial reel and will only be shown to non-followers at first.) Post when you're ready!Step 4: Repeat the process and upload as many as you want. After a while the feature will just be on your account.Additional step: if you ever lose the feature after you had it, just repeat the step-by-step and you'll get access to it again.Recommended episodes:Episode 019: Convert Viewers to Followers with the “That's Me” ReelEpisode 020: SEO Strategies to Optimize Your Instagram ContentEpisode 040: Build More Connections with Everyday MomentsEpisode 050: Stories Work! Here's how to make them work for YOUEpisode 071: Start a New Instagram Account From Scratch (or Refresh Your Current One)Episode 073: Staying Top of Mind with Instagram StoriesSend a message!If you use the send a message option above, be sure to include your email address if you would like a reply! (Please allow 3-5 business days for a response) Join me in the Reels Lab! Love this conversation? Make sure to follow and subscribe so you never miss an episode. Connect with me on Instagram!

Met vandaag: D66 en CDA moeten alvast nadenken over een regeerakkoord | Eurocommissaris Wopke Hoekstra over de VN-klimaattop | Dichter der Nederlanden Babs Gons werd twee jaar lang gevolgd voor een documentaire | Back to the Future na 40 jaar terug in de bioscopen |  Presentatie: Chris Kijne

Daniella and Barbaranne recap their current events while trying to make aches and pains Rock n Roll. Daniella and Gilby head to Judas Priest and Alice Cooper. Zakk drags Barbaranne to the Mr. Olympia in Las Vegas while they are there for Charlie and Carla Benante's star studded, fabulous wedding. They see the Wizard of Oz at the Sphere and also renew their vows at the Chapel of Crystals. Of course there is a new #flicsaf and #barbsbagoftricks and the ladies are so excited to announce their new HonestAF Show Storefront in Sephora. Please note that the ladies will make a small commission should you purchase any of their picks using their links. No gatekeeping beauty here! Happy shopping Beauties! Links in all our Bios for the Sephora Storefront. Learn more about your ad choices. Visit megaphone.fm/adchoices

"Naquele tempo, respondendo Jesus, disse: Graças Te dou, ó Pai, Senhor do Céu e da Terra, que ocultaste estas coisas aos sábios e entendidos, e as revelaste aos pequeninos.Sim, ó Pai, porque assim Te aprouve." Mateus 11:25-26"Vinde a Mim, todos os que estais cansados e oprimidos, e EU vos aliviarei.Tomai sobre vós o Meu jugo, e aprendei de Mim, que Sou manso e humilde de coração; e encontrareis descanso para as vossas almas.Porque o Meu jugo é suave e o Meu fardo é leve." Mateus 11:28-30

professorjrod@gmail.comA census solved with cardboard, a company remade by a $5 billion gamble, and a tiny firmware layer that cracked open the PC market—this is the human story behind how computing became a platform, not a product. We go from Hermann Hollerith's 1890 insight to IBM's sales-first system that taught the world to think in fields and records, and then to the cultural and ethical crosscurrents that come with scale. Those punched holes didn't just count people; they trained generations to quantify work, plan logistics, and make decisions with data.The narrative turns at a crossroads in the early 1960s. Thomas J. Watson Jr. sees a maze of incompatible machines and bets the company on a single, compatible architecture: System/360. It demanded new chips, code, factories, and nerve. Launch day lands with shock and relief—orders flood in for a family of computers that finally speak the same language. That choice redefined the industry's economics: software could live longer than hardware, upgrades didn't mean rewrites, and customers stopped fearing growth. Architecture became destiny, and IBM set the standard that everyone from Apple to ARM would later emulate in their own ecosystems.Then the stage shifts again to 1981, where a humble BIOS turns one machine into a platform. IBM documented how its firmware behaved; Compaq legally reimplemented it; the clone market ignited. Prices dropped, innovation surged, and the Wintel era took shape. IBM lost tight control but the world gained a common PC standard that carried software across brands and borders. From punch card schemas to UEFI, from batch jobs to cloud migrations, the same lesson repeats: design for compatibility, bet on continuity, and accept that openness can multiply impact.If the story made you think differently about the architecture beneath your apps and devices, follow the show, share it with a friend, and leave a review to help others find Technology Tap. What bold standard—or act of openness—should today's tech leaders champion next?Inspiring Tech Leaders - The Technology PodcastInterviews with Tech Leaders and insights on the latest emerging technology trends.Listen on: Apple Podcasts SpotifySupport the showArt By Sarah/DesmondMusic by Joakim KarudLittle chacha ProductionsJuan Rodriguez can be reached atTikTok @ProfessorJrodProfessorJRod@gmail.com@Prof_JRodInstagram ProfessorJRod

Get ready for a behind-the-scenes masterclass in Instagram Bio strategy with Evie + Lindsey! In this episode, the girls do something they've never done before, a live Instagram bio audit straight from listener submissions. They break down what makes a bio pop, how to optimize your name field for search, the power of clear calls-to-action, and how to ditch redundant info that's wasting space. Whether you're a photographer, coach, artist, or author, this episode will help you rewrite your bio to attract your dream clients and convert followers into loyal fans. Grab your notebook, because by the end, you'll have the confidence to craft a bio that actually works for you and your business. --------------------------------- Gear List Freebie: https://theheartuniversity.com/gear --------------------------------- Heart Shop: https://theheartuniversity.com/shop --------------------------------- Primally Pure: https://primallypure.com/?rfsn=5649435.725fd3 Use HEARTANDHUSTLE for 10% OFF. --------------------------------- Watch on YouTube: https://youtube.com/@theheartuniversitychannel?si=33lzxpBA9UxKlgTE --------------------------------- If you want to connect with us and other listeners in the Heart and Hustle community join our Facebook group here. --------------------------------- "PODCAST10" for 10% off anything from The Shop! www.theheartuniversity.com/shop --------------------------------- Follow along: www.instagram.com/mrslindseyroman www.instagram.com/evierupp www.instagram.com/theheartuniversity

New DShield Support Slack Workspace Due to an error on Salesforce s side, we had to create a new Slack Workspace for DShield support. https://isc.sans.edu/diary/New%20DShield%20Support%20Slack/32376 Attackers Exploiting Recently Patched Cisco SNMP Flaw (CVE-2025-20352) Trend Micro published details explaining how attackers took advantage of a recently patched Cisco SNMP Vulnerability https://www.trendmicro.com/en_us/research/25/j/operation-zero-disco-cisco-snmp-vulnerability-exploit.html https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-snmp-x4LPhte Framework BIOS Backdoor The mm command impleneted in Framework BIOS shells can be used to compromise a device pre-boot. https://eclypsium.com/blog/bombshell-the-signed-backdoor-hiding-in-plain-sight-on-framework-devices/ SANS.edu Research: Mark Stephens, Validating the Effectiveness of MITRE Engage and Active Defense https://www.sans.edu/cyber-research/validating-effectiveness-mitre-engage-active-defense/

 All of these men have earth tone button up shirts, khaki pants, weird off brand sneakers, and go hiking on the weekends. Meanwhile the women are business owners, nurses, have their own individual style and are homeowners. So we'll see how this goes! This episode is brought to you by Quince. To get the softest towels, the best sheets, and the chicest accessories, go to ⁠⁠⁠⁠⁠www.quince.com/2bg1r⁠⁠⁠⁠⁠ for free shipping and returns on us! From comfy recliners to cozy bedding and autumn decor. Find it all for way less at https://Wayfair.com. Listen to our PRE-SHOW and watch us on VIDEO only on Patreon. ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Join the Rose Garden today⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠! CONNECT WITH US: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Instagram⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Twitter⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠TikTok⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Merch⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ EMAIL: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠2blackgirls1rose@gmail.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Follow Natasha's Substack The Nite Owl: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠theniteowl.substack.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Learn more about your ad choices. Visit podcastchoices.com/adchoices

Another fabulous cast of women for an undeserving man. Age and beauty is seriously bout to be THE currency of this season with Mr. Mel Owens in charge... This episode is brought to you by Quince. To get the softest towels, the best sheets, and the chicest accessories, go to ⁠⁠⁠⁠www.quince.com/2bg1r⁠⁠⁠⁠ for free shipping and returns on us! Listen to our PRE-SHOW and watch us on VIDEO only on Patreon. ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Join the Rose Garden today⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠! CONNECT WITH US: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Instagram⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Twitter⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠TikTok⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Merch⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ EMAIL: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠2blackgirls1rose@gmail.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Follow Natasha's Substack The Nite Owl: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠theniteowl.substack.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Learn more about your ad choices. Visit podcastchoices.com/adchoices

Season 2 of “The Golden Bachelor” is kicking off next week, and ABC has dropped those cast bios! The fact that 66-year-old lead Mel Owens has said he doesn't want to date women over 60 (i.e. everyone in the show's typical age range) has cast a pall over the proceedings, but who could be mad about meeting these 23 vibrant, multifaceted, brilliant women? Not us! We dig into the bios and discover a cast full of midlife health and fashion influencers, cosmetic dentists, and government workers – whom ABC seems particularly eager to assure us are all addicted to Pilates, long-distance running, and dance. To learn more about listener data and our privacy practices visit: https://www.audacyinc.com/privacy-policy Learn more about your ad choices. Visit https://podcastchoices.com/adchoices