American software company owned by IBM providing open-source software products to enterprises
POPULARITY
Categories
437 episodes with Red Hat
59 episodes with Red Hat
67 episodes with Red Hat
42 episodes with Red Hat
49 episodes with Red Hat
68 episodes with Red Hat
47 episodes with Red Hat
22 episodes with Red Hat
35 episodes with Red Hat
33 episodes with Red Hat
30 episodes with Red Hat
117 episodes with Red Hat
29 episodes with Red Hat
58 episodes with Red Hat
30 episodes with Red Hat
46 episodes with Red Hat
42 episodes with Red Hat
72 episodes with Red Hat
20 episodes with Red Hat
33 episodes with Red Hat
20 episodes with Red Hat
16 episodes with Red Hat
49 episodes with Red Hat
16 episodes with Red Hat
14 episodes with Red Hat
16 episodes with Red Hat
12 episodes with Red Hat
35 episodes with Red Hat
29 episodes with Red Hat
13 episodes with Red Hat
16 episodes with Red Hat
12 episodes with Red Hat
33 episodes with Red Hat
18 episodes with Red Hat
14 episodes with Red Hat
19 episodes with Red Hat
14 episodes with Red Hat
10 episodes with Red Hat
11 episodes with Red Hat
16 episodes with Red Hat
12 episodes with Red Hat
10 episodes with Red Hat
9 episodes with Red Hat
26 episodes with Red Hat
9 episodes with Red Hat
8 episodes with Red Hat
20 episodes with Red Hat
8 episodes with Red Hat
8 episodes with Red Hat
9 episodes with Red Hat
8 episodes with Red Hat
11 episodes with Red Hat
17 episodes with Red Hat
8 episodes with Red Hat
8 episodes with Red Hat
12 episodes with Red Hat
9 episodes with Red Hat
9 episodes with Red Hat
8 episodes with Red Hat
11 episodes with Red Hat
9 episodes with Red Hat
26 episodes with Red Hat
10 episodes with Red Hat
8 episodes with Red Hat
9 episodes with Red Hat
5 episodes with Red Hat
7 episodes with Red Hat
9 episodes with Red Hat
12 episodes with Red Hat
13 episodes with Red Hat
4 episodes with Red Hat
5 episodes with Red Hat
7 episodes with Red Hat
6 episodes with Red Hat
7 episodes with Red Hat
4 episodes with Red Hat
4 episodes with Red Hat
10 episodes with Red Hat
5 episodes with Red Hat
7 episodes with Red Hat
6 episodes with Red Hat
10 episodes with Red Hat
3 episodes with Red Hat
7 episodes with Red Hat
11 episodes with Red Hat
4 episodes with Red Hat
11 episodes with Red Hat
5 episodes with Red Hat
7 episodes with Red Hat
4 episodes with Red Hat
8 episodes with Red Hat
3 episodes with Red Hat
8 episodes with Red Hat
5 episodes with Red Hat
4 episodes with Red Hat
3 episodes with Red Hat
8 episodes with Red Hat
4 episodes with Red Hat
5 episodes with Red Hat
3 episodes with Red Hat
7 episodes with Red Hat
3 episodes with Red Hat
2 episodes with Red Hat
8 episodes with Red Hat
3 episodes with Red Hat
4 episodes with Red Hat
13 episodes with Red Hat
7 episodes with Red Hat
4 episodes with Red Hat
4 episodes with Red Hat
2 episodes with Red Hat
6 episodes with Red Hat
5 episodes with Red Hat
5 episodes with Red Hat
3 episodes with Red Hat
9 episodes with Red Hat
3 episodes with Red Hat
4 episodes with Red Hat
10 episodes with Red Hat
2 episodes with Red Hat
4 episodes with Red Hat
4 episodes with Red Hat
4 episodes with Red Hat
8 episodes with Red Hat
2 episodes with Red Hat
3 episodes with Red Hat
3 episodes with Red Hat
3 episodes with Red Hat
2 episodes with Red Hat
3 episodes with Red Hat
4 episodes with Red Hat
3 episodes with Red Hat
5 episodes with Red Hat
3 episodes with Red Hat
8 episodes with Red Hat
4 episodes with Red Hat
4 episodes with Red Hat
4 episodes with Red Hat
2 episodes with Red Hat
3 episodes with Red Hat
3 episodes with Red Hat
10 episodes with Red Hat
3 episodes with Red Hat
3 episodes with Red Hat
5 episodes with Red Hat
5 episodes with Red Hat
5 episodes with Red Hat
5 episodes with Red Hat
5 episodes with Red Hat
5 episodes with Red Hat
3 episodes with Red Hat
10 episodes with Red Hat
2 episodes with Red Hat
2 episodes with Red Hat
2 episodes with Red Hat
3 episodes with Red Hat
3 episodes with Red Hat
3 episodes with Red Hat
3 episodes with Red Hat
2 episodes with Red Hat
10 episodes with Red Hat
44 episodes with Red Hat
For episode 687 of the BlockHash Podcast, host Brandon Zemp is joined by Yuannan Yang, Security Engineer at CertiK, the largest Web3 security services provider. CertiK offers a wide range of products and services to support the Web3 industry, project teams, and users alike. CertiK's products and services span the entire lifecycle of project development, from incubation and early stages, to growth and maturity. CertiK is one of the most globally recognized companies in the Web3 industry, serving users across 150 countries/regions.Yuannan Yang, based in Washington, DC, US, is currently a Security Engineer at CertiK. Yuannan Yang brings experience from previous roles at Johns Hopkins Whiting School of Engineering, Tsinghua University and Red Hat. Yuannan Yang holds a 2019 - 2020 Master's degree in information security @ Johns Hopkins Whiting School of Engineering.
In this episode of the Kubernetes Bytes podcast, Ryan and Bhavin talk to Janakiram MSV about all things KubeVirt. The discussion starts off by talking about the need for KubeVirt and then dives into the details of the KubeVirt architecture, and what you need to do when deploying virtual machines on Kubernetes, including commercial solutions like Red Hat OpenShift Virtualization and SUSE Virtualization. Check out our website at https://kubernetesbytes.com/ Show Notes: https://www.youtube.com/watch?v=DDwfPuWlsl0 https://janakiram.com/resources/ https://kubevirt.io/
The following article of the AI, Cloud & Data industry is: “The Future of Public Services: A Path Toward Smart Cities” by Javier Cordero, Vice President and General Manager, Red Hat.
IMAGE CREDIT: Pontificia Universidad Católica de Chile from Santiago, Chile, CC BY-SA 2.0 , via Wikimedia Commons LINKS: Fernando Natalio CHOMALÍ GARIB on Catholic-Hierarchy.org: https://www.catholic-hierarchy.org/bishop/bchga.html Fernando Natalio CHOMALÍ GARIB on Gcatholic.org: https://gcatholic.org/p/8844 2023 Vatican Biographical Summary of Fernando Natalio CHOMALÍ GARIB (Italian): https://press.vatican.va/content/salastampa/en/bollettino/pubblico/2023/10/25/321025d.html Chilean Bishops' Conference 2023 bio of Fernando Natalio CHOMALÍ GARIB (Spanish): https://iglesiadeconcepcion.cl/noticias/monsenor-fernando-chomali-ha-sido-nombrado-arzobispo-de-santiago/ 2016 Revised statutes of the Pontifical Academy for Life (Italian): https://press.vatican.va/content/salastampa/en/bollettino/pubblico/2016/11/05/161105b.html 2018 BBC coverage of the Father Karadima case through the eyes of one of his victims, James Hamilton: https://www.bbc.com/news/stories-45486176 2010 NY Times coverage of the Father Karadima case: https://www.nytimes.com/2010/10/28/world/americas/28chile.html 2010 The Media Project coverage of Father Karadima case: https://web.archive.org/web/20160303165612/http://themediaproject.org/article/chile-wrestles-religion-and-impunity 2014 NCR coverage of Father Karadima https://www.ncronline.org/news/accountability/chilean-cardinals-close-pope-stained-abuse-cover-ups 2018 24 Horas report on church membership and trust (Spanish): https://www.24horas.cl/papafranciscoenchile/cifra-de-chilenos-que-se-declaran-catolicos-bajo-desde-73-a-45-en-la-ultima-decada-2612241 2015 NCR coverage of the controversy over Bishop Barros' appointment: https://www.ncronline.org/news/parish/controversial-chilean-bishops-appointment-continues-divide-diocese 2015 Huffington Post coverage of Bishop Barros controversy: https://www.huffpost.com/entry/backlash-against-chilean_b_6955290/amp Voice of America coverage of Pope Francis' trip to Chile: https://www.voanews.com/a/pope-wraps-up-latin-america-trip/4217547.html Firebombings: https://www.kcrg.com/content/news/Update-3-churches-firebombed-in-Chile-during-pope-visit-469520773.html?outputType=amp 2018 BBC coverage of the mass resignation of the Chilean Bishops' Conference: https://www.bbc.com/news/world-latin-america-44442233 More via NCR: https://www.ncronline.org/news/francis-accepts-two-more-chilean-bishops-resignations-continuing-abuse-fallout More via NPR: https://www.npr.org/2018/06/11/618825779/pope-francis-accepts-resignations-of-3-bishops-over-chilean-abuse-scandal More via Religionnews.com: https://religionnews.com/2018/08/03/will-pope-francis-solve-the-abuse-crisis/ December 2024 The Pillar interview: https://www.pillarcatholic.com/p/speed-dating-the-new-cardinals-could Cardinal Garib Washing His Shirt: https://www.instagram.com/reels/DJR_m0xgCsT/ TRANSCRIPT: Hello everyone, welcome to Cardinal Numbers, a rexypod reviewing and ranking all the Cardinals of the Catholic Church from the Catacombs to Kingdom Come. One thing that I'll always remember about the end of my daily show experience is that one accompanying factor was the start of a war. It can be hard to keep at things when you're feeling down, and war had broken out in the Middle East the day I broke my streak of over 100 daily episodes. That's on my mind again because today's Cardinal is of Palestinian descent, and another war broke out today. So before we move on, I want to endorse both working for peace and praying for peace. Goodness knows we need to do all we can, and that we need all the help we can get. Also, before we get into things, please note that this episode was basically the one that sealed the deal on me going into my most recent hiatus. It took more research than expected because of the number of serious accusations adjacent to the story of our Cardinal of the day. Arguably I *could* have told most of future Cardinal Chomalí's story without getting into the Karadima case and subsequent Barros controversy, but that would have taken a lot of intentional sidelining of topics that unfortunately need to be front and center regardless of how controversial they are. Dozens of times we've seen the consequences of downplaying or sidelining such things, and I don't intend to contribute to that. If Cardinal Chomalí goes to the next round, I promise more of the focus will be on his own life and less on the dung he found himself shoveling. And now for the official warning: please note that this episode includes extensive discussion of scandal caused by the sexual abuse of minors and coverups. Listener discretion is advised. Today we're looking at our fifth bishop from the list of new Cardinals Pope Francis elevated on December 7th 2024–his last consistory for the creation of new Cardinals. Fernando Natalio CHOMALÍ GARIB, who describes himself as a descendent of a Palestinian, was born on March 10, 1957 in Santiago, Chile, the capital and largest city basically in the middle of the almost comically long country along South America's Pacific coast. Fernando is one of our late blooming vocations–his first degree was in Civil Engineering, though admittedly it was from the Pontifical Catholic University of Chile, which does host a seminary, though presumably our civil engineer didn't go through that side of things. Instead, when Fernando did decide to go to seminary and study theology and philosophy and such, it was through the Pontifical Major Seminary of Santiago, a storied institution in the suburbs. Enter the B plot for today, because in 1984, the same year Fernando entered seminary, a group of parishioners reported the “improper conduct” of another I cannot emphasize enough quite different Fernando, Father Fernando Karadima. The report was made to the Archbishop of Santiago, a man whose name I will not trouble you with because this is going to be an episode with a lot of names as-is and he'll get his own episode in time. Allegedly the letter containing the report was “torn up and thrown away”, in any event nothing came of it at the time. The Archbishop's secretary, Juan Barros, possibly already Father Barros by this stage, was a protege of Karadima and would later wind up accused of helping cover up Father Karadima's crimes, and this is not the last time we will see him, so keep that name in mind. To recap, we have Father Karadima, a powerfully connected child rapist, potential Father Barros, a fan of Father Karadima and an alleged enabler, and not-yet Father Chomalí, our Cardinal of the day, who isn't connected to our B-Plot yet, so let's move his side of things forward and see how this plays out. In 1991, after seven years of study on top of his engineering degree, Franando Chomalí was ordained a priest for the Archdiocese of Santiago de Chile. After two years of yet further study, he then obtained a licentiate in Moral Theology from the Gregorian in Rome, followed a year later by a doctorate in Sacred Theology from the same storied institution in 1994. I did see some reference to pastoral work, but considering we're like five degrees deep and he still isn't done studying–hello masters in bioethics from the John Paul II Institute in Rome–it's not going to surprise you that Father Chomalí mainly followed the academic route, serving in bioethical and theological posts at the Major Pontifical Seminary of Santiago and the Pontifical University of Chile–both of these, you might recall, being institutions that he had personally attended. In 2001, presumably in part due to his bioethics credentials, he was added to the Pontifical Academy for Life for life, which, yes, I'm repeating myself because not only is “for Life” part of the name, but apparently it was a lifetime appointment. Unfortunately in 2016 Pope Francis shook things up so there are no more appointments to the Pontifical Academy for Life for life. In 2003, our B plot shows back up, with a successor Cardinal Archbishop of Santiago getting more reports of Father Karadima's monstrosities. You'll be pleased to know that at this point the Chilean Bishop's Conference had new processes in place and you'll be furious to know that those new processes were basically ignored while the Cardinal told the complainant that he was praying for him. Nothing was done, hashtag thoughts and prayers. The next year the same cardinal received another report, and you'll be pleased to know that this time the case wound up referred to a specialist, who determined the allegations were credible and recommended action. You'll then be *again* furious to learn that the Cardinal proceeded to ignore the determination and dismissed the case anyways. You'll hear more about all this in *that* cardinal's episode, for now let's get back to Fr Chomalí, whose phone is ringing. His white phone. It's Pope Benedict, calling to make him Auxiliary Bishop of Santiago and Titular Bishop of Nola because you apparently just can't be an auxiliary bishop without a little patch of North Africa to theoretically but not practically call your own. Anyways, that all went down in 2006. In 2010, the Karadima case became international news for the first time when victims filed a criminal complaint in Chile's courts, twenty-five years after that first 1985 letter to Church authorities. The civil courts did not prove more helpful, dismissing the lawsuit due to the time having passed since the events in question, which really has me wanting to flip some tables. For what it's worth, the presiding judge made it clear that she thought Karadima was guilty as sin. The accusations now being public apparently stirred the Church into action. Suddenly the stonewalling Cardinal–reminder that's not Chomalí but another prelate we'll discuss in time–sent a reportedly 700 page file over to the Vatican, which in 2011 found Karadima guilty of abusing minors and sentenced him to a "life of prayer and penitence”. The by then 80 year old Karadima would continue protesting his innocence and by some accounts flaunt his ban from ministry, saying Mass for his followers, which, yes, he definitely *still* had followers. Also in 2011, our Cardinal of the Day Bishop Chomalí became Archbishop Chomalí when Pope Benedict made him Archbishop of Concepción, a bit south of Santiago, which was his first time really serving outside the capital apart from his studies in Rome. And with the Karadima case casting a shadow over the Church across the country, Archbishop Chomalí had his work cut out for him, with trust in the Church as an institution plummeting from 61% in 2010 to just 36% a year later according to polling data. Incredibly, Archbishop Chomalí managed to *increase* church membership in these conditions, probably aided by the broadly popular election of Pope Francis in 2013. Pope Francis wasn't magic though, and it's time to talk about one of his bigger mistakes. Remember Juan Barros, the Archbishop's secretary who was accused of helping protect his mentor Father Karadima? Well, he had been made a bishop back in the 90s, and in 2015 against the advice of basically everyone everywhere, Pope Francis decided to give Barros a new post as Bishop of Osorno. One of the voices against the appointment was Archbishop Chomalí, who was serving as Apostolic Administrator of Osorno at the time and so had front row seats to just how poorly it was coming across, and urged Pope Francis to reconsider. In addition, about half the clergy of the diocese publicly opposed the move–coming out in public against the guy who is set to be your boss is pretty gutsy–and even the politicians got involved, with 51 members of Chile's National Congress signing a letter opposing the move. Pope Francis carried on undaunted, and Bishop Barros was installed in a rather poorly attended ceremony, that is, poorly attended unless you count the hundreds of protestors who stormed the Cathedral. Bishop Barros came over to Osorno from the post he had held as the Military Ordinary for Chile. With that spot now vacant, you guessed it, Archbishop Chomalí was tapped to administer things for Chile's military, which, it's worth noting, grants him the rare privilege of being associated with Antarctica on GCatholic's database, thanks to the Chapel of St. Mary Queen of Peace in Chile's Antarctic zone. The controversy over Bishop Barros came to a head a few years later, when Pope Francis visited Chile. To be clear, the visit *didn't* calm things down–the word “firebombings” comes to mind–and Pope Francis didn't make a conciliatory gesture during the trip. Quite the opposite in fact. Pope Francis wound up defending his choice to appoint Bishop Barros and keep him in place, stating that the case against Barrros was baseless slander, committing that if he ever received evidence, he would respond. With the gauntlet thrown, the evidence apparently came, such that within months Pope Francis was apologizing for his stance, and the *entire* Bishops' Conference of Chile offered their resignations to the Pope, which might give a sense of the magnitude reached here. In the end, most of the bishops, including Archbishop Chomalí, were allowed to carry on, resignations not accepted, though Bishop Barros and three others were sacked as part of the reckoning. Later in the year, presumably as additional fallout from the visit and the subsequent fresh round of investigations, Karadima himself was laicized. *Mr.* Karadima would die in 2021. In October of 2023, Pope Francis appointed Archbishop Chomalí as the fourteenth Archbishop of Santiago de Chile. He became President of the Episcopal Conference of Chile at the same time, which I imagine was no coincidence, though there have been times recently when the two posts are held by different people. He had been the Conference's Vice President since 2021. Given his influential post in Chile's capital, Archbishop Chomalí's inclusion in Pope Francis's last batch of new Cardinals was hardly a surprise. Even though Pope Francis didn't heed his advice at the time, it's likely that Chomalí's advice against one of the biggest mistakes of Pope Francis' papacy was on both their minds as Francis made him a Cardinal. Shortly after Cardinal Chomalí was elevated, The Pillar, which is becoming something of a go-to source for church news, published a series of short interviews with several of the new Cardinals, including Chomalí. And so as we prepare to wrap things up for today, I'd like to offer you a short quotation from that piece so you can get a bit of flavoring from him rather than from the various dumpster fires he was tasked with putting out: “Christian anthropology says that if we want to be happy, we have to give ourselves to others. And secular anthropology tells us that we have to seek happiness by our own means. But things end up badly for us that way because we find ourselves in a society that competes but doesn't find itself. And that is precisely where conflicts arise.” Along with his brother cardinals, Fernando Natalio Cardinal CHOMALÍ GARIB participated in the recent election of Pope Leo. Just before the conclave, Cardinal Chomalí shared a video of himself hand-washing his shirt as part of his preparations, and of course you can catch that exciting link in the show notes. Cardinal Chomali will be eligible to participate in future conclaves until he turns 80 in 2037. Today's episode is part of Cardinal Numbers, and we'll be talking about another one of the new cardinals next month. Or well, later this month, since this episode is a bit late. Thank you for listening, God bless you all! Thanks, Joe!
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
Tim Beattie is the Co-Founder of Stellafai, a platform and coaching model that helps leaders and consultancies align around measurable outcomes and scale their impact without increasing headcount.After 25 years in professional services — including global leadership roles at Red Hat and IBM — Tim has pioneered an outcome-driven, asynchronous coaching approach that replaces the traditional billable-hour paradigm with a lean, repeatable operating system.Listen Now to discover, "How To Scale Your Impact Without Increasing Headcount."#smallbusinessowner #millionairemindset #motivationdaily #successmindset #wintheday
Enterprise AI experimentation is slowing, and a harder question is emerging: where is the business value? With only 10–15% of AI projects reaching sustained production, many organisations are facing a “production gap” between pilots and profitability. The Breakfast Show speaks with Guna Chellappan, General Manager Singapore at Red Hat, about why AI demos don’t automatically scale, the infrastructure and governance challenges holding companies back, and how to move AI from the playground to the profit centre.See omnystudio.com/listener for privacy information.
In this episode of THE MENTORS RADIO, Host Dan Hesse talks with Ginni Rometty, who was the ninth Chairman, President, and Chief Executive Officer of IBM. Under her leadership, the 100-year-old company reinvented 50 percent of its portfolio, built a $25 billion hybrid cloud business, and established leadership in AI and quantum computing. IBM acquired 65 companies during Ginni's tenure as CEO, including Red Hat, the largest acquisition in the company's history. She also drove record results in workforce transformation and supported the explosive growth of an innovative high school program to prepare the workforce of the future in over twenty-eight countries. Through her work with the Business Roundtable, Ginni helped redefine the purpose of the corporation. She has been named Fortune's #1 Most Powerful Woman three years in a row, is a member of the National Academy of Engineering, and has been honored with the designation of Officer in the French Légion of Honor. Today, Ginni Rometty serves on multiple boards and co-chairs OneTen, a coalition committed to upskilling, hiring and promoting one million Americans without four-year degrees by 2030 into family-sustaining jobs and careers. She is the author of the bestselling book Good Power: Creating Positive Change in Our Lives, Work and World, which is full of lessons she learned from important mentors, both inside and outside of IBM. LISTEN TO the radio broadcast live on iHeart Radio, or to “THE MENTORS RADIO” podcast any time, anywhere, on any podcast platform – subscribe here and don't miss an episode! SHOW NOTES: GINNI ROMETTY: BIO: BIO: Virginia (Ginni) Rometty BOOK: Good Power: Leading Positive Change in Our Lives, Work, and World, by Ginni Rometty WEBSITE: https://ginnirometty.com
The following article of the AI Cloud & Data industry is: “Measuring Impact of Change in Times of Technological Evolution” by Javier Cordero, Vice President and general manager Red Hat, Red Hat (AA2007)
In this episode of Stitch Please, host Lisa Wolfork tackles a critical conversation about anti-fascism, anti-racism, and anti-blackness within progressive craft communities. Prompted by her experience in an anti-fascist knitting subreddit, Lisa addresses the Norwegian Red Hat of Resistance (Melt the Ice pattern), the problematic response to a Black woman's critique, and why anti-fascism without anti-racism is like "a dog chasing its tail." This episode is essential listening for understanding why Black women's critique is not dismissal but observation based on extensive lived experience in predominantly white creative spaces, and why it is so important for us to have our own spaces.Hosted By: Dr. Lisa WoolforkSenior Producer: Krystal HillProducer: Mike Bryant========Dr. Lisa Woolfork is an associate professor of English specializing in African American literature and culture. Her teaching and research explore Black women writers, Black identity, trauma theory, and American slavery. She is the founder of Black Women Stitch, the sewing group where Black lives matter. She is also the host/producer of Stitch Please, a weekly audio podcast that centers on Black women, girls, and femmes in sewing. In the summer of 2017, she actively resisted the white supremacist marches in her community, Charlottesville, Virginia. The city became a symbol of lethal resurging white supremacist violence. She remains active in a variety of university and community initiatives, including the Community Engaged Scholars program. She believes in the power of creative liberation.Instagram: Lisa WoolforkTwitter: Lisa Woolfork========Stay Connected:YouTube: Black Women StitchInstagram: Black Women StitchFacebook: Stitch Please Podcast--Sign up for the Black Women Stitch quarterly newsletterCheck out our merch hereLeave a BACKSTITCH message and tell us about your favorite episode.Join the Black Women Stitch PatreonCheck out our Amazon Store
For the second day in a row the lads were delighted to welcome a special guest, this time Fran Heeran, head of telecoms at Red Hat. For once they waste little time before moving on to the main topic of Red Hat and getting to the bottom of what it does. Spoiler alert: it's open-source software for enterprise, which includes telecoms, so they explore topics such as virtualization, containers, and assorted other software arcana. They eventually move on to look ahead at some of the likely innovations and opportunities offered by 6G before concluding by exploring some of the practical telecom applications of AI.
Host Scott Hennen returns with a heavy, fast-moving Tuesday edition that shifts from a glowing review of the new Melania movie to the grim reality of local and national tragedies. The episode centers on two disturbing disappearances: the high-profile kidnapping of Savannah Guthrie's mother and a heartbreaking local murder investigation in Fargo that has authorities searching landfills and rural properties for human remains. Between the true crime updates, Scott sits down for a civil but intense discussion with local activists whose "Red Hat" protest—inspired by WWII Norwegian resistance—has sparked a firestorm of debate in the Red River Valley. Plus, we meet a YouTube-famous student farmer, look at the future of real estate education at UND, and learn why the El Paso airport just went into a 10-day lockdown. Episode Highlights [00:01:10] Melania: The Movie Review Scott shares his impressions of the private screening of Melania. Whether you're a fan or a critic, Scott argues the film offers a powerful glimpse into the First Lady's life and her successful career before meeting Donald Trump. [00:10:00] The Red Hat Resistance In a standout moment of civil discourse, Scott is joined by Cheryl Rosted and Ivan Thompson. They explain why they wear red hats to protest ICE and the Trump administration, while Scott challenges their comparisons to Nazi-occupied Norway. [00:26:45] The "Stolen Land" Debate The team reacts to student-led ICE protests at Davies High School. Scott sounds off on the "scary" reality of students getting news from social media and the controversial narrative regarding indigenous land. [00:32:15] The Search for Isadora Wengel A somber update on the disappearance of 25-year-old Isadora Wengel. Authorities have arrested her boyfriend for murder and are now asking the public to look for a specific 27-gallon black tote with a red lid. [00:44:10] The Franson Department of Real Estate Interim Dean Patrick O'Neill joins to discuss a historic naming at the University of North Dakota. Thanks to a legacy gift from Bob Franson, UND is launching a specialized program to train the next generation of property developers. [00:52:15] Money, Markets, and Metals Landmark Gold's David Fisher breaks down why gold is up 18% year-to-date and what China's "digital yuan" surge means for the future of the U.S. dollar.
Show DescriptionWhen Dave dies, who gets his domain name? How OpenClaw is a massive security concern, tips on handling a broad design surface area with a design system, changing database values with text-transform, should you declare CSS properties with @property, and was Chris wrong about CSS? Listen on WebsiteWatch on YouTubeLinks Your Home for a Century: Our 100-Year Domains and Plans 1Password Access after Death, Legacy Contacts | 1Password Community From magic to malware: How OpenClaw's agent skills become an attack surface | 1Password Openclaw (clawdbot), Agents and the Age of Personal Software - YouTube bbPress.org WooCommerce cap - no cap Nice Select · February 3, 2026 SponsorsAxe-ConAxe-con - the world's largest digital accessibility conference is from the makers of Axe-core and Axe DevTools Browser Extension. Taking place online on February 24-25. Registration is free and also gets you access to the on-demand recordings. Axe-con has a specific Development Track for dev content - some top speakers are Ire Aderinokun (front-end developer and Google developer expert), Jesse Beach (Software Engineering Manager at Meta), and other prominent folks from orgs like Coinbase, Zendesk, Red Hat, Atlassian, and more.
An airhacks.fm conversation with Kabir Khan (@kabirkhan) about: first computer was a ZX Spectrum 48K with rubber keys, playing Bomb Jack as a memorable early game, growing up in Norway near Oslo with lots of outdoor activities including skiing and swimming in warm fjords, discovering multimedia kiosks at Tower Records in Piccadilly Circus as career inspiration, writing a Java applet dissertation visualizing Motorola 68000 CPU instruction processing with animations, early programming in Basic on the ZX spectrum including a hardcoded cookbook application, learning Pascal and the revelation of understanding what files actually are, first job writing an HTTP server in C++ on Windows NT using Winsock, implementing Real-Time Protocol streaming for multimedia content, working at a consultancy learning multiple programming languages including Active Server Pages ASP and Microsoft Transaction Server MTS, going freelance and building a Java-based exhibition industry booking system, using JBoss with EJB3 for the second version of the exhibition system, getting JBoss support and being impressed by their expertise, contributing to JBoss Mail and JBoss AOP as open source contributions, meeting Sacha Labourey at a JBoss partner event in Norway who advised focusing on AOP, joining JBoss in September 2004 when the company had only about 50 people, meeting Marc Fleury and having pizza at his house in Atlanta, the Red Hat acquisition of JBoss in 2006, leading the JBoss AOP project and standardizing interceptor chains, working on the JBoss microcontainer for JBoss 5 which was over-engineered and slow, joining the team that rethought the server architecture leading to Wildfly, working on WildFly core server management and domain management, the recent move of the runtimes division from Red Hat to IBM, current work on Agent-to-Agent (A2A) protocol, quarkus being the Java reference implementation for the A2A specification published by Google, Agent-to-Agent Protocol as a standardized protocol for agent-to-agent communication using JSON-RPC REST and grpc, agent cards as capability advertisements similar to business cards, benefits of smaller specialized agents over monolithic AI applications including better traceability smaller context windows and flexibility with different LLMs, comparison of agent architecture to microservices where smaller agents are preferable unlike traditional services where monoliths can be better, upcoming episode planned to deep-dive into A2A with Quarkus and opentelemetry for agent traceability Kabir Khan on twitter: @kabirkhan
What do Nardwaur, Shopify, Red Hat, and Slack have in common? They're all featured in Earn It by Steve Pratt. Steve is the previous co-founder of Pacific Content, and he wrote this book as an homage to his career in podcasting and marketing. I read some excerpts from Chapter 3, Opposite Strategy, and the differences and overlaps between The Job (business) and the Gift (creative). Check out our last episode, featuring the book Energize: https://www.honeyandhustle.co/i-read-a-chapter-of-energize-by-simon-alexander-ong-for-you/Thanks for listening! Let's keep the convo going: Join the community, Please Hustle Responsibly: https://pleasehustleresponsibly.com/Find all episodes here: https://www.honeyandhustle.coYouTube: https://www.youtube.com/c/AngelaHollowellLinkedIn: https://www.linkedin.com/in/angelahollowell/Twitter: https://twitter.com/honeyandhustleMentioned in this episode:Subscribe to the newsletter today: www.pleasehustleresponsibly.comGet your free lesson from CommunityOS here: https://www.communityos.xyz
Friends, this week we're diving into something that's been eating at me for a while now—how the architects of Christian nationalism have had the audacity to claim Dietrich Bonhoeffer as one of their own. I'm talking about Project 2025 invoking "costly grace" as if Bonhoeffer wasn't writing about them. Here's the thing: when Bonhoeffer penned those famous words in 1937, he wasn't crafting a devotional for suburban book clubs—he was running an illegal seminary under Nazi surveillance, training pastors who were forfeiting their careers, their pensions, and their safety to follow Jesus instead of the Führer. The German Christians of his day fused faith with national identity, blessed political power, and demanded loyalty to a strongman who promised to make their country great again. Sound familiar? The brutal irony is that those who now quote Bonhoeffer are functionally aligned with the very forces he resisted—they're the German Christians quoting the Confessing Church, and that's about as theologically obtuse as Caesar celebrating the cross while forgetting he's the one who put Jesus on it. Costly grace is still available, y'all—it just actually has to cost something. Read the full essay and subscribe for more at my SubStack, Process This You can subscribe to the Audio Essay podcast feed here. Join us at Theology Beer Camp, October 8-10, in Kansas City! UPCOMING ONLINE LENT CLASS: Jesus in Galilee w/ John Dominic Crossan What can we actually know about Jesus of Nazareth? And, what difference does it make? This Lenten class begins where all of Dr. John Dominic Crossan's has work begins: with history. What was actually happening in Galilee in the 20s CE? What did Herod Antipas' transformation of the "Sea of Galilee" into the commercial "Sea of Tiberias" mean for peasant fishing communities? Why did Jesus emerge from John's baptism movement proclaiming God's Rule through parables—and what made that medium so perfectly suited to that message? Only by understanding what Jesus' parables meant then can we wrestle with what they might demand of us now. The class is donation-based, including 0, so join, get info, and join up here. This podcast is a Homebrewed Christianity production. Follow the Homebrewed Christianity, Theology Nerd Throwdown, & The Rise of Bonhoeffer podcasts for more theological goodness for your earbuds. Join over 75,000 other people by joining our Substack - Process This! Get instant access to over 50 classes at www.TheologyClass.com Follow the podcast, drop a review, send feedback/questions or become a member of the HBC Community. Learn more about your ad choices. Visit megaphone.fm/adchoices
The Rum Rollers have officially left the solid ground of the lower realms behind, mooring Adüné at the docking gantry of Airshiff 86, a city-ship that defies both gravity and traditional economics. In this episode, the crew navigates the high-pressure social atmosphere of the Star Talker Federation Union (STFU) and discovers that in the sky, your worth isn't measured by the gold in your purse, but by the weight of the gifts you give away.The Discovery of the Red HatsAs the crew moves from the industrial "Under-Hull" to the shimmering "Market Dome," they learn the truth about gnomish status. They encounter the two distinct classes of the Federation:The Crimson-Capped (The Gift-Givers): These "Red Hats" are the social elite, gnomes who have attained high status by gifting their inventions, labor, and even their food to the collective. To a Red Hat, a hoarding mind is a failing engine.The Bare-Brows: The unproven or the "indebted," those who have yet to contribute a significant "Great Work" to the city's harmony.The Theology of ProbabilityThe crew is granted an audience with High Brewmaster Fizz, who reveals the true purpose of Airshiff 86's mission toward the god-tree, Liber-Tree. In a stunning revelation of divine physics, the crew learns that the gnomes do not pray—they calculate.The Federation seeks the patronage of a god to obtain Star-Sap, the only fuel potent enough to keep their massive cities aloft. In exchange, the gnomes offer the only thing a god cannot manifest: Certainty. Airshiff 86 is a massive, flying Probability Machine. By living lives of perfect mechanical and social harmony, the gnomes process the infinite "chaos" of the universe into "ordered outcomes," acting as a biological CPU that helps their god-patron navigate the complexities of existence.The Celestial BrewTo toast this new alliance, the crew is introduced to the "Brew" itself—not just a drink, but a liquid miracle. From the Cloud-Puff Pastries that must be tethered to the table to the Ales of Accord that grant drinkers a glimpse of the world's ley lines, the Rum Rollers realize that on Airshiff 86, every meal is a ritual and every sip is a contract.Will the Rum Rollers find their place in this gift-based technocracy, or will their "heavy-world" habits drag the city into a catastrophic descent?
Show DescriptionWe're passing over another milestone episode and answering your Q's with our A's while we do it: Dave goes 3D printing, should CSS be inside a web component, Chris is trying to build web component for popovers, why isn't Vue used or talked about more, finding bugs in blocks in the new CodePen, and we're grateful for 700 episodes. Listen on WebsiteWatch on YouTubeLinks Vue.js - The Progressive JavaScript Framework | Vue.js vuejs/petite-vue Syntax: Hacking Pizza Ordering For Fun And Profit - YouTube Theo - Twitch SponsorsAxe-ConAxe-con - the world's largest digital accessibility conference is from the makers of Axe-core and Axe DevTools Browser Extension. Taking place online on February 24-25. Registration is free and also gets you access to the on-demand recordings. Axe-con has a specific Development Track for dev content - some top speakers are Ire Aderinokun (front-end developer and Google developer expert), Jesse Beach (Software Engineering Manager at Meta), and other prominent folks from orgs like Coinbase, Zendesk, Red Hat, Atlassian, and more.
This week John Terrill from Red Hat joins us to talk about branding in Open Source. Many projects don't have a unified communication strategy, but having one is important. -- During The Show -- 00:50 Intro Steve is in Vegas Noah "getting deals" 04:37 Lossless Cut Reached for Avidemux Avoiding re-encoding Learning a new program Lossless Cut Webpage Lossless Cut GitHub 08:30 OmniTools Small docker image Does everything in the web browser OmniTools GitHub 12:43 NLSH For people who want to learn the CLI Translates natural language into CLI Making things easy can backfire NLSH GitHub 16:00 Xyops Features: Job scheduling Workflow automation Server monitoring Alerting Incident response Self Hosted Open Source Xyops 18:18 News Wire Squid 7.4 - github.com Openttd 15.1 - openttd.org Rust 1.93 - rust-lang.org GNU C lwn.net Extix - linux.exton.net Liya Linux 2.5 - distrowatch.com CachyOS 2026 - cachyos.org GNU Guix 1.5 - quix.gnu.org MxLinux 25.1 - mxlinux.org Crypto Thieves in Snap Store - helpnetsecurity.com Open Source Quantum Computer - uwaterloo.ca AI Weather Models - kqed.org Banks Prefer Open-Source - finainews.com Rack-Scale AI - theasset.com OIN 2.0 - yahoo.com 19:55 Python Built-in Web Server Use python to host a web server Used for file transfers Use case Steve's travel router 24:17 Proxy RCE - PSA Basics of the problem grahamhelton.com 26:30 Matter Camera 1920x1080 30fps Synology App to turn a phone into a camera linuxgizmos.com 30:06 MS Gives Keys to FBI Microsoft confirms they gave the FBI BitLocker keys ~ 20 requests per year Home users forced to upload keys Jump through hoops to avoid uploading Encryption is only as good as who holds the keys Pragmatism aardwolfsecurity.com ArsTechnica 35:20 Linux Continuity Continuity document merged into Kernel docs theregister.com 36:40 John Terrill PR in open source Branding open source One size fits all projects Extracting technical knowledge Technical accuracy How to talk with journalists Separating personal views from project views Negative coverage Messaging guidelines Branding and marketing Attracting media attention -- The Extra Credit Section -- For links to the articles and material referenced in this week's episode check out this week's page from our podcast dashboard! This Episode's Podcast Dashboard Phone Systems for Ask Noah provided by Voxtelesys Join us in our dedicated chatroom #GeekLab:linuxdelta.com on Matrix -- Stay In Touch -- Find all the resources for this show on the Ask Noah Dashboard Ask Noah Dashboard Need more help than a radio show can offer? Altispeed provides commercial IT services and they're excited to offer you a great deal for listening to the Ask Noah Show. Call today and ask about the discount for listeners of the Ask Noah Show! Altispeed Technologies Contact Noah live [at] asknoahshow.com -- Twitter -- Noah - Kernellinux Ask Noah Show Altispeed Technologies
Virtualization is shifting, workloads are moving, and AI adoption is accelerating. Learn from Red Hat how organizations can adapt, integrate, and thrive amidst the changes.
In this episode of Sales Is King, host Dan Sixsmith kicks off the show's 10th year and the launch of a brand new studio with a powerhouse guest: Andrew Brown, Senior Vice President and Chief Revenue Officer at Red Hat. Andrew shares how Red Hat is driving double‑digit growth with its hybrid platforms, automation, and AI capabilities—while staying anchored in long‑standing values like freedom, courage, commitment, and accountability. He also breaks down how AI is really changing sales, what separates top sellers from the middle of the pack, and why “happy customers” is his simple, non‑negotiable definition of success.Red Hat's growth engines in 2025Three core platforms: Enterprise Linux, OpenShift (containerization/virtualization), and automation.Why true hybrid (on‑prem, private cloud, hyperscalers) is resonating with customers globally.The acquisition of Neural Magic and how Red Hat is playing in AI inference.Values that customers actually feelHow Red Hat's long‑standing values—freedom, courage, commitment, accountability—show up through products and people, not posters.Stories from customer visits (including India) where clients proactively praise the team, not just the tech.The call to become CRO and first 90 daysHow Andrew was tapped from IBM by Rob Thomas to run “anything that touches revenue” at Red Hat.Why he changed almost nothing at first: two ears, two eyes, one mouth—used in that ratio.Moving the organization from “growing” to truly unlocking the next growth curve, with alignment on one vision and one belief.What really separates top sellers from the middleActive listening as a true differentiator—probing pain, impact, and outcomes versus just hearing words.Never settling: aiming beyond the renewal, operating on the “front foot,” and treating success and failure the same way.A sports mindset: being ready for the clutch moments, orchestrating stakeholders, and failing at least 50% of the time but getting back up.How AI is reshaping sales at Red HatBuilding and buying: Red Hat's own AI assistant embedded in sellers' workflow (Slack → CRM opportunity creation) plus tools like People.ai to free managers from data validation and focus them on coaching.The big challenge: not building AI models, but getting them into production at scale with governance, cost control, and the right deployment (cloud vs. on‑prem).Why only a small percentage of AI projects show real value today—and what needs to change.Channel and ecosystem as revenue multipliersWhy a significant share of Red Hat's revenue runs through partners and how they're enabled pre‑ and post‑sales.Technical certifications, revamped partner programs, and advisory boards to keep value and alignment high.Customer success and value realizationConsolidating scattered customer success pockets into a central, technical CS team that engages the day after the contract is signed.Focus on hands‑on deployment, embedding Red Hat tech in customer architectures, and rescuing under‑utilized hybrid commitments.The direct link Andrew sees between CS, value realization, and recurring revenue uplift.Andrew's personal journey and leadership lessonsFrom aspiring soccer player to IBM intern to CRO at Red Hat.Doing an MBA nights/weekends to bridge technology and business outcomes in C‑level conversations.Early “bad” first management role and learning from white‑space, door‑to‑door style selling.Influences from Lou Gerstner and other mentors: keep it simple, communicate clearly, don't define your life only by work.Andrew Brown is Senior Vice President and Chief Revenue Officer at Red Hat, where he leads all revenue‑touching functions globally across sales, services, and ecosystem partners. Prior to Red Hat, Andrew spent nearly three decades at IBM in a variety of technical, sales, and leadership roles, combining a deep technology background with a strong commercial track record.
Protecting your ideas can be the difference between building momentum and watching someone else run with your work. In this episode of Unstoppable Mindset, I sit down with patent attorney and entrepreneur Devin Miller to explore what founders and business owners really need to know about patents, trademarks, and intellectual property. Devin shares how his background in engineering, startups, and law shaped his approach to innovation, and he breaks down the real differences between provisional and non-provisional patents in clear, practical terms. We talk about common mistakes entrepreneurs make, how legal protection supports growth instead of slowing it down, and why understanding intellectual property early can help you compete with confidence. I believe this conversation will give you clarity, direction, and a stronger foundation for protecting what you work so hard to create. Highlights: 00:01:18 – Hear how growing up in a small town shaped Devin's approach to problem-solving and business.00:12:53 – Learn why Devin combined engineering, business, and law instead of choosing a single career path.00:19:32 – Discover how a student competition turned into a real wearable technology startup.00:30:57 – Understand the clear difference between patents, trademarks, and copyrights.00:33:05 – Learn when a provisional patent makes sense and when it does not.00:53:52 – Discover what practical options exist when competitors copy or knock off your product. About the Guest: Devin Miller is the founder of Miller IP, a firm launched in 2018 that helps startups and small businesses protect their inventions and brands without breaking the bank. He's overseen over a thousand patent and trademark filings with a 95 percent success rate on patents and an 85 percent success rate on trademarks, making sure garage inventors and side hustlers get the same high-quality service as big tech. Before starting his firm, Devin spent years at large law firms working with clients like Intel and Amazon, but he found his true passion in helping scrappy entrepreneurs turn ideas into assets. He blends legal know how with an entrepreneur's mindset, offering flat fee packages, DIY legal tools, and hosting webinars and a podcast series to demystify IP. A lifelong runner who knocks out 10+ miles a day and 30-40 miles daily biking (except Sunday), Devin listens to audiobooks and podcasts while training for marathons. When he's not drafting office action responses or co-hosting Inventive Journey, you might catch him brainstorming the next Inventive Youth program or sipping coffee while sketching partnership agreements. Ways to connect with Devin**:** If you'd like to talk strategy or swap running playlist recs, feel free to schedule a chat at http://strategymeeting.com LinkedIn profile https://www.linkedin.com/in/lawwithmiller/ Firm website [https://www.lawwithmiller.com](https://www.lawwithmiller.com "https://www.lawwithmiller.com") About the Host: Michael Hingson is a New York Times best-selling author, international lecturer, and Chief Vision Officer for accessiBe. Michael, blind since birth, survived the 9/11 attacks with the help of his guide dog Roselle. This story is the subject of his best-selling book, Thunder Dog. Michael gives over 100 presentations around the world each year speaking to influential groups such as Exxon Mobile, AT&T, Federal Express, Scripps College, Rutgers University, Children's Hospital, and the American Red Cross just to name a few. He is Ambassador for the National Braille Literacy Campaign for the National Federation of the Blind and also serves as Ambassador for the American Humane Association's 2012 Hero Dog Awards. https://michaelhingson.com https://www.facebook.com/michael.hingson.author.speaker/ https://twitter.com/mhingson https://www.youtube.com/user/mhingson https://www.linkedin.com/in/michaelhingson/ accessiBe Links https://accessibe.com/ https://www.youtube.com/c/accessiBe https://www.linkedin.com/company/accessibe/mycompany/ https://www.facebook.com/accessibe/ Thanks for listening! Thanks so much for listening to our podcast! If you enjoyed this episode and think that others could benefit from listening, please share it using the social media buttons on this page. Do you have some feedback or questions about this episode? Leave a comment in the section below! Subscribe to the podcast If you would like to get automatic updates of new podcast episodes, you can subscribe to the podcast on Apple Podcasts or Stitcher. You can subscribe in your favorite podcast app. You can also support our podcast through our tip jar https://tips.pinecast.com/jar/unstoppable-mindset . Leave us an Apple Podcasts review Ratings and reviews from our listeners are extremely valuable to us and greatly appreciated. They help our podcast rank higher on Apple Podcasts, which exposes our show to more awesome listeners like you. If you have a minute, please leave an honest review on Apple Podcasts. Transcription Notes: Michael Hingson 00:00 Access Cast and accessiBe Initiative presents Unstoppable Mindset. The podcast where inclusion, diversity and the unexpected meet. Hi, I'm Michael Hingson, Chief Vision Officer for accessiBe and the author of the number one New York Times bestselling book, Thunder dog, the story of a blind man, his guide dog and the triumph of trust. Thanks for joining me on my podcast as we explore our own blinding fears of inclusion unacceptance and our resistance to change. We will discover the idea that no matter the situation, or the people we encounter, our own fears, and prejudices often are our strongest barriers to moving forward. The unstoppable mindset podcast is sponsored by accessiBe, that's a c c e s s i capital B e. Visit www.accessibe.com to learn how you can make your website accessible for persons with disabilities. And to help make the internet fully inclusive by the year 2025. Glad you dropped by we're happy to meet you and to have you here with us. Well, hello to all of you, wherever you happen to be today, you are listening to or watching or both unstoppable mindset and I am your host. Mike hingson, our guest today is Devin Miller, who founded the company, Miller IP, and he'll tell us all about that and what that means and so on as we go through this. But I will tell you that he is a lawyer. He deals with patents and other things and a lot of stuff relating to startups. I think that's going to be a lot of fun to talk about. So without any further ado, as it were, Devin, welcome to unstoppable mindset. We're really glad you're here. Thanks for having me on. Excited to be here. Well, we're glad. We're glad you're here. Can you hear me? Okay, now I hear you. Devin Miller 02:06 Well, we're sorry for the delay, but I said I'm excited to be here and looking forward to chatting. Michael Hingson 02:11 Well, perfect. Well, let's start. I love to always do this. Let's start kind of at the beginning. Why don't you tell us about the early Devon, growing up and all that? Devin Miller 02:21 You know, I I'm happy to do. I don't know there's anything that probably stands out. I was probably fairly typical. So I was raised in a religious family, so we're attended church regularly every week. And I had a couple sisters, an older and a younger one, and was went through, went through schooling and or studied, probably the typical course. So I don't know there's anything stands out. I was in a small town, so grew up as, probably not as small as I'd like it to be anymore, but a small farming town, and it was, it was kind of always enjoyed the small town fill, and actually am back to being in that same hometown where I live now with my family. But yeah, so I did that, and I did probably the at the time, the typical thing with the it's growing up with kids and sports and doing things, and went through high school and and after that, jumped or went off to college. But I don't know if there's anything in particular that stands out in my mind, other than probably, at least in my mind, a pretty typical childhood and upbringing, but enjoyed it nonetheless. But happy to provide any details or I can jump into a bit about college. Michael Hingson 03:38 Well, where did you go to college? Devin Miller 03:40 Yeah, so I went to Brigham, young university, just or BYU, just out here in Utah. So I went off to so, or I graduated high school and I went off to a year of college. So I went off to BYU, kind of intending to go into electrical engineering, which is what I or one of the degrees I ended up studying with, and then I did that for a year, and after which I went off and did a served a religious mission for my church, so Church of Jesus Christ, or Latter Day Saints, otherwise nicknamed Mormon. So I went off and went to Taiwan for about two years. So didn't have any idea, even at that point where Taiwan was and certainly didn't know the language, but when studied that, or they have a training center where you get an opportunity to study it for about three months. So I studied it and then went off to Taiwan and served that religious mission for my church for a couple years before coming back to the high school, or good, not the high school to college to continue my studies. Michael Hingson 04:43 I several, several comments. One, I know what you mean about small hometowns. We moved from Chicago, where I was born, to California when I was five, we moved to a town called Palmdale, and it was a very small rural town about 60. Five miles north of Los Angeles. I don't know what the population was when we first moved there, but it couldn't have been more than 1000 or 1500 people spread out over a little bit of a distance. For me, it was great, because without there being a lot of traffic, I was able to do things I might not have done nearly as well in Chicago things like riding a bike, learning to ride a bike and walking to school and and not ever fearing about walking to school for any reasons, including being blind. But oftentimes I once I learned how to do it, I rode my own bike to school and locked it in the bike rack and then rode home and all that. But then Palmdale started to grow and I'm not quite sure what the population is today, but I live in a town about 55 miles east of Palmdale called Victorville, and as I described Victorville growing up, it was not even a speck on a radar scope compared to the small town of Palmdale, but we we moved down to Southern California from the Bay Area my wife and I to be closer to family and so on. In 2014 we wanted to build a house for Karen, because she was in a wheelchair her whole life. So we wanted to get a a house that would be accessible. And my gosh, the only place we could find any property was Victorville. And at that time, in 2014 it had 115,000 people in it. It has grown. Now it Devin Miller 06:31 has grown. And it tends to be that, you know, it feels like everybody's always kind of chasing the small town then, or people find out about it. Everybody moves in. It's no longer a small town, and then you're off to chasing the the next small town, wherever that might be. So it's kind of a perpetual cycle of of chasing that small or at least for the people to like it. Not everybody loves it, but I'm certainly a proponent of chasing that small town feel from from place to places, as you're trying to or trying to find or recreate what you probably grew up with. So it is a it is a cycle that everybody I think is chasing, Michael Hingson 07:09 yeah, well, for me now, my wife passed away in 2022 we were married 40 years. And so the thing about it is that there are probably advantages for me living alone, being in a place that has a few more people and a few more of the kind of amenities that at least somewhat larger towns have, like a Costco and some some restaurants. We actually live in a homeowner's development, a homeowner's association called Spring Valley Lake, and I live within walking distance of the Country Club, which has a nice restaurant, so I'm able to go to the to the restaurant whenever I choose, and that's kind of nice. So there's value for me and being here and people say, Well, do you ever want to move from Victorville now that your wife died? And why do I want to do that? Especially since I have a 3.95% mortgage? You know, I'm not going to do that, and I'm in a new house that. Well, relatively new. It was built in 2016 so it's pretty much built to code. And insulation is great. Solar is great on the house. Air conditioning works, so I can't complain. Devin Miller 08:20 No, sounds like a good setup, and it's kind of one where, why, if you enjoy where you're at, why would you move to go somewhere else that you wouldn't necessarily enjoy? So it just sounds like it works out. Michael Hingson 08:29 Well, it does, and I can always, as I need to being a keynote speaker and traveling, there's a shuttle that'll take me down to the nearest airports. So that works out. Well, that's awesome. So you went to, I'm a little bit familiar with the the whole LDS missionary program, Mission program, we we were not part of the church, but we lived, when my wife and I got married, we lived in Mission Viejo and we had neighbors right next door to us, who were members of the church, and they came over one day and they said, we have an issue. And I said, Okay. And my wife said, Okay, what's the issue? Well, we have a couple of missionaries coming in, and the only homes that are available to these two boys are homes that already have young female girls in them. So they really can't be in those homes. Would you be willing to rent your one of your rooms to missionaries? And so we said, and well, Karen said, because she was a member of the Methodist church, we said, as long as they don't try to mormonize us, we won't try to methodize them. And we would love to do it. And it worked out really well. We had a couple of missionaries for a while, and then they switched out. And eventually we had a gentleman from Tonga for a while, and we actually had a couple girls for for a while. So it worked out really well, and we we got to know them all, and it was a great relationship. And they did their work, and at Christmas time, they certainly were invited to our Christmas parties. We. Had every year a party. What we actually had was what we call a Christmas tree upping. We got the tree, we brought it into the house, and we invited all of our friends and neighbors to come and decorate the tree in the house. Because, needless to say, we weren't going to do that very well. Karen especially wasn't going to be able to stand up and decorate the tree. So we got them to do all the tree decorations and all that, and we fed them. So it worked out. Devin Miller 10:26 Well, it's awesome. Sounds like, great. And you hit on. I said, that's probably my, my favorite part of the Christmas is a Christmas tree. So growing up, we always had a real live tree, but it was always, you know, it was downstairs in the basement, and had lower ceilings. And so I was always kind of the opinion, hey, when I grow up, I want to have the a huge, you know, kind of like in the newbies at 20 plus or 20 or 20 plus foot tree, yeah. And lo and behold, we, or at least the couple houses that we build have always had, at least in the living space, have had the pretty high ceilings. And so that's always what we do. We'll go out and we'll cut down a live tree. So we'll go out to kind of in nature, to the forest, where they let you cut them down, and we'll, we'll cut down, usually it's around a 20 plus foot tree, and then have it strung up in the house. And I always tell my wife, I said, I'd rather that one could be my Christmas present. I'd be just as happy, because as long as I have my tree, it's a good Christmas for me. Michael Hingson 11:23 Yeah, oh, I hear you. Well, one of the boys who lived next door to us went off on a mission to, I think it was Argentina, and was gone for, I guess, two years. What was really funny is when he came back, it took him a while to re acclimatize his speaking English and getting back his American accent. He was he definitely had much more of a Spanish accent, and was much more used to speaking Spanish for a while. So the the three month exposure period certainly got him started at the at the center there in Utah. And then he went off and did his missionary work and then came home. But, you know, it's, it's got to be a wonderful and a very valuable experience. How do you think it affected you? Devin Miller 12:10 Yeah, I think I said, I think it would be, you said it probably well, is it like one where to say, Hey, this is the most fun time in your life, and you'll never have a more fun time. I don't know that. It's kind of like, you know, I liken it to I so I like to do a lot of running, so or in older years. I don't know that I was as much in younger years, but kind of discovered not that I love running, per se, but love to get out and decompress and otherwise, kind of have a time where I don't have a lot of intrusions or other things that are pressing in on life. And so with that, you know, I've done a number of marathons and marathons, you know, everybody again, says, Well, did you have fun? Or was it a good or was it good marathon? So I don't know that it's ever fun. I don't and do it, but it's a good accomplishment. You it's, you go out, you set your mind to something, and then otherwise, at the end of the day, you reach your goal. And, you know, kind of has the that sense of accomplishment and learning and become improving yourself. That's probably a lot of how I like in a mission is, you know, you have a lot of stresses of learning a new language, being in a different culture, doing something that you're unfamiliar with or not accustomed to, and at the end, you know, you learn a lot of things, you are gain a lot of skills. You hopefully impact a lot of people's lives for the better. And so it is definitely one of those where it's a great accomplishment, but it's not, you know, it's not one way to say, hey, this was a fun vacation where I got to go play for two years. So it it works out well, and I would absolutely do it again. Michael Hingson 13:31 Yeah, I'm sure you learned a lot, and you probably learned a whole lot more in a lot of ways, than most of the people that you you visited with because you treated it as an adventure and an adventure to learn. So that's pretty cool, absolutely. So you came back from that and you went back to college, and did you continue in electrical engineering? Or what Devin Miller 13:56 did you do? Yes and no. So I did continue in electrical engineering. Or so I came back and, you know, the intent was, and what I continue to do is to study electrical engineering. I did add on a second degree, which I was a Mandarin Chinese and so I can't remember, I mentioned I I served in Taiwan for those couple years and had an opportunity to kind of, you know, learn and study the language. So as I was doing that, I kind of came back and said, Well, if I've already put in the effort to learn the language and to study it, I might as well, you know, utilize it, or add it to the degree. And so I I really started, or I added that as a second degree to the first degree. So I came out with both the degree in Chinese or man or Chinese, as well as electrical engineering. So yes, continue to study that. And then from that, you know, kind of just as a part of that story. So I was coming out, kind of getting, you know, the senior year, kind of getting towards the end of that degree, and looked at and said, you know, what do I want to do when I grow up? And I still know if I know the full answer, but I did look at it and say, Hey, I, you know, I don't know exactly what I want to do when I grow up, but I don't, I like engineering. Engineering, but I don't want to be an engineer in the sense that, you know, not that I didn't like engineering, but it was one where a typical electrical engineers, you come out of graduate school, you go work for a big company. You're a very small cog and a very big Will you work for. You know, 1015, years, you gain enough experience to have any say your direction and what projects you work on or really have any impact. Not saying that's not really what I want to do when I grow up, or when I start into the working world. And so kind of with that, I, you know, I had a couple interests I enjoyed, you know, kind of the startup, small business, kind of that type of world. And I also found it interesting to on the legal aspect of intellectual property, so patents, trademarks, and really more. At the idea of, hey, you're going to work with a lot of cooling or cool inventions, cool people are working on a lot of unique things, and you get a lot more variety. And you get, you know, kind of be more impactful. And so that was kind of the the Crossroads I found myself at saying which, you know, kind of which direction I want to go. And, you know, kind of, rather than take one or the other, I kind of, I split the road and decided I was going to do both. So I went off to graduate school and did both an MBA or a master's in business administration as well as a law degree, kind of focused more on intellectual property. So went off and studied both of those kind of with the intent of, you know, I don't want to just be fit into one box or do just one thing, but I'd like to keep a foot in the business world, startup world, and have an opportunity to pursue my own business as well as doing the law degree. So I did that in a Case Western Reserve out in Cleveland, Ohio, studying both of those degrees Michael Hingson 16:34 when you were getting your degree in manner, in Chinese. Was that all about speaking the language, or was it also involved in history and civilization and understanding more about China? What was it like? Devin Miller 16:47 It was really more, certainly, there was a or, I guess, are you saying within college or within the mission itself? 16:54 In college? Okay, yeah. I mean, it was, Devin Miller 16:57 it was still primarily focused on the language. You know, the nice thing is, you can test out of a number of the, you know, entry level or their beginning classes, as long as you can show a proficiency. So there may have been some of that, and you still got, you know, some of the classes, would you still study a little bit of poetry, or, you know, within the language context, they've used poetry as a way to kind of learn different aspects of the language. You'd get a little bit of history, but pretty, or vast majority of focus was kind of both speaking as well as the the written and, you know, those are really as opposed to, like English speaking, where it's phonetics and you can or sound out and kind of understand what a you know, what something means by sounding it out, you don't have to know the word in order To, you know, to pronounce it. Chinese is not that way. So you have characters that are just every character you have to memorize. There is no phonetics. There's no way that you can look at a character and sound it out. And so there's a large amount of just memorizing, memorizing, you know, 20,000 characters to read a newspaper type of a thing. And then on the flip side is you have to learn the language, which is, you know, which are already focused on that, more on the mission, but you have to do pronunciation, so you can say the same word with different tones and it has entirely different meaning. So really, there was enough there on the language side, they tended to primarily focus on that, just because there was quite a bit there to Michael Hingson 18:19 dive into. It's a complicated language. Devin Miller 18:23 It it is certainly or uniquely different from English. I would say probably English to Chinese speakers is the hardest language because it's the most different from their language. And vice versa for English speaking Chinese is at least one of the this or harder languages because it is entirely different. So it is one that has a lot of intricacies that you get to learn. Michael Hingson 18:45 I took German in high school for three years, and then in college, I did a lot of shortwave listening and encountered radio Japan a bunch. So I actually took a year of Japanese, and I think from a written language, it's a lot more complicated than spoken language. I think it's a lot more straightforward than Chinese and a lot of ways easier to learn. But even so, it is different than than Latin languages by any standard. Devin Miller 19:16 But it is. It's an animal in and of itself, but it makes it fun. Michael Hingson 19:21 Yeah, that's right, it does make it fun. Incident. And then, as I said, it was an adventure. And all of that was, was an adventure. My master's is in physics. That was an adventure. And until you spend a lot of time dealing with physics and hopefully getting beyond just doing the math, you learn how much of a philosophical bent and how much about society and the way things work really is wrapped up in physics. So again, it's it's kind of fun, and unlike a lot of physicists or engineers. I've never thought that one is better or worse than the other. I think they both have purposes. And so as a physics person, I never pick on engineers. Devin Miller 20:11 I am, I wouldn't pick up. I wouldn't pick on any physics or physicists or physics majors, either, because that's equally, if not more difficult. And so there's a lot of learning that goes on and involved with all of them. But they're all of them are fun areas to Michael Hingson 20:26 study with. They are. So once you you got your master's degrees, and you you got your law degree, what did you go off and do? Devin Miller 20:36 Yeah, so I mean, I would probably back it up just a little bit. So kind of during that period where I was getting the degrees, couple things happened. Had a couple kids. So started out first kid while I was doing the, I guess the second year where I was in under or doing the law and MBA degree, doing it as a joint degree. And so had the had a kid. And then during that same period, the next year, about a year about a year and a half later, had another kid. And so that puts me as a it's a four year program, if you combine both of them together. And so I was in the kind of the third year, the four year program. And while I was doing those studies, you know, I had a I was doing a couple things. One is, I was doing the both, or studying both majors, raising the family. I was working about 20 hours as a law clerk or for a law firm, and then during that, I can't remember or if it was a flyer, or if it was, you know, an email or whatnot, but came across a business competition, or it's kind of a, it was kind of a, a multi disciplinary competition wherever, you know, people of different degrees and different fields of study would get together, you form a group of four or five, and you work on developing an idea, and then you would enter it into the competition and see how it goes. And so we did that the first year, and we did something, an idea to make Gym Bags less smelly, and then enter that in and took second place. And during that period, next year comes along, we're all in our final year of our degree. And as we're doing that, we are studying the degree and or entering the competition again. And we decided to do something different. It was for wearables. You know, this is before Apple Watch, or, you know, the Fitbit, or anything else. It was well before I knew that, but we just said, Hey, when I was there, thinking, hey, wouldn't it be cool I'd ran my or, I think, my second marathon that time. Wouldn't it be awesome if you could monitor your hydration level so that you can make sure you're staying well hydrated throughout and it helps with the air, not being a sore and being, you know, quicker recovery and performing better. And so out of that, took the genesis of that idea, entered it back into the business comp, or that is a new idea, into the business competition, and did that with the partners, and took second place again, still a little bitter, or bitter that about that, because the people that took first place has entered the same thing that they entered the previous year, but polished, or took the money they've earned previously and polished it made it look a little nicer, and won again because it looked the most polished. But that aside, was a great, or great competition. Enjoyed it. And from that, you know, said, Hey, I think this is a good idea. I think it can be a, you know, something that you could actually build a business around. And so said, Hey, or kind of told the the people that were in the the group with me, you know, we're all graduating. We're going different directions. Would be pretty hard to do a startup altogether. So why don't we do this? Or why don't you guys take all the money that I got, you know that we you're in some reward money, or, you know, prize money. If you take my portion, split it amongst yourselves, and I'll just take ownership of the idea, whatever it is, where, you know, wherever I take it, and simply own it outright, you know, basically buying them out. And so that's what I did. So coming out of, you know, getting the MBA in the law degree, that was kind of always the intent. So, or coming out of school, I went and joined a law firm here in Utah. Was a full time patent attorney, and then alongside, you know, had the side hustle, what I'd really say is kind of a second full time job to where I was, you know, pursuing that startup or small business alongside of doing the law firm. So that was kind of the the genesis for, as I graduated full time attorney working, you know, with a lot of our cool clients and other things, and then also incorporating the desire to do a startup or small business. And that's kind of been, really, the trajectory that I've taken throughout my career is really, you know, finding ways to combine or to pursue both interests together. Michael Hingson 24:26 What happened to the business? Devin Miller 24:28 Yeah, so it so it's still alive today. I've been, I exited. Now it's been a couple year and a half, two years somewhere in there. Have to think back. So it started out. So with the business I started out, it was actually one where, rewinding just a little bit when we when I got started, my dad was also an electrical engineer. He'd actually, you know, he's well or farther into his career, and he done a number of different things across their medical devices through his career. And so he kind of, or he joined on as kind of doing it with us. Hustle with me, and we took that, started to build it. We brought on some additional team members. We brought on an investor, and actually built out and grew the business. It also evolved. So we were starting to test or test out the technology have it with some colleges and some other, you know, athletes, which was a natural place to start it at and about that time, and we were getting kind of to that next hurdle where we either needed to get a further investment or cash infusion, you know, to kind of take it to a more of a marketable, you know, a except a Polish full or ready to go to market type of product. And at that time, as we're exploring that we had or came or got connected with somebody that was more in the diabetes monitoring, they were doing it more from a service base. But you know, the overlay as to kind of how the technologies are overlapped with what they're doing tended to work out pretty well. And so we ended up combining the business to be one, where it was redirected a lot of the technology we developed underlining to be more of a wearables for the diabetes monitor. So that was a number of years ago. I stayed on doing a lot of, some of the engineering and development, primarily more in the intellectual property realm, of doing a lot of patents and whatnot. And then about a year and a half, two years ago, got bought out, was exited from that company and and that continues on today. It's still alive and growing, and I kind of watch it from, you know, from a distance, so to speak, or kind of continue to maintain interest, but don't are not necessarily active within the business anymore. So that was kind of a long answer to a shorter question, but that's kind of where the business eventually evolved to. Michael Hingson 26:36 So now I'm sure that the company is doing things like developing or working with products like continuous glucose monitors and so on. Devin Miller 26:46 Yep, yeah, that's kind of the direction as to what they're headed you Michael Hingson 26:49 well, and what's what's been interesting about several of the CGM type devices is that for people who are blind, there's been a real push to try to get some of them to be accessible. And what finally occurred about a year ago, maybe two years ago, is that one of the devices that's out there was approved to actually incorporate an app on a smartphone, and when the app came out, then it was really easy, although it took an effort to convince people to pay attention to it and do it, but it became technically a lot easier to deal with access, because all you had to do was to make the app accessible. And so there now is a continuous glucose monitor that that is accessible, whereas you wherein you get all the information from the app through voiceover, for example, on the iPhone or through talkback on a android phone that you get when you're just looking at the screen, which is the way it really should be anyway, because If you're going to do it, you should be inclusive and make it work for everyone. Devin Miller 28:06 No, that's cool. Yeah, there's a number of I think, between, you know, being a prevalent, you know, issue that people are dealing with, to, you know, different trying to address things earlier on, and also to motivate people do healthier lifestyle. And kind of the direction I think, is headed where a lot of the the company that's continues on today, from our original technology, is on the non invasive side. So a lot of them have, you have to have a patch, or you have to have periodically prick, or put an arm, you know, arm, right? Something where has a needle in the arm. And this one is kind of trying hair working to take it to that next level, to where it's no longer having to be invasive, and it's really all without having air with sensors that don't require you to have any sort of pain or prick in order to be able to utilize it. So kind of fun to fun to see how the industry continues to evolve. Michael Hingson 28:55 Well, today, we're working on that, and tomorrow, of course, the tricorder. So you know, we'll, we'll get to Star Trek 29:03 absolutely one step at a time. Michael Hingson 29:05 Yeah, but I've kind of figured that people were certainly working on non invasive technology so that you didn't have to have the sensor stuck in your arm. And I'm not surprised that that that's coming, and we'll be around before too long, just because we're learning so much about other ways of making the measurements that it makes sense to be able to do that. Devin Miller 29:31 Yep, no, absolutely. You know, it is a hard nut to crack. The body is very complex. A lot of things going on, and to measure it, not invasively, is certainly a lot that goes into it, but I think there's a lot of good, good technologies coming out. A lot of progress is being made, and certainly fun to continue to see how the health devices continue to hit the market. So certainly a cool area. Michael Hingson 29:53 So why did you decide, or maybe it was a natural progression, but why did you decide to go into patent law? Yeah. Devin Miller 30:01 I mean, I think it was probably a natural progression, and in the sense that, you know, it is one where overall desire was, Hey, I like engineering from the sense I like to think or how things work and kind of break things down and to have a better understanding. So really, intellectual property law and patents and trademarks and others allowed me to work with a lot of startups and small businesses, see a lot of cool things that they're developing still play a hand in it, and yet, also not, you know, be mired down to a long project over multiple years where you, you know, you're a small cog in a big wheel. And so, yeah, that was kind of one where it fit well within kind of the overall business, you know, business desire and business aspect of what I wanted to accomplish, and also just overall, you know, enjoying it or enjoying it. So that's kind of where it might, you know, it married well with the the desire to do startups and small businesses, as well as to work with a lot of other startups and small businesses. Michael Hingson 30:55 That's a lot of fun, to be able to deal with startups and see a lot of new and innovative kinds of things. And being in patent law, you probably see more than a lot of people, which does get to be exciting in an adventure, especially when you see something that looks like it has so much potential. Yep. Devin Miller 31:14 No, it is. It is fun. I get to see everything from I've worked on everything from boat anchors to credit card thing or devices that help elderly people to remove them more easily, from their wallet to AI to drones to software other or software platforms to medical devices. So it gives a ability to have a pretty good wide exposure to a lot of cool, different, you know, very different types of innovations, and that makes her just, you know, a fun, fun time, and be able to work or work with the air businesses as they develop. Are all those different technologies? Michael Hingson 31:50 Well, on the the law side of things, what's the difference between a provisional patent and a non provisional filing? Devin Miller 31:57 Yeah, so, so I don't back it up, and I'll get to your question. But maybe I'd set the stages to when you're looking at what is the difference between a patent and trademark and copyright, because a lot of times when people look at that, that's probably a good question too. Provisional trademark, or I want a, you know, or a non provisional copyright, or whatever it might be, and kind of get the terminology mixed up. So if you're to take it one step back, a provisional patent app or a patent is something that goes towards protecting an invention. So something that has the functionality that does something, that accomplishes something, a trademark is going to be something that is protecting of a brand. So name of a company, name of a product, a cash, phrase, a logo, and those type of things all really fall under trademarks and copyrights are going to be something that's more creative in nature. So a painting, a sculpture, a picture, a book, you know, all those type of things are going to fall under copyrights. And so really, when you're looking at it, you know, kind of breaking it down initially, you look at it as you know, which one is it. And so now to your question, Michael Hingson 32:58 well, before you go there, before you go ahead, before you go there. So if I'm writing software, does that fall under patent or copyright? I would assume if the software is to do something, it would be a patent. Devin Miller 33:12 So software primarily is under a patent. So there's, technically, you can copyright software. Now there's, it's pretty limited in its scope of protection. So if you're to do or software and do it under a copyright, really, all it protects is the exact way that you wrote the code. So you know, got it using this exact coding language. If somebody come along, copy and paste my code, you'll be protected. But it doesn't protect the functionality of how this code works or what it does. It is purely just how you wrote the code. So most of the time, when you're looking at software, it's really going to be more under a patent, because you're not going to want to just simply protect the identical way that you wrote the code, but rather what it does and what it does, yeah. So yep. So yeah, you for if you're to do as as your example, software, primarily, you're going to it's going to fall under patents. Michael Hingson 34:01 Okay, so anyway, back to provisional and non provisional. Devin Miller 34:05 Yeah, so, and when you're looking at doing a patent, you can do there's a couple different types of patents. One is a design patent. It really just goes to something the esthetic nature, the look and feel of a of an invention. So if you're thinking of the iPhone, you know, used to have the curved edges. I had the circle or a button at the bottom. It had, you know, the speaker placement and all those things. And it was just that outward appearance, not the functionality, could go under a design patent, but what the primary patent, which is what most people pursue, is what's called the utility patent application. And the utility patent application is really going towards the functionality of how something works. So the utility, how it works, what it does, and then kind of the purpose of it. And so with that, when you're looking at pursuing a utility patent application, there are a couple different types of patents that you can or types of utility patent patent applications. So. As you mentioned, one is called a provisional patent application. The other one is called a non provisional patent application. So a provisional patent application is kind of set up primarily, a lot of times for startups or small businesses where they're going to have a some product or an innovation that they're working on. They're in earlier stages. They're wanting to kind of protect what they have while they continue to develop it, and kind of flush it out. So provisional patent application is set up to be a one year placeholder application. So it will get, you know, you file it, you'll get patent pending, you'll get a date of invention, and it'll give you a year to decide if you want to pursue a full patent application or not. So you can file that gives you that one year time frame as a placeholder. The non provisional patent application would be the full patent application. So that would be what has, all the functionality, all the features, all the air, formalities and air, and it will go through the examination process. We'll go look at it for patentability. So those are kind of the difference provisional, one year, placeholder, less expensive, get your patent pending, versus the non provisional, that's the full patent application and gives you kind of that, or we'll go through examination. Michael Hingson 36:12 Do most people go through the provisional process just because it not only is less expensive, but at least it puts a hold and gives you a place. Devin Miller 36:22 It really just depends on where people are at. So kind of, you know, a lot of times people ask, Hey, well, what would you recommend? And I'll usually say, hey, there are typically two reasons why I would do a provisional patent application. And if you don't fall into either of those camps, then I would probably do a non provisional patent. Got it. So generally, the two reasons I get one is certainly budgetary. Give you an example. So our flat fee, you know, we do our primarily everything, flat fee in my firm, and a provisional patent application to prepare and file it, our flat fee is 2500 versus a non provisional patent application is 6950 so one is, Hey, your startup, small business, to have a limited funds, you're wanting to get a level of protection in place while you continue to pursue or develop things, then you would oftentimes do that as a provisional patent application. And the other reason, a lot of times where I would recommend it is, if you're saying, Hey, we've got a initial innovation, we think it's going to be great. We're still figuring things out, so we'd like to get something in place while we continue to do that research and develop it and kind of further figure it out. So that would be kind of, if you fall into one of those camps where it's either budgetary overlay, or it's one where you're wanting to get something in place and then take the next year to further develop it, then a provisional patent application is oftentimes a good route. There are also a lot of clients say, Hey, I'm, you know, we are pretty well. Did the Research Development getting ready to release it in the marketplace. While we don't have unlimited funds, we still have the ability to just simply go or go straight to a non provisional so we can get the examination process started, and then they'll go that route. So both of them are viable route. It's not kind of necessarily. One is inherently better or worse than the other is kind of more where you're at along the process and what, what kind of fits your needs the best. Michael Hingson 38:09 But at least there is a process that gives you options, and that's always good. Absolutely, patent laws, I well, I won't say it's straightforward, but given you know, in in our country today, we've got so many different kinds of things going on in the courts and all that, and sometimes one can only shake one's head at some of the decisions that are made regarding politics and all that, but that just seems to be a whole lot more complicated and a lot less straightforward than what you do With patent law? Is that really true? Or are there lots of curves that people bend things to go all sorts of different ways that make life difficult for you? Devin Miller 38:50 Um, probably a little bit of both. I think that it so. The law, legal system in general, is a much more slower moving enemy, so it does have a bit more of a kind of a basis to anticipate where things are headed in general. Now, the exception is, there always is an exception to the rule. Is that anytime the Supreme Court gets involved with patent law cases, I'd say 95% of the time, they make it worse rather than better. So, you know, you get judges that none of them are really have an experience or background in patent law. They've never done it. They really don't have too much familiarity with it, and now they're getting posed questions that are fairly involved in intricate and most of the time when they make decisions, they make it worse. It's less clear. You know, it's not as great of understanding, and it otherwise complicates things more. And so when you get the Supreme Court involved, then they can kind of make it more difficult or kind of shake things up. But by and large, it is a not that there isn't a lot of or involved in going through the process to convince the patent and examiner the patent office of patentability and make sure it's well drafted and has the it's good of coverage and scope, but at least there is, to a degree, that ability to anticipate. Hate, you know what it what's going to be required, or what you may likely to be looking at. You know? The other exception is, is, you know, the, ironically, I think the patent office is the only budget or producing or budget positive entity within all of the government. So every other part of the government spends much more money than they ever make. The Patent Office is, I think the, I think the postal office at one point was the other one, and they have, now are always in the in the red, and never make any money. But, you know, they are the patent office. Now, the problem with that is, you think, great, well now they can reinvest. They can approve, they should have the best technology, they should be the most up to date. They should have, you know, all the resources because they're self funding, and yet, there's always a piggy bank that the government goes to raid and redirects all those funds to other pet projects. And so, or the patent office is always, perpetually underfunded, as ironic as that is, because they're getting, always getting the piggy bank rated, and so with that, you know, they are, if you're to go into a lot of the patent office, their interfaces, their websites or databases, their systems, it feels like you're the onset of the or late 90s, early 2000s as far as everything goes. And so that always is not necessarily your question, but it's always a bit aggravating that you know you can't, as an example, can't submit color drawings. People ask, can you submit videos? Nope, you can't submit any videos of your invention, you know, can you provide, you know, other types of information? Nope, it's really just a written document, and it is line drawings that are black and white, and you can't submit anything beyond that. So there's one where I think eventually it will sometime, maybe shift or change, but it's going to be not anytime soon. I don't think there's any time on the horizon, because they're kind of stuck it once they move, moved over to the lit or initially onto the computer system, that's about where that evolution stopped. Michael Hingson 41:51 Well, the other thing though, with with videos, especially when you get AI involved and so on, are you really seeing a video of the invention. Or are you seeing something that somebody created that looks great, but the invention may not really do it. So I can understand their arguments, but there have to be ways to deal with that stuff. Devin Miller 42:13 Yeah, and I think that even be prior to AI, even we just had, you know, videos been around for 20 or 30 years, even, you know, digital format or longer. That probably, and the problem is, I think it's more of the search ability. So if you have a drawing, you can more easily search drawings and compare them side by side, and they'll do it. If you have a video, you know what? What format is the video? And is it a, you know, dot movie, or dot MOV, or is it.mp for is it color? Is it black and white? How do you capture it? Is it zoomed in as a kind of show all the details? Or is it zoomed out? And I think that there's enough difficulty in comparing video side by side and having a rigid enough or standardized format, the patent office said, man, we're not going to worry about it. Yes, so we could probably figure something out, but that's more work than anybody, any administration or any of the directors of the patent office ever want to tackle so it's just always kind of kicked down the road. Michael Hingson 43:06 Do they ever actually want to see the invention itself? Devin Miller 43:12 Not really, I mean, you so the short answer is no. I mean, they want to see the invention as it's captured within the the patent application. So the problem Michael Hingson 43:21 is, the drawing, they don't want to see the actual device, or whatever it is, well, and a lot Devin Miller 43:24 of times, you know as a inventors, they you know as a patent applicants, as the inventors and the owners, you're saying, hey, but I want to show them the invention. Problem is, the invention doesn't always mirror exactly what's showing in the patent application. Because you're on generation three of your product patent application is still in generation one, yeah, and so it doesn't mirror, and so the examiners are supposed to, they don't always, or aren't always good, and sometimes pull things and they shouldn't, but they're supposed to just consider whatever is conveyed in the patent application. Yeah, it's a closed world. And so bringing those additional things in now you can, so technically, you can request a live in office interview with the examiner, where you sit down live. You can bring in your invention or other or details and information, and when you do it live, face to face with an interview, you can walk them through it. Most very few people attorneys ever do that because one clients aren't going to want to pay for you to one of the offices, put you up in a hotel, you know, sit there, spend a day or two to or with the examiner to walk them through it. It just adds a significant amount of expense. Examiners don't particularly like it, because they have to dedicate significantly more time to doing that. Yeah, they're allotted, so they lose they basically are doing a lot of free work, and then you're pulling in a lot of information that they really can't consider. So you technically can. But I would say that you know, the likelihood of the majority of attorneys, 99 point whatever, percent don't do that, including myself. I've never been to do a live or live one, just because it just doesn't, it doesn't have enough advantage to make it worthwhile. Michael Hingson 44:58 Well, in talking about. About the law and all the things that go on with it. One of the things that comes to mind is, let's say you have somebody in the United States who's patenting, or has made a patent. What happens when it all goes to it gets so popular, or whatever, that now it becomes an international type of thing. You've got, I'm sure, all sorts of laws regarding intellectual property and patents and so on internationally. And how do you get protection internationally for a product? Devin Miller 45:32 File it in each country separately. So, you know, there are people, and I understand the inclinations, hey, I want to get a worldwide or global patent that covers everything in every country. The short answer is, you can't. I mean, technically, you could, if you file a patent into every country separately, nobody, including when I used to work or do work for companies including Intel and Amazon and Red Hat and Ford. They don't have patents in every single country throughout the world because they just don't have enough marketplace. You know, you go to a very small, let's say, South African country that you know, where they just don't sell their product enough in it, it just doesn't make the sense, or the courts or the systems or the patent office isn't well enough to find, or it's not enforceable enough that it just doesn't capture that value. And so there isn't a ability to have a global, worldwide patent, and it really is one where you have to file into each country separately. They each have their own somewhat similar criteria, still a different, somewhat similar process, but they each have their own criteria in their process that has to go through examination. So when you're looking at you know when you want to go for whether it's in the US or any other country, when you're deciding where you want to file it, it's really a matter of what marketplaces you're going to be selling the product into. So if you look at it and you know, I have as an example, some clients that 95% of their marketplace is all in the US, that's where they anticipate, that's probably where they're going to sell it. Well, yes, you could go and find, if you have 2% of your marketplace in Japan, you could go file a patent and get it into Japan, but you have such a small amount of your marketplace that's probably there that it doesn't make sense. And vice versa will have as an example. And a lot of times in the medical devices, they'll a lot of times file both in the EU as well as in the US, because those are two of the predominant medical device and are places where a lot of innovation is going on, where there's a lot of focus on utilization, development, medical devices, and there's just a lot of that demand. And so you're really going to look at it is which, where's your marketplace. The other times are the people, a lot of times, they'll get tripped up on so they'll say, Well, I probably need to file into China, right? And I said, Well, maybe because the inclination is, well, everybody just goes to China. They'll knock off the product. And so I want to have a patent in China so that I can, you know, fight against the knockoffs. And that isn't while I again, understand why they would ask that question. It wouldn't be the right way to convey it. Because if you if all it is is they you have no real, you know, no desire, no plan, to go into China. You're not going to sell it. You're not going to build a business there. If they're knocking it off and just just doing it in China, so to speak, then they're not. There isn't going to be a need to file a patent in China, because you don't have any marketplace in there. There's nothing really to protect. And if somebody makes it in China as a just picking on China, making as an example, and imports it into the US, you can still enforce your patent or otherwise do or utilize it to stop people from importing knock off because it's in the US, because they're, yeah, exactly, they're selling it, importing it, or otherwise doing activities in the US. So it's really a matter of where your marketplace is, not where you think that somebody might knock it off. Or, Hey, I'm gonna get a try and get a global patent, even though my marketplace is really in one or two spots. Michael Hingson 48:38 What about products like, say, the iPhone, which are commonly used all over. Devin Miller 48:44 Yeah, they're going to do, they'll do a lot of countries. They still Michael Hingson 48:47 won't do. They'll still do kind of country by country. Devin Miller 48:50 Yeah, they'll now, they'll do a lot of countries. Don't get me wrong, a lot of right. Phones are sold throughout the world, but they'll still look at it as to where it is, and they still have, you know, issues with them. So one of the interesting tidbits as an example, so going back and rewinding your time, taking apple as an example. You know, they came out with, originally, the iPod, then they had iPhone, and then they had the iPad. Now the question is, when they originally came out with their watch, what did they call it? 49:17 Apple Watch? Apple Watch. Now, why Devin Miller 49:20 didn't they call the I wash, which is what it made sense. It goes right along with the iPhone, the iPad, the iPhone, you know, the all of those iPod on that. And it was because somebody had already got a trademark in China that was for a different company, unrelated to the apple that had it for the iWatch. And so when Apple tried to go into the country, they tried to negotiate. They tried to bully. They weren't able to successfully get the rights or to be able to use I wash within China. China was a big enough market, and so they had and rather than try and split it and call it the I wash everywhere but China and trying to have the Apple Watch in China, they opted to call it the Apple Watch. Now I think they might. Of eventually resolve that, and I think it's now can be referred to as the I watch, I'm not sure, but for, at least for a long period of time, they couldn't. They called it the Apple Watch when they released it, for that reason. So even if you have, you know, a big company and one of the biggest ones in the world, you still have to play by the same rules. And why, you can try and leverage your your size and your wealth and that to get your way, there's still those, there's still those hindrances. So that's kind of maybe a side, a side note, but it's kind of one that's interesting. Michael Hingson 50:30 So that's the trademark of how you name it. But how about the technology itself? When the Apple Watch was created, I'm assuming that they were able to patent that. Devin Miller 50:39 Yeah, they will have, I'm sure they probably have anywhere from 30 to 100 to 200 I mean, they'll have a significant amount of patents, even it's just within the Apple Watch, everything from the screen, the display, how it's waterproof, how it does communications, how does the battery management, how does the touch, how does the interface, all of those are going to be different aspects that they continue to, you know, did it originally in the original Apple Watch, and are always iterating and changing as they continue to improve the technology. So generally, you know that, I'm sure that you will start out with as a business of protecting you're getting a foundational patent where you kind of protect the initial invention, but if it's successful and you're building it out, you're going to continue to file a number of patents to capture those ongoing innovations, and then you're going to file it into all of the countries where you have a reasonable market size that makes it worthwhile to make the investment. Michael Hingson 51:32 So if you have a new company and they've got a name and all that, what should new businesses do in terms of looking and performing a comprehensive search for of trademarks and so on to make sure they are doing the right thing. Devin Miller 51:49 Yeah, a couple of things. I mean, it wanted, if you're it depends on the size of company, your budget, there's always the overlay of, you know, you can want to do everything in the world, and if you don't have the budget, then you have to figure out what goes in your budget. But if I'll take it from kind of a startup or a small business perspective, you know, you first thing you should do is just as stupid and as easy as it sounds, you should go do a Google search. Or, now that you have chat GPT, go do a chat BT search and a Google search. But, you know, because it's interesting as it sounds, or, you know, is you think that, oh, that's, you know, kind of give me or an automatic I'll have still even till today, people come into my office. They'll say, Hey, I've got this great idea, this great invention, and a Lacher getting a patent on it, and they'll start to walk me through it. I'm like, you know, I could have sworn I've seen that before. I've seen something very similar. We'll sit down at my desk, take two minutes, do a Google search, and say, so is this a product that you're thinking of? Oh, yeah, that's exactly it. Okay. Well, you can't really get a patent on something that's already been invented and out there, and so, you know, do a little bit of research yourself. Now there is a double edged sword, because you can do research and sometimes you'll have one or two things happen. You'll not having the experience and background, not entirely knowing what you're doing. You'll do research, and you'll either one say, Hey, I've done a whole bunch of research. I can't really find anything that's similar. When, in fact, there's a lot of similar things out there. There's a patent, and people will say, yeah, it's the same, it's the same invention, but my purpose is a little bit different. Well, you can't if it's the exact same or invention. Whether or not you say your purpose is different, doesn't get around their patent and same thing on a trademark. Yeah, their brand's pretty much 53:20 identical, but they're Devin Miller 53:21 doing legal services and I'm doing legal tools, and so it's different, and it's, again, it's one where there's there they have a false sense of security because they rationalize in their head why it's different, or vice versa. You also get people that will say, Hey, this is even though it's significantly different, it's the same purpose. And so while, while they really could go do the product, while they could get a patent or a trademark, because they think that it's just overall kind of the same concept, then they talk themselves out of it when they don't need to. So I would say, start out doing some of that initial research. I would do it if I was in their shoes, but temper it with, you know, do it as an initial review. If there's something that's identical or the same that's out there, then it gives you an idea. Probably, you know, you're not going to be able to add a minimum, get or patent their intellectual property protection, and you may infringe on someone else's but if you you know, if there's, there's some differences, or have to do that initial research, that's probably the time, if you're serious about, you know, investing or getting business up and going, you've probably engaged an attorney to do a more formal search, where they have the experience in the background and ability to better give a better understanding or determination as to whether or not something presents an issue. Michael Hingson 54:32 Yeah, well, that's understandable. If I've developed something and I have a patent for it, then I suddenly discovered that people are selling knockoffs or other similar devices on places like Amazon and so on. What do you do about that? Because I'm sure there must be a bunch of that that that does go on today. Devin Miller 54:53 Yeah, yes, it does. I mean, I wouldn't say it's not as probably as prevalent as some people think. In other words, not every single. Product, right, being knocked off. Not everything is copied. Sometimes it's because, you know, either I don't have the ability, I don't have the investment, I don't have the, you know, it's not as big enough marketplace, I don't have the manufacturing, I don't have the connections, or it is simply, am respectful, and I'm not going to go do a discord because I'm not going to try and rip off, you know, what I think is someone else's idea. So it doesn't happen that as frequently as I think sometimes people think it does, but it certainly does occur. You know, there's a competitive marketplace, there's a profit incentive, and if there's a good product that's out there that people think they can do something with, and there's a motivation to do it, either because people are unaware that it's an issue, or that they they're unaware that they can't copy it or is protected. And so if you get into that, you know, there's a few potentially different recourses. One is, you know, a lot of times you'll start out with the cease and desist.
An airhacks.fm conversation with Holly Cummins (@holly_cummins) about: first computer experience with her dad's Kaypro CPM machine and ASCII platform games, learning Basic programming on an IBM PC clone to build a recipe management system, studying physics at university with a doctorate in quantum computing, self-teaching Java to create 3D visualizations of error correction on spheres during PhD research, joining IBM as a self-taught programmer without formal computer science education, working on Business Event Infrastructure (BDI) at IBM, brief unhappy experience porting JMS to .net with Linux and VNC, moving to IBM's JVM performance team working on garbage collection analysis, creating Health Center visualization tooling for J9 as an alternative to JDK Mission Control, innovative low-overhead always-on profiling by leveraging JIT compiler's existing method hotness data, transitioning to WebSphere Liberty team during its early development, Liberty's architectural advantage of OSGi-based modular core enabling small fast startup while maintaining application compatibility, working on Apache Aries enterprise OSGi project and writing a book about it, discussion of OSGi's strengths in protecting internal APIs versus complexity costs for application developers, the famous OSGi saying about making the impossible possible and the possible hard, microservices solving modularity problems through network barriers versus class loader barriers, five years as IBM consultant helping customers adopt cloud-native technologies, critique of cloud-native terminology becoming meaningless when everything required the native suffix, detailed analysis of 12-factor app principles and how most were already standard Java practices, stateless processes as the main paradigm shift from JavaServer Faces session-based applications, joining Red Hat's quarkus team three and a half years ago through Erin Schnabel's recommendation, working on Quarkiverse community aspects and ecosystem development, leading energy efficiency measurements confirming Quarkus's sustainability advantages, current role as cross-portfolio sustainability architect for Red Hat middleware, writing Pact contract testing extension for Quarkiverse to understand extension author experience, re-architecting Quarkus test framework class loading to enable deeper extension integration, recent work on Dev Services lazy initialization to prevent eager startup of multiple database instances across test profiles, fixing LGTM Dev Services port configuration bugs for multi-microservice observability setups, upcoming JPMS integration work by colleague David Lloyd requiring class loader simplification, the double win of saving money while also reducing environmental impact, comparison of sustainability benefits to accessibility benefits for power users, mystery solved about the blue-haired speaker at European Java User Groups years ago Holly Cummins on twitter: @holly_cummins
Show DescriptionWeb Day Out is coming up and Jeremy Keith from Clearleft (name pending the ShopTalk Show rebrand) is here to chat about it and while we've got him, Dave throws him on the hot seat to answer some hard hitting journalism questions about the state of the web in 2026. Listen on WebsiteWatch on YouTubeLinks Web Day Out in Brighton, March 12th 2026 Strategic design partners for website and service design | Clearleft css.properties Raycast - Your shortcut to everything Rachel Andrew – Doing stuff on the web since 1996. Browser support at Clearleft CSS Day 2026, 11th & 12th of June, Amsterdam SponsorsAxe-conAxe-con - the world's largest digital accessibility conference is from the makers of Axe-core and Axe DevTools Browser Extension. Taking place online on February 24-25. Registration is free and also gets you access to the on-demand recordings. Axe-con has a specific Development Track for dev content - some top speakers are Ire Aderinokun (front-end developer and Google developer expert), Jesse Beach (Software Engineering Manager at Meta), and other prominent folks from orgs like Coinbase, Zendesk, Red Hat, Atlassian, and more.
I needed that laugh. Whew! Kid Fury | Crissle Thisistheread.com Patreon Fury: patreon.com/kidfury Patreon Crissle: patreon.com/cw/CrisslesCouch Merch: shoptheread.com/ IG: @thisistheread Hosted by Simplecast, an AdsWizz company. See https://pcm.adswizz.com for information about our collection and use of personal data for advertising.
Show DescriptionWhy are AI tools so bad at CSS layout, Robin Rendle inspired monospaced fonts, CodePen's slideVars library, why are Safari dev tools so hard to use, button follow up, and what player component does ShopTalk use for it's website? Listen on WebsiteWatch on YouTubeLinks Clair Obscur | Expedition 33 Apple One Where's the AI design renaissance? Outlyne Bolt Lando Norris Robin Rendle Dave Rupert Casey Newton slideVars - Automatic Sliders for CSS Custom Properties Media Chrome Docs SponsorsAxe-conAxe-con - the world's largest digital accessibility conference is from the makers of Axe-core and Axe DevTools Browser Extension. Taking place online on February 24-25. Registration is free and also gets you access to the on-demand recordings. Axe-con has a specific Development Track for dev content - some top speakers are Ire Aderinokun (front-end developer and Google developer expert), Jesse Beach (Software Engineering Manager at Meta), and other prominent folks from orgs like Coinbase, Zendesk, Red Hat, Atlassian, and more.
What if consulting contracts rewarded results instead of hours worked? Tim Beattie, CEO of Stella and former Red Hat executive, is pioneering exactly that approach. In this conversation, Beattie breaks down the emerging consulting model that's replacing traditional project-based work. Subscription engagements provide clients ongoing access to expertise while creating predictable revenue streams. Asynchronous coaching through recorded videos scales impact beyond billable hours. AI tools amplify consultant knowledge without replacing human connection.
We're spending the winter out west with classic western movies and their stars in January. First up is Shane, the story of a gunfighter who tries to turn over a new leaf but has to fall back on his trade when his newfound family is threatened. We'll hear the two lead actors - Alan Ladd and Van Heflin - in Suspense shows as well as a radio recreation of the movie. First, Heflin is a reporter who receives an invitation from a murderer in "The Lady in the Red Hat" (originally aired on CBS on November 30, 1950). Then, Ladd stars in a tale of revenge from the old west in "A Killing in Abilene" (originally aired on CBS on December 14, 1950). Finally, both men reunite as The Lux Radio Theatre presents "Shane" (AFRS rebroadcast of a show from February 22, 1955).
IBM's recent acquisitions of Red Hat, HashiCorp, and its planned purchase of Confluent reflect a deliberate strategy to build the infrastructure required for enterprise AI. According to IBM's Sanil Nambiar, AI depends on consistent hybrid cloud runtimes (Red Hat), programmable and automated infrastructure (HashiCorp), and real-time, trustworthy data (Confluent). Without these foundations, AI cannot function effectively. Nambiar argues that modern, software-defined networks have become too complex for humans to manage alone, overwhelmed by fragmented data, escalating tool sophistication, and a widening skills gap that makes veteran “tribal knowledge” hard to transfer. Trust, he says, is the biggest barrier to AI adoption in networking, since errors can cause costly outages. To address this, IBM launched IBM Network Intelligence, a “network-native” AI solution that combines time-series foundation models with reasoning large language models. This architecture enables AI agents to detect subtle warning patterns, collapse incident response times, and deliver accurate, trustworthy insights for real-world network operations.Learn more from The New Stack about AI infrastructure and IBM's approach: AI in Network Observability: The Dawn of Network Intelligence How Agentic AI Is Redefining Campus and Branch Network Needs Join our community of newsletter subscribers to stay on top of the news and at the top of your game. Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
We make our big Linux predictions for 2026, but first, we score how we did for 2025.Sponsored By:Managed Nebula: Meet Managed Nebula from Defined Networking. A decentralized VPN built on the open-source Nebula platform that we love. 1Password Extended Access Management: 1Password Extended Access Management is a device trust solution for companies with Okta, and they ensure that if a device isn't trusted and secure, it can't log into your cloud apps. CrowdHealth: Discover a Better Way to Pay for Healthcare with Crowdfunded Memberships. Join CrowdHealth to get started today for $99 for your first three months using UNPLUGGED.Unraid: A powerful, easy operating system for servers and storage. Maximize your hardware with unmatched flexibility. Support LINUX UnpluggedLinks:
ServiceNow to acquire cybersecurity startup Armis MacSync Stealer adopts quieter installation Nissan customer data stolen in Red Hat raid Thanks to our episode sponsor, ThreatLocker Want real Zero Trust training? Zero Trust World 2026 delivers hands-on labs and workshops that show CISOs exactly how to implement and maintain Zero Trust in real environments. Join us March 4–6 in Orlando, plus a live CISO Series episode on March 6. Get $200 off with ZTWCISO26 at ztw.com.
What's Inside: The 5% Milestone: We analyze the data behind the massive surge in Linux desktop adoption and why gaming is the secret weapon. The UpTech Project: Máirín Duffy introduces us to a student-led initiative bridging the digital divide with Linux. 2026 Predictions: From RISC-V taking over wearables to the COSMIC desktop challenging the status quo, we look at where the "Time Machine" is headed. And so much more! 00:00:00 Intro: Linux Time Machine to 2026 00:01:50 Extended Intro: Meet Captain Ryan, Jill & Mo 00:02:20 Show Schedule Update: New Flight Plan 00:02:59 Community Feedback: The Great Cranberry Sauce Debate 00:12:40 AI and Energy: Hungry Models, Huge Power Bills 00:15:51 Empowering Youth Through Linux & Tech 00:29:11 2025 Highlights: Linux Market Share Levels Up 00:33:18 Outtake: Technical Turbulence in the Time Machine 00:34:16 Shifting to Linux & AI: Hype, Hope, and Worry 00:40:38 Steam Machines Dream: PC Gaming's Second Chance 00:43:38 SteamOS on ARM: Deck Power Everywhere 00:45:34 Wayland Takes the Bridge: Desktop Evolution 00:49:07 Red Hat Lightspeed: AI Co‑Pilot for Sysadmins 00:56:58 Destination Linux Grew: 2025 Community Wins 00:58:32 Linux 2026: Bold Predictions & Future Trends 01:03:00 Cosmic Becomes the Top DE? 01:06:41 Windows' AI Future: Copilot All the Things 01:09:13 Linux Desktop Market Share: Past 5%, Aiming Higher 01:09:38 Subscription Backlash: Users Hit Unsubscribe 01:11:27 Return to Physical Ownership: Discs, Devices & Freedom 01:15:28 Old Is Better: Vintage Gear vs Disposable Tech 01:21:09 AI's Role in Linux Development: Help or Hassle? 01:24:57 A Bold Prediction: Jill's 2026 Mohawk 01:26:19 Future Show Tease: More Linux, Less Bloat 01:26:44 Thanks Mo: Red Hat Wisdom in the Time Machine 01:27:07 Outro: See You in 2026
Links James on LinkedIn (https://www.linkedin.com/in/jahuang/) Mike on LinkedIn (https://www.linkedin.com/in/dominucco/) Mike's Blog (https://dominickm.com) Show on Discord (https://discord.com/invite/k8e7gKUpEp) Alice Promo (https://go.alice.dev/data-migration-offer-hands-on) AI on Red Hat Enterprise Linux (RHEL) Trust and Stability: RHEL provides the mission-critical foundation needed for workloads where security and reliability cannot be compromised. Predictive vs. Generative: Acknowledging the hype of GenAI while maintaining support for traditional machine learning algorithms. Determinism: The challenge of bringing consistency and security to emerging AI technologies in production environments. Rama-Llama & Containerization Developer Simplicity: Rama-Llama helps developers run local LLMs easily without being "locked in" to specific engines; it supports Podman, Docker, and various inference engines like Llama.cpp and Whisper.cpp. Production Path: The tool is designed to "fade away" after helping package the model and stack into a container that can be deployed directly to Kubernetes. Behind the Firewall: Addressing the needs of industries (like aircraft maintenance) that require AI to stay strictly on-premises. Enterprise AI Infrastructure Red Hat AI: A commercial product offering tools for model customization, including pre-training, fine-tuning, and RAG (Retrieval-Augmented Generation). Inference Engines: James highlights the difference between Llama.cpp (for smaller/edge hardware) and vLLM, which has become the enterprise standard for multi-GPU data center inferencing.
Guests Rynn Mancuso | Maryblessing Okolie | Mo McElaney Panelist Richard Littauer | Eriol Fox Show Notes In this episode of Sustain, Richard and Eriol talk with members of the Organization for Ethical Source (OES), Rynn Mancuso, Maryblessing Okolie, and Mo McElaney, about how ethics, licensing, and codes of conduct intersect in open source. They unpack the origins and challenges of the Hippocratic License, the community driven overhaul of Contributor Covenant 3.0, what it really takes to collaborate across borders and cultures, and how OES is now turning its attention to ethical AI, translations and practical resources for communities to make it a safer and more inclusive space. They also suggest ways for listeners to get involved in these important initiatives. Hit download now! [00:02:17] Rynn gives the elevator pitch on what the Organization for Ethical (OES) is. [00:04:57] Mo explains the Hippocratic License is modeled on “do no harm” and it's an open source license. [00:06:06] Richard wonders if the Hippocratic License is open source since we're not using OSI's definition. Mo explains that OES still uses “open source” in a broader, “big tent” sense focused on work done in the open, and Rynn adds why definitions need to evolve. [00:09:27] Rynn shares rewriting the Contributor Covenant 3.0, starting from their background, to being a limited scope, and getting feedback from translators that language was too American/Western and 3.0 needed a broader cultural fit. [00:15:12] Maryblessing was brought in to lead v3.0 from an African, non-US perspective and to make the process community driven. She tells us what's new in the Contributor Covenant 3.0. [00:19:43] The discussion covers how they all worked together. It was a highly collaborative, consensus driven process where anyone could propose edits. They talk about how long it took, not work entirely on GitHub, and why not everything was public. [00:24:59] We hear about some adoption challenges for codes of conduct for small projects and enterprises. [00:28:53] Rynn, Mo, and Maryblessing touch on how they are approaching ethical AI work, they share options to support OES, how to get involved, and translation needs. Quotes [00:12:32] “It was a very limited scope, and we always designed it to work on the internet and be for open source projects.” [00:13:23] “I would get these problems that really had to do with caste, but nobody would say anything about caste.” [00:16:37] “This new version also emphasizes restorative justice, and we're keen on using inclusive languages.” [00:17:06] “We're making progress on bringing in African translation.” [00:17:38] “One of the things we did with the new website was to include the CC3 builder which was going to help make it easy for people to adapt the code of conduct.” [00:21:37] “Every bit of feedback we got, we took it seriously, we talked about it.” [00:22:13] “It took is a year and six months to do the entire thing, to make sure people were available. It took that long because we wanted to make sure we were incorporating every feedback.” [00:23:14] “We do not do everything in the open on GitHub. One reason is structural. GitHub is not great at document management. Another reason we do that is we've received a lot of harassment form groups on the internet that were frankly invested in being able to cause trouble for a lot of people.” [00:29:14] “We're in the early stages of considering how we could approach ethical AI.” Spotlight [00:33:12] Mo's spotlight is for more folks to get involved with this project and other projects through the OES. [00:33:34] Rynn's spotlight is a shoutout to the folks at IBM and RedHat and Dev/Mission and JVS where they volunteer. [00:35:25] Maryblessing's spotlight is all the amazing people that helped put together the Contributor Covenant v.3.: Greg Cassel, Coraline Ada Ehmke, Gerardo Lisboa, Rynn Mancuso, Mo McElaney, Maryblessing Okolie, Ben Sternthal, and Casey Watts. [00:36:11] Eriol's spotlight is the OpenSSF Working Group on Securing Software Repositories. [00:36:44] Richard's spotlight is a fun paper called, Paradoxes of Openness: Trans Experiences in Open Source Software by Hana Frluckaj, Nikki Stevens, James Howison, and Laura Dabbish. Links SustainOSS (https://sustainoss.org/) podcast@sustainoss.org (mailto:podcast@sustainoss.org) richard@sustainoss.org (mailto:richard@sustainoss.org) SustainOSS Discourse (https://discourse.sustainoss.org/) SustainOSS Mastodon (https://mastodon.social/tags/sustainoss) SustainOSS Bluesky (https://bsky.app/profile/sustainoss.bsky.social) SustainOSS LinkedIn (https://www.linkedin.com/company/sustainoss/) Open Collective-SustainOSS (Contribute) (https://opencollective.com/sustainoss) Richard Littauer Socials (https://www.burntfen.com/2023-05-30/socials) Eriol Fox X (https://x.com/EriolDoesDesign) Rynn Mancuso LinkedIn (https://www.linkedin.com/in/rynnmancuso/) Maryblessing Okolie LinkedIn (https://www.linkedin.com/in/maryblessingokolie/?originalSubdomain=ng) Mo McElaney LinkedIn (https://www.linkedin.com/in/maureenmcelaney/) Organization For Ethical Source (OES) (https://ethicalsource.dev/) OES- What We Do (https://ethicalsource.dev/what-we-do/) OES-What We Believe (https://ethicalsource.dev/what-we-believe/) Donate-The Organization for Ethical Source (Open Collective) (https://opencollective.com/ethical-source) Contributor Covenant (https://www.contributor-covenant.org/) Contributor Covenant 3.0 Code of Conduct (https://www.contributor-covenant.org/version/3/0/code_of_conduct/) Code of conduct enforcement guidelines (MDN Web Docs) (https://developer.mozilla.org/en-US/docs/MDN/Community/Community_Participation_Guidelines) Coraline Ada Ehmke (https://en.wikipedia.org/wiki/Coraline_Ada_Ehmke) Ethical Source- Beacon (https://github.com/EthicalSource/beacon) Adopt Contributor Covenant (https://www.contributor-covenant.org/adopt/) Resources for Community Moderators (https://www.contributor-covenant.org/resources/) Dev/Mission (https://devmission.org/) JVS (Jewish Vocational Services) (https://jvs.org/) Techtonica (https://techtonica.org/) OpenSSF Working Group on Securing Software Repositories (https://github.com/ossf/wg-securing-software-repos) Paradoxes of Openness: Trans Experiences in Open Source Software (ACM Digital Library) (https://dl.acm.org/doi/abs/10.1145/3687047) Credits Produced by Richard Littauer (https://www.burntfen.com/) Edited by Paul M. Bahr at Peachtree Sound (https://www.peachtreesound.com/) Show notes by DeAnn Bahr Peachtree Sound (https://www.peachtreesound.com/) Special Guests: Maryblessing Okolie, Maureen Mcelaney, and Rynn Mancuso.
An airhacks.fm conversation with Ales Justin (@alesj) about: Early computing experiences with spectrum 48ZX and game development in Yugoslavia, progression from Basic to Pascal to C/C++ and eventually Java, mathematics education and its application to programming, working on energy consumption analysis applications for Slovenian companies, transitioning from a big IT company to a startup focusing on energy sector software, implementing Spring deployer for JBoss and contributing to open source, joining JBoss/Red Hat after impressing Bill Burke and Mark Fleury with Spring-JBoss integration, working on JBoss microcontainer with Adrian Brock and emphasis on precise testing, development of CapeDwarf as a JBoss implementation of Google App Engine APIs, collaboration with Google on TCK (Technology Compatibility Kit) development, solving concurrency bugs for a billion-dollar kitten app company using Cape Dwarf clustering, transition to cloud technologies with kubernetes and openshift integration, brief departure to work on cryptocurrency exchange using Spring Boot and Kafka, experiencing and solving Kafka / Strimzi issues on Google Cloud Platform, returning to Red Hat to work on Strimzi and eventually quarkus, focus on runtime systems and reactive programming with grpc and observability, importance of open source contribution and community engagement, evolution from monolithic application servers to cloud-native microservices architecture Ales Justin on twitter: @alesj
SQLite is embedded everywhere - phones, browsers, IoT devices. It's reliable, battle-tested, and feature-rich. But what if you want concurrent writes? Or CDC for streaming changes? Or vector indexes for AI workloads? The SQLite codebase isn't accepting new contributors, and the test suite that makes it so reliable is proprietary. So how do you evolve an embedded database that's effectively frozen?Glauber Costa spent a decade contributing to the Linux kernel at Red Hat, then helped build Scylla, a high-performance rewrite of Cassandra. Now he's applying those lessons to SQLite. After initially forking SQLite (which produced a working business but failed to attract contributors), his team is taking the bolder path: a complete rewrite in Rust called Turso. The project already has features SQLite lacks - vector search, CDC, browser-native async operation - and is using deterministic simulation testing (inspired by TigerBeetle) to match SQLite's legendary reliability without access to its test suite.The conversation covers why rewrites attract contributors where forks don't, how the Linux kernel maintains quality with thousands of contributors, why Pekka's "pet project" jumped from 32 to 64 contributors in a month, and what it takes to build concurrent writes into an embedded database from scratch.--Support Developer Voices on Patreon: https://patreon.com/DeveloperVoicesSupport Developer Voices on YouTube: https://www.youtube.com/@DeveloperVoices/joinTurso: https://turso.tech/Turso GitHub: https://github.com/tursodatabase/tursolibSQL (SQLite fork): https://github.com/tursodatabase/libsqlSQLite: https://www.sqlite.org/Rust: https://rust-lang.org/ScyllaDB (Cassandra rewrite): https://www.scylladb.com/Apache Cassandra: https://cassandra.apache.org/DuckDB (analytical embedded database): https://duckdb.org/MotherDuck (DuckDB cloud): https://motherduck.com/dqlite (Canonical distributed SQLite): https://canonical.com/dqliteTigerBeetle (deterministic simulation testing): https://tigerbeetle.com/Redpanda (Kafka alternative): https://www.redpanda.com/Linux Kernel: https://kernel.org/Datadog: https://www.datadoghq.com/Glauber Costa on X: https://x.com/glcstGlauber Costa on GitHub: https://github.com/glommerKris on Bluesky: https://bsky.app/profile/krisajenkins.bsky.socialKris on Mastodon: http://mastodon.social/@krisajenkinsKris on LinkedIn: https://www.linkedin.com/in/krisjenkins/--0:00 Intro3:16 Ten Years Contributing to the Linux Kernel15:17 From Linux to Startups: OSv and Scylla26:23 Lessons from Scylla: The Power of Ecosystem Compatibility33:00 Why SQLite Needs More37:41 Open Source But Not Open Contribution48:04 Why a Rewrite Attracted Contributors When a Fork Didn't57:22 How Deterministic Simulation Testing Works1:06:17 70% of SQLite in Six Months1:12:12 Features Beyond SQLite: Vector Search, CDC, and Browser Support1:19:15 The Challenge of Adding Concurrent Writes1:25:05 Building a Self-Sustaining Open Source Community1:30:09 Where Does Turso Fit Against DuckDB?1:41:00 Could Turso Compete with Postgres?1:46:21 How Do You Avoid a Toxic Community Culture?1:50:32 Outro
Tiffany Anton sits down with Vickie Pelamati and Karen Ritchie of The Lovely Find Tea Room, a charming Granville getaway dedicated to preserving the traditional English tea experience. Vickie, the owner, shares how purchasing a small house after her husband's passing inspired her vision for a tea room, while Karen, the manager, explains her love for classic English Tea Time and how that passion turned into a business with her best friend. Together, they discuss serving everyone from Red Hat ladies and Girl Scouts to men in overalls—with special mugs ready for larger hands—and how their faith keeps them moving forward through every challenge. Karen breaks down their rotating English lunch menu, unique tea blends, regular customer groups, and their intimate 18-guest capacity, along with their five-year-old age limit to preserve the experience. They also preview upcoming events, including a festive visit from Mrs. Claus on December 14th and 15th. Listen To The Local Matters Podcast Today! News Talk 94.1
According to the WIN World AI Index only 3% of Irish consumers aged between 35-54 engage with AI regularly. To find out more about this I spoke to Ivan Jennings, Tech Sales Leader Red Hat Ireland .Ivan talks about his background, the first ever WIN World AI Index Irish findings, AI, ubiquitous computing and moreMore about the WIN World AI Index Survey:The WIN World AI Index Survey 2025 is a global initiative capturing how people in 40 countries perceive, understand, and prepare for the rise of Artificial Intelligence. This pioneering survey provides a unique snapshot of global AI readiness, trust, and usage.
We pull on a few loose threads from recent episodes, and some of them unravel into way more than we expected.Sponsored By:Managed Nebula: Meet Managed Nebula from Defined Networking. A decentralized VPN built on the open-source Nebula platform that we love. 1Password Extended Access Management: 1Password Extended Access Management is a device trust solution for companies with Okta, and they ensure that if a device isn't trusted and secure, it can't log into your cloud apps. CrowdHealth: Discover a Better Way to Pay for Healthcare with Crowdfunded Memberships. Join CrowdHealth to get started today for $99 for your first three months using UNPLUGGED.Unraid: A powerful, easy operating system for servers and storage. Maximize your hardware with unmatched flexibility. Support LINUX UnpluggedLinks:
At KubeCon + CloudNativeCon 2025 in Atlanta, the panel of experts - Kate Goldenring of Fermyon Technologies, Idit Levine of Solo.io, Shaun O'Meara of Mirantis, Sean O'Dell of Dynatrace and James Harmison of Red Hat - explored whether the cloud native era has evolved into an AI native era — and what that shift means for infrastructure, security and development practices. Jonathan Bryce of the CNCF argued that true AI-native systems depend on robust inference layers, which have been overshadowed by the hype around chatbots and agents. As organizations push AI to the edge and demand faster, more personalized experiences, Fermyon's Kate Goldenring highlighted WebAssembly as a way to bundle and securely deploy models directly to GPU-equipped hardware, reducing latency while adding sandboxed security.Dynatrace's Sean O'Dell noted that AI dramatically increases observability needs: integrating LLM-based intelligence adds value but also expands the challenge of filtering massive data streams to understand user behavior. Meanwhile, Mirantis CTO Shaun O'Meara emphasized a return to deeper infrastructure awareness. Unlike abstracted cloud native workloads, AI workloads running on GPUs require careful attention to hardware performance, orchestration, and energy constraints. Managing power-hungry data centers efficiently, he argued, will be a defining challenge of the AI native era.Learn more from The New Stack about evolving cloud native ecosystem to an AI native eraCloud Native and AI: Why Open Source Needs Standards Like MCPA Decade of Cloud Native: From CNCF, to the Pandemic, to AICrossing the AI Chasm: Lessons From the Early Days of CloudJoin our community of newsletter subscribers to stay on top of the news and at the top of your game. Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
Join Alyssa & (baby) Jamie for a Thanksgiving Fathead Feast along with some turkey talk. Happy Thanksgiving Fatheads!Turkey Calls | "Best Wild Turkey Hen Calling and Yelping 2" by: Jay Scotthttps://www.youtube.com/watch?v=HAS6G7Uq4Oc Write us some of your cringe stories at nervouslaughterpodcast@gmail.comThe socials: Instagram | Facebook | Twitter
In this Technology Reseller News, Podcast, Doug Green interviews Don Boxley, CEO and Co-Founder of DH2i, for a deep dive into one of the biggest challenges facing IT teams today: the migration gap between legacy Windows-based SQL Server deployments and the containerized, Linux-driven future that modern applications increasingly require. DH2i, a long-time Microsoft and Red Hat partner, delivers high availability, secure communication, and cross-platform mobility for SQL Server, Oracle, and MySQL environments. Their flagship platform, DX Enterprise, enables customers to run the same production-grade SQL instance across Windows, Linux, and Kubernetes — and move between them with seamless failover. As Boxley explains, this eliminates the traditional roadblocks that keep enterprises locked into aging infrastructure. With SQL Server 2025 bringing new support for AI-driven applications, Microsoft tapped DH2i to deliver mission-critical HA capabilities for these next-generation workloads. The company also introduced a hands-on, step-by-step Minikube tutorial, allowing DBAs and MSPs to experiment safely with Kubernetes-based SQL deployments on their own PCs before ever touching production. “Most teams think they're stuck on Windows — they're not. With DX Enterprise, you can move SQL Server to Linux or containers without disruption, and your customers won't even know the difference,” Boxley notes. DH2i's developer edition is available as a free download, complete with 30-day support, giving IT teams a no-risk path to testing, learning, and modernizing their database infrastructure. Learn more at https://dh2i.com/. Software Mind Telco Days 2025: On-demand online conference Engaging Customers, Harnessing Data
2B Bolder Podcast : Career Insights for the Next Generation of Women in Business & Tech
AI only works at scale when the shiny demo meets the gritty realities of deployment, security, and change management. In episode #146 of the 2B Bolder Podcast, I had the pleasure of sitting down with Monica Livingston, AI Platform Lead for the Americas at Red Hat and a former Intel leader, to unpack how open source accelerates real outcomes, and why the “plumbing” behind enterprise AI matters more than most roadmaps admit. Monica shares a clear view of what platforms must do in production: version control, monitoring, governance, policy, and cost discipline, all while staying flexible enough to avoid stack lock-in.We get candid about the two biggest misconceptions leaders hold: AI isn't a black box you plug in once, and the most complex variable is people, not models. Monica explains how to align teams through transparency, psychological safety, and clear KPIs so pilots survive the leap to operations. She also offers practical advice for new managers under pressure, from building trust to making recognition routine, and reflects on mentors who pushed her to trade constant breadth for deep expertise that compounds.For anyone mapping a career in AI, this conversation covers real paths forward, including accessible learning, hands-on projects, and emerging roles that are reshaping the field. We discuss early STEM exposure as a lever for agency, guidance for young women entering the tech field, and the value of calculated risk anchored in personal values such as family and health. Monica also shares her perspective on how to stand out in crowded applicant pools, the power of referrals, and why transformation often occurs on your own time before it becomes a job title.If this resonates, follow and share with a colleague who's building AI for the real world. Subscribe for more conversations at the intersection of open technology, human leadership, and careers with purpose, and leave a quick review to help others find the show.Hi Mary here, through my conversations with women leaders, I've learned just how urgent the need is for AI strategies that actually make sense. It's not about adopting tools just to keep up; it's about building a smart foundation. That's exactly what Beyondsoft is doing. To learn more visit https://www.youtube.com/playlist?list=PL-yCsEeZbsl6ivoZoS9YW1quYxbQr1Teo
Rod and Karen Nicki Minaj’s Trump supporting, Kid Rock uses the r-word on Fox News, NBC guts DEI, bomb threats called into NJ voting precincts, Heritage Foundation culture war, George Clooney says running Kamala was a mistake, White People News, man burns down pride flags, man kills store clerk over pizza made with no gloves, mom kills monkey and sword ratchetness. Patreon: https://www.patreon.com/theblackguywhotips Twitter: @rodimusprime @SayDatAgain @TBGWT Instagram: @TheBlackGuyWhoTips Email: theblackguywhotips@gmail.com Blog: www.theblackguywhotips.com Teepublic Store Amazon Wishlist Crowdcast Voicemail: (980) 500-9034Go Premium: https://www.theblackguywhotips.com/premium/See omnystudio.com/listener for privacy information.
After all the AI hype is over, one change for Linux will be sticking around; we put it to the test.Sponsored By:Managed Nebula: Meet Managed Nebula from Defined Networking. A decentralized VPN built on the open-source Nebula platform that we love. 1Password Extended Access Management: 1Password Extended Access Management is a device trust solution for companies with Okta, and they ensure that if a device isn't trusted and secure, it can't log into your cloud apps. CrowdHealth: Discover a Better Way to Pay for Healthcare with Crowdfunded Memberships. Join CrowdHealth to get started today for $99 for your first three months using UNPLUGGED.Unraid: A powerful, easy operating system for servers and storage. Maximize your hardware with unmatched flexibility. Support LINUX UnpluggedLinks:
This week SUSE's SLES and Red Hat's RHEL are embracing AI in the form of MCP and CUDA support. FFMPEG scores a $100k donation, Pop_OS and Cosmic finally have a release data, and Unity is in need of help. Kodi 22 has an Alpha, Debian has a Systemd dustup, and Krita has landed HDR support. And there's a port of Linux to WASM, so you can run the kern in your browser. Handy! For tips we have doxx for opening .docx in the terminal, a primer on absolute vs relative paths, whoami for grabbing the current username, and btrfs's scrub command for checking the local disk. You can find the show notes at https://bit.ly/4ovhsLG and have a great week! Host: Jonathan Bennett Co-Hosts: Rob Campbell, Jeff Massie, and Ken McDonald Download or subscribe to Untitled Linux Show at https://twit.tv/shows/untitled-linux-show Want access to the ad-free video and exclusive features? Become a member of Club TWiT today! https://twit.tv/clubtwit Club TWiT members can discuss this episode and leave feedback in the Club TWiT Discord.
[I meant to get this out before Halloween, but life got in the way — previous Janet stories — Part One | Part Two ]Janet left Two Moons Yoga Studio, where a gaggle of concerned American citizens — the true patriots — held an emergency “No Kings, Cancel Halloween” meeting to save democracy. The attendees were Janet's age. They were her neighbors, but she didn't know most of them. They were all directed to join the NextDoor app to get to know each other better online.Janet used the app frequently. Even though they had a rule about no politics, she would use NextDoor to inform her neighbors if ICE agents had entered the town's perimeter. She would also warn neighbors about the e-bikes speeding through town, endangering animals and pedestrians. She would take pictures of people whose dogs left messes that their owners did not pick up and post them on NextDoor, and she would make sure to let everyone know how many people were responsibly wearing masks at the Farmer's Market.COVID wasn't over, Janet knew. It was still a constant threat, especially to the marginalized, trans people, Black and Brown people, and immigrants. It was her duty to wear a mask at all times, even at the meeting at Two Moons Yoga. Only some people there were wearing masks, but not all. Janet was sure to jot down their names in case she needed to warn people later.The meeting went well. Everyone was on the same page that democracy and their way of life were now under a grave threat. This is not normal, said Barack Obama. Janet agreed. Their action plan was to go door to door and inform their neighbors that Halloween would be canceled due to the government shutdown and the fascist occupation of the country. They had even bigger goals, like canceling Thanksgiving and boycotting Christmas, too. But one step at a time. Halloween was in just a few days, and it was time to send a message to the government that we would not be buying candy or trick-or-treating while Nazis roamed our streets.Everyone had a list of the neighborhood's sections. Janet would go that evening after she watched MSNBC. She didn't want to interrupt her neighbors, who were probably just as glued to their TVs. That was the only way to stay informed now that the country has been overtaken by fascists.Nothing else can be trusted now. The media is terrified of Trump, not even the ladies of The View talk politics anymore. Janet can only watch for five minutes before they move on to shallow interviews and publicity hits. Trump has intimidated everyone, suing networks, disappearing Jimmy Kimmel for a joke, and that has had a chilling effect on free speech. Janet wasn't exactly thrilled about knocking on doors, but she had to do something. She couldn't just stay home and post about HIM on Facebook and NextDoor. Some had suggested giving out bags of groceries to those whose SNAP benefits would run out. Yes, a community effort for the poor and downtrodden. It's just that Vista Butte isn't a town full of poor people. It was expensive to live here. Were there poor people in this town? Then she remembered the maid who comes to clean her house once a month, and everyone has a gardener. Maybe she would approach them with a bag of groceries when she saw them at work. Would it be weird to take a selfie and post it on Instagram to show how important it is to recognize the poor right now?Assuming the maid was poor just because she cleaned houses for a living wasn't racist, was it? Is it offensive to call her a maid? What's the appropriate term? Janet asked ChatGPT. The answer: housekeeper, house cleaner, or domestic worker.” Okay, so domestic workers might be the poor people in Vista Butte, like immigrants. Janet did her best not to offend marginalized people. She didn't know if any such people lived in Vista Butte. The town was, after all, 96% white, affluent, and very liberal. But on the off chance she might encounter one, she wanted them to know she cared about their health, too. That's why she wears a mask outside every day.Janet began walking up her street and could feel the October breeze. This was the best time of year in Vista Butte. It wasn't too hot and it wasn't yet too cold. It was one of those perfect fall days. Every so often, you could smell smoke from a fireplace off in the distance. She didn't want to think about HIM on a day like this. She needed to be living in the moment more. Self-care. Meditation. Daily walks. Breathing exercises.The election was almost one year ago. Janet's hair had finally grown back after she shaved it to protest THE FASCIST in the White House. She thought about keeping it because people were so kind to her when they thought she was battling cancer. She never said she was. They just assumed, and she kind of let them. It felt good to have people be nice to her.Things aren't getting better, Janet knew. They're getting worse. Much worse. He disembowled the East Wing to put up a Nazi building. He defiled the Lincoln bedroom's bathroom and put in a Roman bathhouse. Everything is ugly, tacky gold. He hates America! He had a late-stage Roman Empire ball at Mar-a-Lago, apparently. While millions were about to starve because of the government shutdown. He was having a party for billionaires!Janet tried not to think of it. Instead, she looked around at all of the Vote Yes on Prop 50 signs that were stabbed into the lawns of all of her neighbors. What good people they were. They raised $120 million. Imagine that. Of course, it will pass. We have to save democracy, she thought, by adding more seats in Congress. Janet herself donated around $300. Somewhere in the distance, she could hear buzzing, whirring, what is that sound? She knew before she even saw them that it was those kids on the electric bikes that had been terrorizing the town. E-Bikes. Everyone had complained on Next Door. Even the MAGGAt, who goes by the name RedHat. Even he, or she, or they, no he or she, hated them. They were dangerous. They were loud. It was the only time she and RedHat agreed on anything. He was always the first to chime in on her ICE posts. “Good job, ICE,” he would say. “We need to protect American workers,” and “the media is lying about ICE and scaring people.” But Red Hat was living in a Fox News fantasy world, Janet knew. Their fights got so heated that Janet had to block RedHat and then warn everyone on Next Door not to engage with him. There is no point, she would say. He is too lost and can't be helped. All we can do is block him. But he just made a new account. What will we do with all of these racists who voted for Trump? She thought, We can't live with them. We can't forgive them. Their days are numbered. Already, the Democrats are leading in the polls. It's just a matter of time before we take back the country and save democracy. But what to do with all of those bad people? Janet didn't know. But she hoped someone did. Red Hat was right about the bikes, though. The kids didn't know how to control them. They went too fast down the road. They scared dogs and cats, and they scared Janet. She could hear them off in the distance now. Then, she could see them. There they were, a gang of about six boys speeding right toward her. Janet was still holding her No Kings sign, which she'd brought to the meeting, which said No KKK No FASCIST USA and NO KINGS. She held it up in front of her so the boys could see her clearly in case they weren't paying attention. Could they see her? They had a devilish look on their faces and were speeding right toward her. Were they planning on hitting her? Would they hit a middle-aged woman in a mask carrying a No Kings sign? Yes, Janet knew, they would because they're DUMB KIDS. It was now a game of chicken, and Janet was not playing that game. Just as they got within a few feet of her, she leaped out of the way and stumbled, falling face down onto the concrete. She could hear them screaming with laughter as they sped by. “Chicken!” one of them called out. Janet was furious. She ripped her mask off her face and stood in the middle of the road with her cell phone aimed right at them. “I'm recording you!” She said. The boys screeched to a halt on their bikes and turned around to look at her. They apparently thought this was really funny because they could not stop laughing. “Go ahead, No Kings,” one of them said, and that cracked them all up even more. “I will!” Janet said, “And then I'll call the police! How do you like that?” “We didn't do anything,” another said. A couple of them had their own cell phones out and began recording her. “You tried to kill me!” Janet said. That made the boys burst into yet more uncontrollable giggles as they began mocking her. “Oh, no! She almost died!” ”Death by E-bike!”“You don't even live in this town, do you?” Janet said. “Why don't you go back to where you came from?” “Why don't you?” One of them said. “I live here. Do you?”They didn't answer, but just thought the whole thing was either super funny or a waste of time. And with that, off they went, with their noisy, irritating, dangerous E-Bikes headed for who knows where. Janet searched around for her mask, but the strap was broken. She was too traumatized to bother picking it up. She did take her sign, which was wrinkled and dirty. She looked around to see if any of her neighbors had witnessed the ugly scene. She might need a witness if she called the cops. But why bother? What could they do? She would keep trying to get E-Bikes banned so the neighborhood could be peaceful and orderly again. She was just a block away from her house now. Tears were streaming down her face. Why did those kids have to be so mean? Why are they so aggressive? Boys, that's why. Boys who grow up to be men. Boys who can't be controlled. That's what is wrong with our society, Janet knew. Just look at all of the damage caused by Trump. The Gestapo was disappearing people off the streets and putting them somewhere, ripping children from the arms of their mothers and putting them on trains. Sending grandmothers to concentration camps. All because they're Brown and the racists on the Right want only a WHITE AMERICA.He's sent in the military to occupy our cities. It's not to protect ICE, stop crime, or clean up the streets. It's to implement MARTIAL LAW to put all of us under federal control. It won't be long before we're snatched off to death camps just for making a joke or having a NO KINGS rally. Of course, Fox News will shrug it off. That's how the Holocaust happened. The Good Germans did nothing. Janet finally got home and flopped down on the couch. That was too much activity for someone who never left the house. She closed her eyes to take a quick nap before checking social media. Just as Janet was drifting off, she heard her phone ping. Someone had texted her. She glanced down and saw it was the woman who organized the Cancel Halloween meeting. The message said, “Call me. It's urgent.” Janet's first instinct was not to call her back, to pretend she didn't get the message or that she slept through it. Whatever it was that was urgent, Janet didn't want to know. But she picked up her phone and called anyway.“Kim?”“Hi Janet, thanks for calling. ””Yes, Kim, how are you?” Janet was trying to counter Kim's panic with calm. ”I'm okay, I just—have you looked at Facebook?””No, I just got home. I was about to work out.””You should probably check it now. Did you tell an immigrant and a mixed-race child that they didn't belong in this town and to go back where they came from?”A cold chill ran down Janet's spine. Her palms began to sweat. She could see the scene play out in her mind, the cell phones recording her as she said those exact words. But “go back to where they came from” just meant whatever town they lived in that wasn't Vista Butte.“Well, I didn't say that exactly,” Janet said.”That's what it looks like in that viral video.””There's a viral video? It just happened like 15 minutes ago.””So it did happen,” Kim said.”Well, I mean, they tried to kill me.””You're a white woman, Janet.””And what's that supposed to mean?””One of those kids was mixed race,” Kim said.”They all looked white to me,” Janet said. ”One kid's stepfather is Black, apparently,” Kim said.”Stepfather? So that's not his biological father, Kim. And what is he, like the only Black person in Vista Butte?””Well, I'm just telling you what is happening online right now. You should go look, and I think, given the anger and tension around this, it's best that you do not go door to door or engage with anyone on behalf of our group.”And with that, Kim hung up the phone without even saying goodbye. Janet sat there, stunned. One of those boys was a migrant child? A Brown child? And she told him to go back to where he came from? And a mixed-race child? In a town that's 96% white. Her phone was pinging with Nextdoor notifications. She checked there first. There was a whole thread about her, the so-called “racist” video was now playing on the app. There was Janet screaming at the kids, “Go back to where you came from!” It was filmed from a different perspective, though. It was from someone watching from inside their house. They must have posted the video. Who would do that? She read the comments. “What a terrible person.””That's scary.””It's sad what's happened to her.””I didn't know there were Karens in this town.””Racism is ugly and so is she.””I always knew there was something weird about her. She just seems off.””The kid has a mom who works at the local Wendys and ICE has just taken her. He's worried he's next.””She's MAGA now.””I hate ugly people, don't you?””She lives near me.””I see her walking outside sometimes. Scary.””There is nothing wrong with standing up for your morals and shutting these people out of your life forever.””We should meet later and figure out what to do about her.”Only one person, RedHat, pushed back. “Everything is racist with you people,” he wrote. Great, the MAGA guy. That's how low she sank. She was sick. Her stomach hurt. How could this be happening? Why did she say what she said? They all looked white to her. Were they all white? Now she couldn't even remember their faces. She only saw them laughing.She didn't want to look at Facebook, but she had to know what they were saying about her. There were dozens of posts on her wall calling her the worst names she'd ever heard in her life. There were lengthy posts from people she only knew online explaining why they were walking away and unfriending her. “It's a matter of morality,” they would explain. “Of decency.” “She is toxic,” one said. “She needs help,” said another. “Some people can't be helped,” said her old co-worker from years ago. “Racism is a disease,” said one of the women from the No Kings protest.Racist? Janet was starting to get angry now. She wasn't racist. She did everything she could to not be racist. She was careful never to say the wrong word. She wanted only the best for all of the marginalized groups. She hated white people. She knew they were the colonizers and the oppressors. She thought America was a rotten, corrupt, white supremacist empire that would elect a twice impeached, four times indicted, adjudicated rapist, felon, fascist, dictator! They were the racists, not Janet. Not JANET! Now things were starting to get weird. Should she call Kim back? Should she apologize on Facebook? That's what she did. She apologized. She sat down and wrote, “I am very sorry that I said those words. But I am not a racist. I don't have a racist bone in my body. I'm sorry if I offended anyone.” Then she posted it. Right away, the comments flooded in. “Too late,” one said. “It's always the racists who say they aren't racist,” said another. “You should take responsibility for the harm you caused.”Janet sank into the couch and put her head in her hands. Then she heard a knock on the door. Who could that be? She slowly approached the door and looked through the peephole. It was the women from the meeting. They were standing there, arms crossed.“Open the door, Janet. I know you're in there,” said one of the women. Janet said nothing. They pounded the door again. “You are not welcome at our meetings anymore, and we want you out of our neighborhood.” The other women chimed in, and they began clapping and chanting, “GO BACK TO WHERE YOU CAME FROM! YOU ARE NOT WELCOME HERE! Janet clutched her chest and fell to the floor. What is happening? She couldn't breathe…she couldn't breathe, and then, suddenly, she realized she was now on the couch and awake. She'd been dreaming. It was all a bad dream. She was sweating through her shirt. Her heart was pounding. She picked up her phone and looked at the screen. No notifications. She checked her history, no call from Kim. She looked on NextDoor, and there were no posts about her. She checked Facebook, same thing. And that was when she looked up to Heaven and thanked God. She had never done that before—not ever—but it seemed appropriate now. Thank you, God, she said. She knew there was a reason she'd had that dream. She knew it was a wake-up call to be a better person. Did that mean she should maybe try to make friends with RedHat? Would that be enough to redeem her? No, she knew. That dream was a warning. She had to be very careful from now on. And she would be. She would not break any rules. She would not even try to get the E-Bikes banned. She would be quiet and go along to get along. She picked up the phone and called Kim. “Hello?””Hi Kim, it's Janet. I was just wondering what time we would all be knocking on doors tonight.””Oh, hi, Janet. That would be around 7:30. We can meet down at Kate's Koffee at 7.””Sounds great!” Janet said. “See you then!”She turned on MSNBC, and there was Rachel Maddow looking worried, as usual. What now? Islamophobic attacks on Zohran Mamdani. A woman being manhandled by ICE agents. There were real problems to worry about, Janet realized, much bigger than whether some awful little brats had a damaging video of her. And yet, just as she felt herself relax, she heard her phone ping. She looked at it and said aloud, “Oh no.” TIP JAR// This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit www.sashastone.com/subscribe
SANS Internet Stormcenter Daily Network/Cyber Security and Information Security Stormcast
More .well-known scans Attackers are using API documentation automatically published in the .well-known directory for reconnaissance. https://isc.sans.edu/diary/More%20.well-known%20Scans/32340 RedHat Patches Openshift AI Services A flaw was found in Red Hat Openshift AI Service. A low-privileged attacker with access to an authenticated account, for example, as a data scientist using a standard Jupyter notebook, can escalate their privileges to a full cluster administrator. https://access.redhat.com/security/cve/cve-2025-10725#cve-affected-packages TOTOLINK X6000R Vulnerabilities Paloalto released details regarding three recently patched vulnerabilities in TotalLink-X6000R routers. https://unit42.paloaltonetworks.com/totolink-x6000r-vulnerabilities/ DrayOS Vulnerability Patched Draytek fixed a single memory corruption vulnerability in its Vigor series router. An unauthenticated user may use it to execute arbitrary code. https://www.draytek.com/about/security-advisory/use-of-uninitialized-variable-vulnerabilities
CISA furloughs most of its workforce due to the government shutdown. The U.S. Air Force confirms it is investigating a SharePoint related breach. Google warns of a large-scale extortion campaign targeting executives. Researchers uncover Android spyware campaigns disguised as popular messaging apps. An extortion group claims to have breached Red Hat's private GitHub repositories. A software provider for recreational vehicle and power sport dealers suffers a ransomware breach. Patchwork APT deploys a new Powershell loader using scheduled tasks for persistence. A Tennessee Senator urges aggressive U.S. action to prepare for a post-quantum future. Cynthia Kaiser, SVP of Halcyon's Ransomware Research Center and former Deputy Assistant Director at the FBI's Cyber Division, joins us with insights on the government shutdown. A Malaysian man pleads guilty to supporting a massive crypto fraud. Protected health info is not a marketing tool. 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 Cynthia Kaiser, SVP of Halcyon's Ransomware Research Center and former Deputy Assistant Director at the FBI's Cyber Division, joins us with insights on the government shutdown. Selected Reading Shutdown guts U.S. cybersecurity agency at perilous time (CISA) Air Force admits SharePoint privacy issue; reports of breach (The Register) Google warns executives are being targeted for extortion with leaked Oracle data (IT Pro) Researchers uncover spyware targeting messaging app users in the UAE (The Record) Red Hat confirms security incident after hackers claim GitHub breach (Bleeping Computer) 766,000 Impacted by Data Breach at Dealership Software Provider Motility (Security Week) Patchwork APT: Leveraging PowerShell to Create Scheduled Tasks and Deploy Final Payload (GB Hackers) GOP senator confirms pending White House quantum push, touts legislative alternatives (CyberScoop) Bitcoin Fixer Convicted for Role in Money Laundering Scheme (Bank Infosecurity) Nursing Home Fined $182K for Posting Patient Photos Online (Bank Infosecurity) 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? You too can reach the most influential leaders and operators in the industry. Here's our media kit. Contact us at cyberwire@n2k.com to request more info. 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
© 2020-2026 Ivy Podcast Discovery LLC
