Podcasts about hpe

Raghu Bala is the CEO and Founder of Synergetics AI, a firm helping enterprises design and deploy agentic AI systems to drive growth, operational efficiency, and lasting competitive advantage. A serial entrepreneur with four startup exits, he has led Synergetics AI in developing cutting-edge solutions in autonomous and agentic AI, collaborating with organizations like MIT and HPE. Raghu previously held senior roles at Yahoo, InfoSpace, and PwC and holds degrees from The Wharton School and Stanford University. In this episode… Imagine a world where your digital twin shops for you, makes payments, and even negotiates on your behalf. Could AI agents transform both businesses and daily life by bringing seamless automation, security, and personalization? How are innovators building the infrastructure for this future? Raghu Bala, a seasoned entrepreneur and AI innovator, explains that agentic AI is redefining how enterprises and consumers interact with technology. He highlights that AI agents — autonomous digital entities — can automate workflows, manage transactions, and act independently across complex systems. With tools like LangTrain, AgentFlow, and AgentVM, these agents enable secure, efficient operations while paving the way for the agent economy. Raghu explains practical applications, from digital twins automating e-commerce purchases to AI supporting real-time addiction counseling in healthcare, illustrating how these systems can streamline tasks and unlock new opportunities. In this episode of the Inspired Insider Podcast, host Dr. Jeremy Weisz sits down with Raghu Bala, CEO and Founder of Synergetics AI, to discuss building the agent economy, the evolution of autonomous AI, and the integration of digital twins in business. They explore secure AI workflows, real-world applications across industries, and the future of agent-driven commerce. Raghu also shares his favorite productivity tools and insights on aligning technology with company culture.

How can technology be used in the fight against modern slavery? This week, Technology Now is exploring the impact of modern slavery and how technology can be used to try and reduce it. We ask what the scale of the problem is today, we examine what modern slavery can look like, and we discuss how organisations and consumers can work together to try and combat this practice. John Schultz, Executive Vice President, Chief Legal and Administrative Officer and Corporate Secretary for HPE, tells us more.This is Technology Now, a weekly show from Hewlett Packard Enterprise. Every week, hosts Michael Bird and Sam Jarrell look at a story that's been making headlines, take a look at the technology behind it, and explain why it matters to organizations.About John:https://www.hpe.com/uk/en/leadership-bios/john-schultz.htmlSources https://www.hpe.com/us/en/newsroom/blog-post/2025/12/when-good-intentions-are-not-enough-the-importance-of-data-and-ai-in-solving-the-modern-slavery-epidemic.htmlhttps://www.hpe.com/uk/en/leadership-bios/john-schultz.html

Carole a toujours adoré les enfants, elle s'imaginait en mère adoptive mais c'est finalement en tombant enceinte qu'elle devient maman. Dès le premier essai bébé. Alors elle doit jongler entre le lancement de son entreprise et une grossesse pleine de rebondissements.Quant à l'accouchement, comme souvent, rien ne se passe comme prévu. Mais dans cet épisode on s'intéresse aussi aux années d'après l'arrivée de son fils. Toutes ces années durant lesquelles il ne dort pas, pleure chaque nuit, et Carole épuisée, pleure souvent aussi.Elle comprend au fil des années que son fils a une atypie, une hypersensibilité et pense alors au HPI, HPE ou d'autres lettres dont on parle de plus en plus. Mais après des années d'errance, des années à se sentir seule ou en décalage avec les avis des autres, le diagnostic tombe enfin : son fils a un trouble du spectre autistique TSA de niveau 2.Bonne écoute !----------------------------------------------Vous aimez le podcast HelloMammas ? Mettez ⭐⭐⭐⭐⭐ — sur Apple Podcast, Spotify ou Deezer ça nous aide énormément et abonnez-vous gratuitement sur votre plateforme d'écoute préférée pour ne manquer aucun épisode !On se retrouve chaque mardi pour un nouvel épisode

Special Envoy Steve Witkoff on the latest negotiations with Iran. Making headlines about how close Iran was the obtaining a nuclear weapon and why the U.S. decided to strike when it did. What he thinks peace in the Middle East could look like. Plus, the CEO of HPE with his first interview since reporting results. Predicting price pressures on memory to persist into next year. And could Nvidia be looking to get into software? That story, this hour. Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

Summary In this episode of Chattinn Cyber, Marc Schein is chattin' with Mike Armistead, a seasoned cybersecurity expert with over 40 years of experience, including more than 20 years as a vendor in the cybersecurity space. The conversation opens with a discussion about the challenges security leaders face in 2026. Mike highlights the complexity of their role, comparing it to that of a CFO managing financial risk, but notes that cybersecurity leaders often lack the comprehensive management tools that CFOs have. He emphasizes the fragmented nature of cybersecurity tools and the difficulty in stitching together disparate signals to form a coherent security posture. Mike further explains that the human element is the critical glue in cybersecurity programs. The effectiveness of security teams depends heavily on the leadership and the ability of individuals to contextualize technical signals within the business environment. This need for situational awareness is driving interest in AI technologies, particularly on the defender side, to augment human capabilities and expand the scope and depth of security operations. The chat then shifts to the role of AI in cybersecurity products. Mike observes that while AI is increasingly integrated into detection tools, the industry has largely shifted focus away from prevention. He advocates for a strategic return to prevention, where AI can play a significant role in helping security leaders develop and implement risk mitigation strategies tailored to their organizations. Mike stresses the importance of a holistic approach that goes beyond real-time detection to include employee training, access control, and disaster recovery. Addressing the challenges faced by middle-market organizations, Mike points out that these companies are often expected to meet the same cybersecurity standards as large enterprises but with far fewer resources. He advises middle-market CISOs to prioritize protecting their most critical assets—their “crown jewels”—and to have candid conversations with leadership about realistic security goals. This pragmatic approach helps ensure that limited resources are focused on the highest risks rather than attempting to cover every possible threat. Finally, Mike shares information about a community he helped start called the Security Impact Circle, which focuses on cybersecurity leadership issues such as board engagement. This community facilitates workshops that bring together CSOs and board directors to bridge the communication gap and align security priorities with business needs. Mike encourages listeners to visit securityimpactcircle.org to learn more and get involved. Five Key Points Covered Cybersecurity leaders face complex challenges similar to CFOs but lack equivalent management tools. Human expertise is essential to contextualize technical security signals within the business environment. AI is increasingly used in detection but should also be leveraged to enhance prevention strategies. Middle-market organizations must prioritize protecting their most critical assets due to limited resources. The Security Impact Circle community helps improve communication and alignment between security leaders and boards. Five Key Quotes from the Conversation “Security leaders have a tough job… it's not unlike what a CFO has to think about, right? That risk happens to be financial, and the CISOs really happens to be in cyber.” “The security teams are really bound by how good not only their leader, but the deputies, the managers, the architects, those individual contributors that really help lead it.” “I think the opportunity is to swing it back to prevention… AI can really start to help on the prevention strategy side of cybersecurity.” “Middle-market leaders are expected to do everything that the largest enterprises do, but they don't have the resources to cover all the ground.” “We bring in a director from a public company's audit committee to run workshops… it's less about what a CSO thinks they should say and more about what the director thinks they need to hear.” About Our Guest Mike Armistead brings nearly 40 years of business experience marked by a proven track record of building companies, navigating strategic acquisitions, and leading growth at every stage. As co-founder and CEO of Respond Software, acquired by Mandiant for $200 million, and co-founder of Fortify Software, acquired by HP for $285 million, Mike has played pivotal roles in multiple successful startups, including serving as SVP on the turnaround team at WhoWhere (acquired by Lycos for $133 million) and contributing to Pure Software's IPO. His post-acquisition leadership includes key roles as VP of Products & UX at Mandiant, Director at Google Cloud, and VP & GM for Fortify and ArcSight business groups at HPE, where he drove significant expansion and over $400 million in revenue impact. Alongside these successes, Mike gained valuable insights from two brief ventures, including leading InLeague through post-9/11 financial challenges and emphasizing product-market fit in another startup. Beginning his career as a Product Manager at HP in the late 1980s, Mike's multifaceted experience spans diverse industries and company sizes. Today, he remains passionate about building high-performing teams and tackling complex, noble challenges. Follow Our Guest LinkedIn About Our Host National co-chair of the Cyber Center for Excellence, Marc Schein, CIC,CLCS is also a Risk Management Consultant at Marsh McLennan Agency. He assists clients by customizing comprehensive commercial insurance programs that minimize the burden of financial loss through cost effective transfer of risk. By conducting a Total Cost of Risk (TCoR) assessment, he can determine any gaps in coverage. As part of an effective risk management insurance team, Marc collaborates with senior risk consultants, certified insurance counselors, and expert underwriters to examine the adequacy of existing client programs and develop customized solutions to transfer risk, improve coverage and minimize premiums. Follow Our Host Website | LinkedIn  

Markets respond to fast moving geopolitical headlines and fresh swings in energy. Oil dominates the market conversation. Pippa Stevens tracks price moves while Helima Croft, Global Head of Commodity Strategy at RBC Capital Markets, breaks down supply risks, geopolitical crosscurrents and what it would take for crude to move higher or stabilize. Matt Stucky of Northwestern Mutual Wealth Management and Anastasia Amoroso of Partners Group assess the broader market setup and debate how investors should position amid volatility. Earnings from HPE add another data point for tech. Jason Furman, former Chair of the Council of Economic Advisers, weighs in on the Fed and the economic outlook. Dan Levy of Barclays explains how higher oil prices could ripple through the auto sector. Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

Carole est la maman d'un petit garçon de six ans et elle comprend au fil des années que son fils a une atypie, une hypersensibilité et pense alors au HPI, HPE ou d'autres lettres dont on parle de plus en plus.. Toutes ces années durant lesquelles il ne dort pas, pleure chaque nuit, et Carole épuisée, pleure souvent aussi.Mais après des années d'errance, des années à se sentir seule ou en décalage avec les avis des autres, le diagnostic tombe enfin.À demain pour découvrir l'épisode dans son intégralité !----------------------------------------------Vous aimez le podcast HelloMammas ? Mettez ⭐⭐⭐⭐⭐ — sur Apple Podcast, Spotify ou Deezer ça nous aide énormément et abonnez-vous gratuitement sur votre plateforme d'écoute préférée pour ne manquer aucun épisode !On se retrouve chaque mardi pour un nouvel épisode

What's happening at Mobile World Congress Barcelona 2026? This week, Technology Now is on the ground in Barcelona at the 20th Mobile World Congress to delve deeper into the future of networking. We ask what are the big themes of this year's Mobile World Congress, we explore why events like this are important to organisations like HPE, and we examine why consumers should care about events like this. Rami Rahim, President and General Manager, HPE Networking tells us more.This is Technology Now, a weekly show from Hewlett Packard Enterprise. Every week, hosts Michael Bird and Sam Jarrell look at a story that's been making headlines, take a look at the technology behind it, and explain why it matters to organizations. This episode is available in both video and audio formats.About Rami:https://www.hpe.com/uk/en/leadership-bios/rami-rahim.html

Intersect 360 Research CEO Addison Snell talks in depth about the AI innovations powering the Genesis Mission with Assc. Laboratory Director Gina Tourassi from the Oak Ridge National Laboratory. Sponsored by HPE and AMD.

Where does Executive Greatness come from? By helping executives, founders, and leadership teams communicate with conviction, clarity, and presence.Ash is the Founder & CEO of the Executive Greatness Institute, where he has coached leaders at Cisco, Uber, Google, HPE, and Sprinklr to deliver powerful strategic narratives and keynote talks that inspire teams, boards, and customers.He has also founded the Duh AI company, an incubator for AI-driven ventures.The common thread across Ash's ventures and advisory work is conviction: the belief that when leaders communicate with purpose, people follow with energy and commitment. So, whether he is coaching executives, advising on digital transformation, or building AI platforms, his mission is to help people and organisations find their voice, tell their story, and realise their boldest ambitions.Summary of PodcastIntroductions and BanterThe meeting begins with casual conversation as the participants introduce themselves and discuss topics like virtual backgrounds, lighting issues, and health concerns. They establish a relaxed, conversational tone.Executive Presence and CommunicationThe discussion turns to the importance of executive presence and effective communication. Ash Seddeek shares his expertise in helping leaders craft and deliver impactful messages tailored to their audience. He emphasises the need for energy, storytelling, and adapting the delivery style.Investor Pitches and Audience AdaptationThe group delves into the nuances of delivering effective investor pitches. Ash explains the importance of understanding the investors' perspectives and crafting the message accordingly, versus a more general employee communication. He highlights the need to build trust and excitement.The Role of AI in CommunicationThe conversation explores the potential impact of AI on communication and presentation. Ash and the hosts discuss the balance between AI-powered tools and the value of human expertise, presence, and the ability to provide honest, trusted feedback.Wrap-up and ReflectionsThe meeting concludes with the hosts and Ash reflecting on the key takeaways from the discussion, including the importance of energy, audience adaptation, and the evolving role of technology in communication. They express gratitude for the insightful conversation.The Next 100 Days Podcast Co-HostsGraham ArrowsmithGraham founded Finely Fettled in 2014 to provide data from The UK High Net Worth Database to marketers targeting affluent and high-net-worth customers. He's the founder of MicroYES, a Partner for MeclabsAI, creating lead generation AI Agents & Workflows and introducing the MeclabsAI Platform. Graham also provides an Answer Engine Optimisation solution to get your website in shape to be found by LLMs.Kevin Appleby Kevin specialises in finance transformation and implementing business change. He's the COO of GrowCFO, which provides both community and CPD-accredited training designed to grow the next generation of finance leaders. You can find Kevin on LinkedIn and at kevinappleby.com

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

How has the idea of ethics been affected by the rise of AI? This week, Technology Now is exploring the ideas of ethical and responsible AI. We examine how integrated into society AI has become, we ask how we co-exist with AI, and we look into how regular people, organisations, and governments are having to respond to the increasing adoption of AI. Kay Firth-Butterfield, CEO of Good Tech Advisory LLC and the world's first Chief AI Ethics Officer, tells us more.This is Technology Now, a weekly show from Hewlett Packard Enterprise. Every week, hosts Michael Bird and Sam Jarrell look at a story that's been making headlines, take a look at the technology behind it, and explain why it matters to organizations. This episode is available in both video and audio formats.About Kay: https://kayfirthbutterfield.comSources:https://www.bbc.co.uk/news/business-66807456https://www.bbc.co.uk/news/world-us-canada-65735769https://www.bbc.co.uk/news/articles/cq808px90wxohttps://www.npr.org/2025/05/07/g-s1-64640/ai-impact-statement-murder-victimhttps://www.academia.edu/123541578/The_Clinical_Chemist

In questo episodio esploriamo come la tecnologia ha abilitato le Olimpiadi, l'importanza cruciale della qualità semantica dei dati e come le aziende possono oggi scalare la competitività internazionale attraverso strumenti innovativi di Ricerca e Sviluppo.

How does a quantum computer work? This week, Technology Now is diving into the world of quantum computing. We delve into how quantum computers work, we explore what's needed to build them and we ask what we should expect from this field of research in the future. Dr Michaela Eichinger, Product Solutions Physicist at Quantum Machines, tells us more.This is Technology Now, a weekly show from Hewlett Packard Enterprise. Every week, hosts Michael Bird and Sam Jarrell look at a story that's been making headlines, take a look at the technology behind it, and explain why it matters to organizations. This episode is available in both video and audio formats.About Michaela: https://www.linkedin.com/in/michaela-eichinger/?originalSubdomain=chSourceshttps://blog.sciencemuseum.org.uk/quantum-computing-what-who-how-and-when/https://www.nobelprize.org/prizes/physics/2025/press-release/#:~:text=Their%20experiments%20on%20a%20chip,passed%20a%20current%20through%20it.https://www.britannica.com/science/zero-point-energyhttps://www.space.com/how-cold-is-spaceK.W. Taconis, Dilution refrigeration, Cryogenics, Volume 18, Issue 8, 1978, Pages 459-464, ISSN 0011-2275, https://doi.org/10.1016/0011-2275(78)90204-7., (https://www.sciencedirect.com/science/article/pii/001122757890204

How is AI changing the way we store data? This week Technology Now dives into the topic of data storage in the world of AI. We explore intelligent storage, how data sovereignty is influencing how we store our data, and consider where the world of storage could be going in the future. Jim O'Dorisio, Senior Vice President and General Manager HPE Storage, tells us more.This is Technology Now, a weekly show from Hewlett Packard Enterprise. Every week, hosts Michael Bird and Sam Jarrell look at a story that's been making headlines, take a look at the technology behind it, and explain why it matters to organizations.About Jim:https://www.linkedin.com/in/odorisiojim/Sources:https://www.statista.com/statistics/871513/worldwide-data-created/#statisticContainerhttps://www.studionetworksolutions.com/how-much-data-is-used-and-stored-in-the-world/#:~:text=expanding%20digital%20universe.-,Global%20Data%20Usage,over%20180%20zettabytes%20by%202025.1 billion terrabytes in 1 zettabyte. If a smartphone has 1Tb storage, then you need 180 billion smartphones to make 180Zb of storage. 180 billion > 100 billionhttps://www.computerhistory.org/timeline/memory-storage/https://www.computerhistory.org/revolution/memory-storage/8/308https://www.computinghistory.org.uk/det/6129/https://www.computerhistory.org/revolution/memory-storage/8/308/963

I am happy to welcome you to the inaugural podcast keynote! This is the official episode 400, so if you're listening to this in February there are 399 episodes to scroll beneath this one. I wanted to mark the 400th episode with something--- in episode 200 we had a town hall and it went really well. I am not sure where this will go on Laura's CV, but I am really happy she accepted the invitation to make something new and to be creative with me on this podcast! Dr. Laura Alfrey –is an associate professor at Monash University in Australia her research interests are in HPE and the ways which policy, professional learning and practice contribute to inclusive and educative experiences for everyone. Today she will share her innovative research in fitness testing…. But beyond publishing copious articles, getting cited hundreds of times a year for her work- Laura also serves the field by being on the Editorial Board for Curriculum Studies in HPE, Sport Education and Society, and the Journal of Teaching in Physical Education…AND MANY MORE!This podcast keynote is about fitness testing in PE, from an Australian lens, with a few notes about the American context, and some commentary by US based researchers as well. Here is a link to the video Laura showed: https://www.youtube.com/watch?v=VcH_IErqIXMThis is the article Chuck noted in his comment: Charles B. “Chuck” Corbin (2026)National Youth Fitness Tests and Awards: Dispelling Misconceptions andMisinformation, Journal of Physical Education, Recreation & Dance, 97:1,3-5, DOI: 10.1080/07303084.2025.2579444 To link to this article:https://doi.org/10.1080/07303084.2025.2579444

How are hospitals using AI and HPC to assist them in helping save lives? This week, Technology Now is joined by Keith Perry, Senior Vice President and Chief Information Officer at St. Jude Children's Research Hospital to explore how St Jude uses the latest technologies to help treat and prevent illness and catastrophic disease, giving patients and families more time, and more hope, when it comes to diagnosis.This is Technology Now, a weekly show from Hewlett Packard Enterprise. Every week, hosts Michael Bird and Sam Jarrell look at a story that's been making headlines, take a look at the technology behind it, and explain why it matters to organizations.About Keith:https://www.linkedin.com/in/keith-perry-8562347/Sources:Hernigou P. Ambroise Paré III: Paré's contributions to surgical instruments and surgical instruments at the time of Ambroise Paré. Int Orthop. 2013 May;37(5):975-80. doi: 10.1007/s00264-013-1872-y. Epub 2013 Apr 12. PMID: 23580029; PMCID: PMC3631503.https://www.surgicalholdings.co.uk/history-of-surgical-instruments.htmlSmith-Bindman R, Kwan ML, Marlow EC, et al. Trends in Use of Medical Imaging in US Health Care Systems and in Ontario, Canada, 2000-2016. JAMA. 2019;322(9):843–856. doi:10.1001/jama.2019.11456https://caferoentgen.com/2023/10/07/a-tale-of-two-hands-the-story-behind-the-two-famous-radiographs-captured-by-wilhelm-roentgen/https://www.orau.org/health-physics-museum/collection/shoe-fitting-fluoroscope/index.html

Modern ABM is not a channel or a quick win. In this episode of the OnBase podcast, Paul Gibson sits down with Katie Skene, Senior ABM Manager at Global Relay, to explore what modern account-based marketing really takes to succeed. They discuss why account selection is the foundation of ABM, how sales and marketing alignment drives long-term impact, where AI and intent signals can go wrong, and why curiosity is becoming the defining skill for ABM leaders. If you are trying to scale ABM, overcome internal resistance, or move from theory to execution, this episode offers practical insight from the front lines.About the GuestKatie Skene is a B2B marketing professional with 14 years of experience across agency and in-house roles. She began her career in marketing at a US medical devices company before spending a decade in agencies, where she built expertise across marketing automation, paid media, and multi-channel campaign execution, alongside commercial responsibility for pipeline and revenue.Specialising in B2B technology, Katie has worked with global brands including Adobe, HPE, Capgemini, and Fujitsu. Account-based marketing has been a consistent focus throughout her career, and her time at Agent3, now Pretzel, working within ABM centres of excellence cemented her passion for aligning marketing, technology, and sales to drive meaningful growth.Connect with Katie.

What topics have to be considered while discussing AI? This week, Technology Now is returning to Davos, Switzerland, dive deeper into the topics surrounding the AI revolution. We ask how sovereignty in AI is linked to trust and explore how sustainability both impacts, and is impacted by sovereignty within the industry. Kirk Bresniker, chief architect of HPE Labs, tells us more.This is Technology Now, a weekly show from Hewlett Packard Enterprise. Every week, hosts Michael Bird and Sam Jarrell look at a story that's been making headlines, take a look at the technology behind it, and explain why it matters to organizations. This episode is available in both video and audio formats.About Kirk: https://www.linkedin.com/in/kirkbresniker/

What are HPE doing at Davos? This week, Technology Now is heading to the World Economic Forum Annual Meeting in Davos, Switzerland to talk to HPE CEO and President Antonio Neri about the topics which are currently captivating business and world leaders. We explore what's changed since last year, why people are focusing on AI and trust, and why quantum has emerged, again, as a topic of interest.This is Technology Now, a weekly show from Hewlett Packard Enterprise. Every week, hosts Michael Bird and Sam Jarrell look at a story that's been making headlines, take a look at the technology behind it, and explain why it matters to organizations. This episode is available in both video and audio formats.Video podcast: https://www.youtube.com/watch?v=DxgUswwHsLg&list=PLtS6YX0YOX4c12MoKvNgYw6zwNogLW3E7&index=1&pp=iAQB

Last week, Taiwan Semiconductor (NYSE: TM) put up stellar fourth-quarter numbers, signaling that we've yet to reach peak AI demand. Are we in for another banner year in 2026? Jason Hall, Travis Hoium, and Tim Beyers discuss: - TSM's spectacular Q4 and capex spending plan. - Which company tops the AI value chain: TSM or NVDA. - Good corporate citizens in a nod to companies that exhibit the values espoused by Dr. Martin Luther King Jr., whom we honor today. Don't wait! Be sure to get to your local bookstore and pick up a copy of David's Gardner's new book — Rule Breaker Investing: How to Pick the Best Stocks of the Future and Build Lasting Wealth. It's on shelves now; get it before it's gone! Tickers: Companies discussed: TSM, NVDA, SBGSY, HPE, HPQ Host: Tim Beyers Guests: Jason Hall, Travis Hoium Producer: Anand Chokkavelu Engineer: Dan Boyd Learn more about your ad choices. Visit megaphone.fm/adchoices

Data centers are still the headline, but the real pinch points are power and real estate. Emily Flippen is joined by Motley Fool analysts Anders Bylund and Dan Caplinger to map the data center buildout, the risks of “overbuild,” and where investors can look for exposure without paying bubble prices. Companies discussed: MSFT, AMZN, NEE, GOOGL, HPE, AAON, STRL, DLR, FIX, EME, AMT, EQIX, IRM, STN, SBGSY Host: Emily Flippen, Dan Caplinger, Anders Bylund Producer: Anand Chokkavelu Engineer: Dan Boyd Disclosure: Advertisements are sponsored content and provided for informational purposes only. The Motley Fool and its affiliates (collectively, “TMF”) do not endorse, recommend, or verify the accuracy or completeness of the statements made within advertisements. TMF is not involved in the offer, sale, or solicitation of any securities advertised herein and makes no representations regarding the suitability, or risks associated with any investment opportunity presented. Investors should conduct their own due diligence and consult with legal, tax, and financial advisors before making any investment decisions. TMF assumes no responsibility for any losses or damages arising from this advertisement. We're committed to transparency: All personal opinions in advertisements from Fools are their own. The product advertised in this episode was loaned to TMF and was returned after a test period or the product advertised in this episode was purchased by TMF. Advertiser has paid for the sponsorship of this episode. Learn more about your ad choices. Visit ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠megaphone.fm/adchoices Learn more about your ad choices. Visit megaphone.fm/adchoices

Innovation comes in many forms, and compliance professionals need not only to be ready for it but also to embrace it. Join Tom Fox, the Voice of Compliance, as he visits with top innovative minds, thinkers, and creators in the award-winning #InnovationinCompliance podcast. In this episode, host Tom Fox welcomes Angie McPhail to discuss the transformation of compliance from a regulatory function to a strategic business imperative. Angie shares her professional background, having led the Integrity and Compliance group for the Americas at Juniper Networks before its acquisition by HPE. Key discussions include the evolving role of compliance as a strategic influencer within organizations, the intersection of ethics and integrity with ESG, and the importance of trust in building effective compliance programs. Angie emphasizes the need for compliance professionals to understand business strategy, leverage technology, and build trust to drive sustainable growth. The talk also covers the future outlook for compliance leaders and provides advice on preparing the next generation of compliance professionals. Key highlights: Compliance as a Strategic Business Function Influence and Trust in Compliance Compliance as a Driver of Business Success Managing Reputational Risk Future of Compliance Leadership Resources: Angie McPhail on LinkedIn Innovation in Compliance was recently ranked 4th among Risk Management podcasts by 1,000,000 Podcasts.

How are our networks designed to cope with the increasing demands of AI? This week, Technology Now dives into the topic of networking for AI, exploring how our networks have adapted and evolved to meet the ever growing demands of modern day AI infrastructure. Praful Lalchandani,VP of Networking Product Management, tells us more.This is Technology Now, a weekly show from Hewlett Packard Enterprise. Every week, hosts Michael Bird and Sam Jarrell look at a story that's been making headlines, take a look at the technology behind it, and explain why it matters to organizations.About Praful: https://www.linkedin.com/in/prafullalchandani/Sources:https://www.networkworld.com/article/972044/ethernet-at-50-bob-metcalfe-pulls-down-the-turing-award.htmlhttps://www.networkworld.com/article/970970/what-is-ethernet.htmlhttps://computer.howstuffworks.com/ethernet5.htm

Send us a textThe year felt like it stretched on forever, and in that extra space the networking world reshaped itself. We traded weekly cadence for deeper focus, shipped an AWS Advanced Networking book that the community embraced, and then watched the landscape pivot as vendors consolidated, clouds connected to each other, and AI hype met the hard edges of security and reliability.We dig into the acquisition wave with clear eyes: Arista picking up VeloCloud from Broadcom and what that means for SD‑WAN customers; HPE's Juniper deal clearing regulatory review and the open questions around Mist and portfolio strategy; and why Broadcom–VMware didn't trigger instant mass migrations, even as budgets and CSP support shifted. Then we chart the most surprising turn—AWS and Google offering a cross‑cloud link that's not a one‑off database play, but a general connective fabric. If pricing trends toward pipe capacity rather than per‑GB egress, multi‑cloud networking stops being a niche product pitch and becomes an operator reality. We even explore the idea of a Cloud Exchange Point, where automation snaps providers together at scale.AI was everywhere and still uneven. We call out real wins—friendlier automation workflows and eBPF‑powered visibility via Cisco's Isovalent acquisition—while laying out the unsolved work: agentic AI with least privilege, auditable actions, and enforceable data boundaries. Until those controls are standard, enterprises will limit autonomy and keep AI close to expert hands. Against the constant layoff drumbeat, we offer direct advice: build skills across cloud interconnects, Kubernetes networking, and eBPF telemetry; document outcomes in the language of cost and risk; and lean into community for opportunities and perspective.If you want a no‑nonsense guide to what changed, what actually matters, and how to prepare for a faster 2026, this one's for you. Subscribe, share with a teammate who needs signal over noise, and drop your take: which shift will shape your architecture next year?Purchase Chris and Tim's book on AWS Cloud Networking: https://www.amazon.com/Certified-Advanced-Networking-Certification-certification/dp/1835080839/ Check out the Monthly Cloud Networking Newshttps://docs.google.com/document/d/1fkBWCGwXDUX9OfZ9_MvSVup8tJJzJeqrauaE6VPT2b0/Visit our website and subscribe: https://www.cables2clouds.com/Follow us on BlueSky: https://bsky.app/profile/cables2clouds.comFollow us on YouTube: https://www.youtube.com/@cables2clouds/Follow us on TikTok: https://www.tiktok.com/@cables2cloudsMerch Store: https://store.cables2clouds.com/Join the Discord Study group: https://artofneteng.com/iaatj

Send us a textDr. Brandon Crawford sits down with Bill, Meghan, and Theo Longhenry to share the miraculous journey of their daughter, Millie, who was born with alobar holoprosencephaly (HPE)—a severe, often fatal brain malformation. Despite being placed on hospice and told she had no hope of development, Millie's life is a living testament to the convergence of faith, neuroplasticity, and regenerative medicine.The Longhenry family offers a raw, faith-fueled perspective on confronting an impossible diagnosis. They recount the emotional trauma of being told by medical experts to "take her home and prepare for her to die" and the subsequent decision to reject a "comfort-only" path, choosing instead to pursue aggressive, unconventional healing methods. The conversation highlights the foundational role of faith, particularly the family's reliance on Psalm 23, which Millie visibly responds to with profound joy.Products 528 Innovations Lasers NeuroSolution Full Spectrum CBD NeuroSolution Broad Spectrum CBD NeuroSolution Stimpod STEMREGEN® Learn MoreFor more information, resources, and podcast episodes, visit https://tinyurl.com/3ppwdfpm

What is Spaceborne Lunar? This week, Technology Now explore how, and why, you would put a supercomputer on the moon. We ask why anyone would want to put a supercomputer on the moon, we discover how one would go about doing such a thing, and we explore the benefits that this sort of extreme edge computing could bring. Norm Follett, Senior Director, HPE Global Technical Marketing, Space Technologies & Solutions, tells us more.This is Technology Now, a weekly show from Hewlett Packard Enterprise. Every week, hosts Michael Bird and Sam Jarrell look at a story that's been making headlines, take a look at the technology behind it, and explain why it matters to organizations. This episode is available in both video and audio formats.About Norm: https://www.linkedin.com/in/normfollett/Sources:https://www.hpe.com/us/en/newsroom/accelerating-space-exploration-with-the-spaceborne-computer.htmlhttps://spectrum.ieee.org/software-as-hardware-apollos-rope-memoryhttps://www.bcs.org/articles-opinion-and-research/the-first-computers-on-the-moon/https://www.sciencefocus.com/space/what-tech-would-the-apollo-11-mission-have-todayhttps://www.bbc.co.uk/future/article/20230516-apollo-how-moon-missions-changed-the-modern-worldAverill C., 2022, a Brief Analysis of the Apollo Guidance Computer, https://doi.org/10.48550/arXiv.2201.08230

2025 was a year of seismic shifts in tech, as AI surged into a critical growth phase with massive investments, partnerships, and global trade battles over chips. Intel and HPE restructured for the AI era, quantum computing made strides with Microsoft, Google, and Cisco advancing real-world applications, and cloud giants struck multibillion-dollar deals. Meanwhile, strategic acquisitions reshaped the landscape—Lenovo, SoftBank, Google, Qualcomm, Anthropic, and more strengthened AI, cloud, cybersecurity, and quantum capabilities—highlighting a year defined by scale, innovation, and high-stakes competition across the technology ecosystem.Time Stamps0:00 - Cold Open0:17 - Welcome to the Tech Field Day News Rundown 1:09 - AI is at an Inflection Point, Who Really Controls its Future?4:58 - Intel at a Crossroads: Layoffs, Leadership Change, and the Fight to Stay Relevant in AI9:31 - The Internet Is More Fragile Than You Think14:33 - HPE Under Pressure and on the Move20:39 - The Global AI Trade War Heats Up27:10 - Quantum Computing Is Moving From Hype to High Stakes30:55 - Cloud Wars Heat Up as Tech Giants Expand AI Infrastructure33:33 - Billion-Dollar Deals Changing and Redefining the Future of AI and Cloud37:53 - Upcoming Tech Field Day Events in 202643:30 - Thank You to our Guest Cohosts in 202545:27 - Thanks for Watching the Tech Field Day News RundownFollow our hosts ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Tom Hollingsworth⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠, ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Alastair Cooke⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠, and ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Stephen Foskett⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠. Follow Tech Field Day ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠on LinkedIn⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠, on ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠X/Twitter⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠, on ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Bluesky⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠, and on ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Mastodon⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠.

Ireland's ambitions to strengthen female leadership across its technology sector have taken a leap forward with the launch of NOVA - Women in Tech Leadership Programme, designed specifically for the top tier of emerging female tech leaders. Created by Technology Ireland Digital Skillnet in partnership with Connecting Women in Tech (CWIT), NOVA will focus on combining human-centred leadership with the advanced strategic technology and AI-enabled capabilities expected of senior tech leaders in the years ahead. For the Technology Ireland Digital Skillnet, the NOVA programme builds on a decade of impact on women in the technology sector, through its multi award winning women tech returner programmes, bringing over 900 women back to the tech sector, and impacting on gender balance across the sector. The initiative will see over 20 professionals from 25 CWIT member companies advance their leadership journey when the first cohort commences in January. Máire Hunt, Director of Technology Ireland Digital Skillnet, said: "As a sector we must continually find new ways to attract, retain and promote women. Particularly in the age of AI, women can be disproportionately affected. The NOVA programme is a high-performance accelerator specifically designed for women leaders who can shape the future of technology in an AI driven world. It equips participants not just to take a seat at the table, but to shape it." Women are often underrepresented in tech and AI leadership roles, which can influence how AI systems are developed and implemented. If AI systems are developed without diverse perspectives, they may perpetuate biases that disproportionately affect women. Una Fitzpatrick Director of Technology Ireland, said: "Women in Technology already excel in their technical domain. However, they are under-represented at more senior management positions. Companies across the sector are looking for a sector driven, development pathway that prepares female leaders to make an impact in an AI driven world." Technology Ireland Digital Skillnet partnered with CWIT for the pilot NOVA programme, which was formally launched on Friday last. Maire Hunt added: "CWIT exists to help women thrive in the tech industry, so they were a natural partner for the first NOVA programme." The inaugural intake in January includes 25 female leaders across domains such as cloud computing, cybersecurity, fintech, AI services, semiconductors, and enterprise technology. Companies such as Ergo, ADM, HPE, Workday, Kerry Group, ESB, Mastercard, Salesforce, BT, Accenture and Microsoft are represented. Commenting, Sabrina Staunton of Mastercard and CWIT, said: "CWIT exists due to the power of the network to attract, retain and promote females to thrive in the technology space in Ireland. We are excited to launch the first-of-its-kind development program to address the challenge of female talent retention across the Irish technology industry, through the power of partnerships built on our collective power to empower." NOVA includes modules on strategic thinking, future technologies, emotional intelligence, AI-enabled decision making, high-impact communication and personal leadership identity. Combining live workshops, one on one coaching and a leadership impact project, the NOVA programme blends in-person and virtual sessions, one on one coaching and practical insights. Held over a six-month period it is designed to build skills progressively and embed new leadership habits. Individual companies can also deliver the programme in-house for groups of female leaders. Version 1 is one example where the programme is contextualised for a fast-growing AI driven organisation. Ireland's technology sector employs more than 170,000 people across global multinationals, high-growth Irish companies and a vibrant start-up ecosystem. As businesses continue to adapt to AI-driven transformation, programmes such as NOVA that develop strategic awareness, adaptability and leadership presence will be in de...

They've created a “Google Translate” for the cloud, and it's changing everything. Today, we're talking to Brad Parks, CloudOps and Private Cloud Leader at HPE. We discuss how Morpheus is bringing cloud operating models to on-premises infrastructure, why hybrid cloud is an inevitability rather than a strategy for most enterprises, and how HPE is helping IT teams eliminate vendor lock-in while maintaining workload portability across any infrastructure. All of this right here, right now, on the Modern CTO Podcast!  To get learn more about HPE and Morpheus, check out their website here.

Corey Quinn reconnects with Keith Townsend, founder of The CTO Advisor, for a candid conversation about the massive gap between AI hype and enterprise reality. Keith shares why a biopharma company gave Microsoft Copilot a hard no, and why AI has genuinely 10x'd his personal productivity while Fortune 500 companies treat it like radioactive material. From building apps with Cursor to watching enterprises freeze in fear of being the next AI disaster in the news, Keith and Corey dig into why the tools transforming solo founders and small teams are dead on arrival in the enterprise, and what it'll actually take to bridge that gap.About Keith TownsendKeith Townsend is an enterprise technologist and founder of The Advisor Bench LLC, where he helps major IT vendors refine their go-to-market strategies through practitioner-driven insights from CIOs, CTOs, and enterprise architects. Known as “The CTO Advisor,” Keith blends deep expertise in IT infrastructure, AI, and cloud with a talent for translating complex technology into clear business strategy.With more than 20 years of experience, including roles as a systems engineer, enterprise architect, and PwC consultant, Keith has advised clients such as HPE, Google Cloud, Adobe, Intel, and AWS. His content series, 100 Days of AI and CloudEveryday.dev, provide practical, plainspoken guidance for IT leaders. A frequent speaker at VMware Explore, Interop, and Tech Field Day, Keith is a trusted voice on cloud and infrastructure transformation.Show Highlights(01:25) Life After the Futurum Group Acquisition(03:56) Building Apps You're Not Qualified to Build with Cursor(05:45)Creating an AI-Powered RSS Reader(09:01) Why AI is Great at Language But Not Intelligence(11:39) Are You Looking for Advice or Just Validation?(13:49) Why Startups Can Risk AI Disasters and AWS Can't(17:28) You Can't Outsource Responsibility(19:52) Business Users Are Scared of AI Too(23:00) LinkedIn's AI Writing Tool Misses the Point(26:42) Private AI is Starting to Look Appealing(29:00) Never Going Back to Pre-AI Development(34:27) AI for Jobs You'd Never Hire Someone to Do(39:09) Where to Find Keith and Closing ThoughtsLinksThe CTO Advisor:  https://thectoadvisor.comSponsor: https://www.sumologic.com/solutions/dojo-aihttps://wiz.io/crying-out-cloud

What's the current state of play in the world of networking? This week, Technology Now returns to HPE Discover Barcelona for a discussion with Rami Rahim, President and General Manager, HPE Networking. We ask why networking is so important, how it is possible to keep the world connected, and explore what networking will look like going into the future.This is Technology Now, a weekly show from Hewlett Packard Enterprise. Every week, hosts Michael Bird and Sam Jarrell look at a story that's been making headlines, take a look at the technology behind it, and explain why it matters to organizations. This episode is available in both video and audio formats.About Rami Rahim: https://www.hpe.com/uk/en/leadership-bios/rami-rahim.html

Take a Network Break! Our Red Alert calls out a dangerous vulnerability in the popular open-source React library. On the news front, HPE decides on a “both and” strategy for its two wireless portfolios and rolls out an option to let customers pick and choose among cross-platform features in Mist and Aruba Networking Central through... Read more »

Take a Network Break! Our Red Alert calls out a dangerous vulnerability in the popular open-source React library. On the news front, HPE decides on a “both and” strategy for its two wireless portfolios and rolls out an option to let customers pick and choose among cross-platform features in Mist and Aruba Networking Central through... Read more »

Take a Network Break! Our Red Alert calls out a dangerous vulnerability in the popular open-source React library. On the news front, HPE decides on a “both and” strategy for its two wireless portfolios and rolls out an option to let customers pick and choose among cross-platform features in Mist and Aruba Networking Central through... Read more »

Leaders today face climate havoc, geopolitical instability and a 'more chaotic form of globalization,' said David Miliband, the president and chief executive officer of humanitarian organization International Rescue Committee. On this recent Meet the Leader, he explains how leaders can navigate this more disordered world and an 'age of impunity' – a trend he's tracked for years where some seem less accountable to the power they yield. He explains the challenge he sees for leaders of all stripes in the near future, giving practical advice on how leaders can stay accountable to the big picture and better meet the moment to craft tactical strategies and drive cooperation for positive change.  This interview was recorded October 2025 in the World Economic Forum New York Office. About this episode: International Rescue Committee: https://help.rescue.org/ Related podcasts: What most people get wrong about progress: Harvard psychologist Steven Pinker Watch: https://www.youtube.com/watch?v=Y2IJjZs4E7A&t=51s Read: https://tinyurl.com/3smrwev9 We're 'losing the war' on modern slavery: What leaders can do - HPE's John Schultz Watch: https://www.youtube.com/watch?v=HlXggC3o08I&t=1s Read: https://tinyurl.com/488aupcn  

Dave Nicholson and Chris Wang break down Hewlett Packard Enterprise (HPE) earnings. The stock plummeted after the mixed report, temporarily becoming the biggest S&P 500 loser on the day. Dave talks about some of his takeaways from recent meetings with HPE executives. Chris puts the guidance in focus, noting that it is softer than expected.======== Schwab Network ========Empowering every investor and trader, every market day.Options involve risks and are not suitable for all investors. Before trading, read the Options Disclosure Document. http://bit.ly/2v9tH6DSubscribe to the Market Minute newsletter - https://schwabnetwork.com/subscribeDownload the iOS app - https://apps.apple.com/us/app/schwab-network/id1460719185Download the Amazon Fire Tv App - https://www.amazon.com/TD-Ameritrade-Network/dp/B07KRD76C7Watch on Sling - https://watch.sling.com/1/asset/191928615bd8d47686f94682aefaa007/watchWatch on Vizio - https://www.vizio.com/en/watchfreeplus-exploreWatch on DistroTV - https://www.distro.tv/live/schwab-network/Follow us on X – https://twitter.com/schwabnetworkFollow us on Facebook – https://www.facebook.com/schwabnetworkFollow us on LinkedIn - https://www.linkedin.com/company/schwab-network/About Schwab Network - https://schwabnetwork.com/about

Gartner placed them in the highest corner of their Magic Quadrant. Why is HPE leading their industry? Today, we're talking to Brian Gruttadauria, CTO of Hybrid Cloud at Hewlett Packard Enterprise. We discuss how agentic AI is transforming hybrid cloud infrastructure, why human-in-the-loop will remain critical for enterprise AI adoption, and how HPE went from 20% to 92% GitHub Copilot adoption in just over a year. All of this right here, right now, on the Modern CTO Podcast!  To get learn more about HPE, check out their website here.

What's going on at HPE Discover Barcelona 2025. This week, Technology Now visits Barcelona for an interview with company CEO Antonio Neri. We ask what the how the world of technology is faring a quarter of the way into the 21st century, we look forward to where we're heading in the future, and we explore how HPE is responding to our changing world.This is Technology Now, a weekly show from Hewlett Packard Enterprise. Every week, hosts Michael Bird and Sam Jarrell look at a story that's been making headlines, take a look at the technology behind it, and explain why it matters to organizations. This episode is available in both video and audio formats.http://www.hpe.com/discover/barcelona

Bob Friday, Chief AI Officer for HPE Networking, discusses how federal agencies are rethinking network modernization in the face of rising complexity, new security demands, and the accelerating influence of AI. Friday shares what he's hearing from federal IT leaders about their most urgent challenges—cloud migration hurdles, stringent security requirements like FedRAMP and FIPS, and the staffing constraints shaping today's modernization efforts. He also breaks down the technology trends driving HPE's approach, including the shift to real-time AI-ops, the organizational changes required to fully leverage agentic AI, and how HPE's acquisition of Juniper Networks strengthens the push toward a “self-driving network.”

Why put a supercomputer into orbit? This week, Technology Now concludes its mini-series by looking to space. We examine our final objects, Spaceborne computers one and two, as well as Spaceborne Lunar. We will explore why HPE are sending supercomputers to space, how they have to be adapted to exist off world, and where they will be travelling to next.This is Technology Now, a weekly show from Hewlett Packard Enterprise. Every week, hosts Michael Bird and Aubrey Lovell look at a story that's been making headlines, take a look at the technology behind it, and explain why it matters to organizations.More about Norm Follett: https://www.linkedin.com/in/normfollett/Sourceshttps://www.pwc.com.au/industry/space-industry/lunar-market-assessment-2021.pdf

As a global company, HPE's talent challenges are at the top of the funnel. We learn how they utilize unconventional channels and smart targeting to reach people where they already are. Rachel Duran is the Head of Global Employer Brand and Recruitment Marketing at Hewlett Packard Enterprise. Rachel Duran on LinkedIn: https://www.linkedin.com/in/rachelduran/ HPE Careers: https://careers.hpe.com/us/en Subscribe to this podcast: https://employerbrandingpodcast.com Measure your employer brand: https://employerbrandindex.co Thanks for tuning in!

How do networks keep our society running? This week, Technology Now continues with the third episode in its miniseries with a further three objects: the A52 WiFi 7, and Juniper access points. We dive into the birth of modern networking, the security and technology required for “bring your own device” connections, and the unexpected things a modern day WiFi router can detect. Stuart Strickland, Wireless Chief Technology Officer and HPE Fellow tells us more.This is Technology Now, a weekly show from Hewlett Packard Enterprise. Every week, hosts Michael Bird and Aubrey Lovell look at a story that's been making headlines, take a look at the technology behind it, and explain why it matters to organizations.About Stuart Strickland: https://www.hpe.com/psnow/doc/a00118725enw

storically tumultuous year for federal employees didn't dim the public's pre-shutdown view of government services, according to a new survey that largely credited tech adoption for the positive perceptions. The 2025 American Customer Satisfaction Index Federal Government Study, released Tuesday, found citizen satisfaction with federal government services at a 19-year high with a score of 70.4 on a 0-to-100 scale, a 1% jump from 2024. The survey of 6,914 randomly chosen respondents was conducted before the longest government shutdown in U.S. history, but ACSI's director of research emeritus emphasized that the results still “reflect real momentum in improving how citizens experience federal services.” Forrest Morgeson, an associate professor of marketing at Michigan State in addition to his role at ACSI, said that the introduction of AI is making a large impact, and such advancement “signal a future where government services can be more responsive and accessible to all.” Many of the highest-ranking federal agencies in customer satisfaction were lauded for their implementation of technologies, including USDA, the State Department and the Small Business Administration. The National Institutes of Health didn't ensure that the entity housing personal health information of over 1 million people — including biosamples — implemented proper cybersecurity protocols, according to an internal watchdog. In a report publicly released Friday, the Department of Health and Human Services' Office of Inspector General made five recommendations for the security of the All of Us program — a database of diverse health information from 1 million participants that's meant to aid research — after finding weaknesses. According to the report, while the award recipient operating the program's Data and Research Center implemented some cybersecurity measures, NIH failed to ensure other controls were addressed. The report found that NIH didn't ensure that the awardee, which wasn't identified, appropriately limited access to the program's data and didn't communicate national security concerns related to maintaining genomic data — or data relating to DNA. It also failed to ensure that weaknesses in security and privacy were fixed within a timeline outlined in federal requirements. The audit was initially conducted by the inspector general due to the threats that cyberattacks and the potential exposure of sensitive information can pose to the agency's programs. The watchdog's objective was to scrutinize the access, security and privacy controls of the program. Also in this episode: HPE Networking Chief AI Officer Bob Friday joins SNG host Wyatt Kash in a sponsored podcast discussion on how agencies can leverage cloud and AI to build more automated, secure and mission-ready networks. This segment was sponsored by HPE.

How has compute evolved to meet the changing demands of modern society? This week, Technology Now continues with its mini-series, exploring objects two, three and four: the HP35 calculator, the HP 65 calculator, and the ProLiant Gen 12 Server. We dive into this history of personal devices and computing, how compute has evolved over the years, and where the world of computing is going to go in the future. Kirk Bresniker, Chief Architect at HPE Labs, tells us more.This is Technology Now, a weekly show from Hewlett Packard Enterprise. Every week, hosts Michael Bird and Aubrey Lovell look at a story that's been making headlines, take a look at the technology behind it, and explain why it matters to organizations.About Kirk: https://www.linkedin.com/in/kirkbresniker

Today, we're joined by Robin Braun, VP of AI business development for hybrid cloud at HPE, and Luke Norris, co-founder and CEO of Kamiwaza, to discuss how AI systems can be used to automate complex workflows and unlock value from legacy enterprise data. Robin and Luke detail high-impact use cases from HPE and Kamiwaza's collaboration on an “Agentic Smart City” project for Vail, Colorado, including remediation and automation of website accessibility for 508 compliance, digitization and understanding of deed restrictions, and combining contextual information with camera feeds for fire detection and risk assessment. Additionally, we discuss the role of private cloud infrastructure in overcoming challenges like cost, data privacy, and compliance. Robin and Luke also share their lessons learned, including the importance of fresh data, and the value of a "mud puddle by mud puddle" approach in achieving practical AI wins. The complete show notes for this episode can be found at https://twimlai.com/go/755.

How did HPE and Disney form a relationship which has continued for over 80 years? This week, Technology Now begins a mini-series to celebrate the tenth birthday of HPE. In Episode one, we explore where it all began – with the sale of an oscillator to Disney in the ‘30s - and how that partnership has continued to this day through digitisation, the pandemic, and the current AI explosion.This is Technology Now, a weekly show from Hewlett Packard Enterprise. Every week, hosts Michael Bird and Aubrey Lovell look at a story that's been making headlines, take a look at the technology behind it, and explain why it matters to organizations.About Alice Taylor:https://www.linkedin.com/in/alicetaylor/Sourceshttps://www.computinghistory.org.uk/det/5011/HP-9826/https://www.hpe.com/nl/en/what-is/virtual-desktop.html https://www.imdb.com/list/ls093653710/https://www.flywing-tech.com/blog/a-1939-audio-oscillator-caught-disneys-eye-and-helped-launch-hp/ https://www.hewlettpackardhistory.com/item/a-deal-with-disney/ https://www.hpe.com/us/en/about/history/innovation-gallery/008-product.htmlhttps://www.thedisneyclassics.com/blog/animation-styles https://medium.com/cinemania/a-puppet-in-walt-disneys-hands-ea2d5b43ef96 

Happy Halloween, tech fam!

What is Chapel? This week, Technology Now explores the programming language, Chapel. We ask what it is, how it was designed, and we explore why people would use it instead of some of the more established languages.This is Technology Now, a weekly show from Hewlett Packard Enterprise. Every week, hosts Michael Bird and Aubrey Lovell look at a story that's been making headlines, take a look at the technology behind it, and explain why it matters to organizations.About Brad Chamberlain:https://www.linkedin.com/in/brad-chamberlain-3ab358105 Sourceshttps://www.britannica.com/biography/Ada-Lovelacehttps://www.adalovelaceinstitute.org/about/https://cdn.britannica.com/31/172531-050-E009D42C/portion-Charles-Babbage-Analytical-Engine-death-mill-1871.jpghttps://commons.wikimedia.org/wiki/File:PunchedCardsAnalyticalEngine.jpghttps://www.mpg.de/female-pioneers-of-science/Ada-Lovelace