Podcasts about VM

Join Richard Jefferson, Channing Frye, and Allie Clifton as they dive into another round of Truth or Trash on this episode of Road Trippin'. The dynamic duo discusses whether Steph Curry will secure his 5th championship, debates if NBA Jam is the greatest basketball game of all time, and analyzes which NBA franchise has the most upside for the future. The crew also laments the cancellation of HBO's "Winning Time", and wonders if another network should pick up the series. Have a question or topic for our next show? Text or leave us a VM at 657-522-5578 (6575-CALLRT) Cheers! ► YouTube!

On this episode, Nick Dais is joined by Josh Williams to talk about the Commanders 2-0 start, Bills invading Washington, A loser leaves town match in Minnesota this weekend, Are the Bucs going to 3-0 after MNF and a segment called "I've Seen Enough" THANK YOU LEGENDS FOR ALL THE SUPPORT ON THE PATREON THE LAST FEW WEEKS!

Steve Tuck, Co-Founder & CEO of Oxide Computer Company, joins Corey on Screaming in the Cloud to discuss his work to make modern computers cloud-friendly. Steve describes what it was like going through early investment rounds, and the difficult but important decision he and his co-founder made to build their own switch. Corey and Steve discuss the demand for on-prem computers that are built for cloud capability, and Steve reveals how Oxide approaches their product builds to ensure the masses can adopt their technology wherever they are. About SteveSteve is the Co-founder & CEO of Oxide Computer Company.  He previously was President & COO of Joyent, a cloud computing company acquired by Samsung.  Before that, he spent 10 years at Dell in a number of different roles. Links Referenced: Oxide Computer Company: https://oxide.computer/ On The Metal Podcast: https://oxide.computer/podcasts/on-the-metal TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: This episode is brought to us in part by our friends at RedHat. As your organization grows, so does the complexity of your IT resources. You need a flexible solution that lets you deploy, manage, and scale workloads throughout your entire ecosystem. The Red Hat Ansible Automation Platform simplifies the management of applications and services across your hybrid infrastructure with one platform. Look for it on the AWS Marketplace.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. You know, I often say it—but not usually on the show—that Screaming in the Cloud is a podcast about the business of cloud, which is intentionally overbroad so that I can talk about basically whatever the hell I want to with whoever the hell I'd like. Today's guest is, in some ways of thinking, about as far in the opposite direction from Cloud as it's possible to go and still be involved in the digital world. Steve Tuck is the CEO at Oxide Computer Company. You know, computers, the things we all pretend aren't underpinning those clouds out there that we all use and pay by the hour, gigabyte, second-month-pound or whatever it works out to. Steve, thank you for agreeing to come back on the show after a couple years, and once again suffer my slings and arrows.Steve: Much appreciated. Great to be here. It has been a while. I was looking back, I think three years. This was like, pre-pandemic, pre-interest rates, pre… Twitter going totally sideways.Corey: And I have to ask to start with that, it feels, on some level, like toward the start of the pandemic, when everything was flying high and we'd had low interest rates for a decade, that there was a lot of… well, lunacy lurking around in the industry, my own business saw it, too. It turns out that not giving a shit about the AWS bill is in fact a zero interest rate phenomenon. And with all that money or concentrated capital sloshing around, people decided to do ridiculous things with it. I would have thought, on some level, that, “We're going to start a computer company in the Bay Area making computers,” would have been one of those, but given that we are a year into the correction, and things seem to be heading up into the right for you folks, that take was wrong. How'd I get it wrong?Steve: Well, I mean, first of all, you got part of it right, which is there were just a litany of ridiculous companies and projects and money being thrown in all directions at that time.Corey: An NFT of a computer. We're going to have one of those. That's what you're selling, right? Then you had to actually hard pivot to making the real thing.Steve: That's it. So, we might as well cut right to it, you know. This is—we went through the crypto phase. But you know, our—when we started the company, it was yes, a computer company. It's on the tin. It's definitely kind of the foundation of what we're building. But you know, we think about what a modern computer looks like through the lens of cloud.I was at a cloud computing company for ten years prior to us founding Oxide, so was Bryan Cantrill, CTO, co-founder. And, you know, we are huge, huge fans of cloud computing, which was an interesting kind of dichotomy. Instead of conversations when we were raising for Oxide—because of course, Sand Hill is terrified of hardware. And when we think about what modern computers need to look like, they need to be in support of the characteristics of cloud, and cloud computing being not that you're renting someone else's computers, but that you have fully programmable infrastructure that allows you to slice and dice, you know, compute and storage and networking however software needs. And so, what we set out to go build was a way for the companies that are running on-premises infrastructure—which, by the way, is almost everyone and will continue to be so for a very long time—access to the benefits of cloud computing. And to do that, you need to build a different kind of computing infrastructure and architecture, and you need to plumb the whole thing with software.Corey: There are a number of different ways to view cloud computing. And I think that a lot of the, shall we say, incumbent vendors over in the computer manufacturing world tend to sound kind of like dinosaurs, on some level, where they're always talking in terms of, you're a giant company and you already have a whole bunch of data centers out there. But one of the magical pieces of cloud is you can have a ridiculous idea at nine o'clock tonight and by morning, you'll have a prototype, if you're of that bent. And if it turns out it doesn't work, you're out, you know, 27 cents. And if it does work, you can keep going and not have to stop and rebuild on something enterprise-grade.So, for the small-scale stuff and rapid iteration, cloud providers are terrific. Conversely, when you wind up in the giant fleets of millions of computers, in some cases, there begin to be economic factors that weigh in, and for some on workloads—yes, I know it's true—going to a data center is the economical choice. But my question is, is starting a new company in the direction of building these things, is it purely about economics or is there a capability story tied in there somewhere, too?Steve: Yeah, it's actually economics ends up being a distant third, fourth, in the list of needs and priorities from the companies that we're working with. When we talk about—and just to be clear we're—our demographic, that kind of the part of the market that we are focused on are large enterprises, like, folks that are spending, you know, half a billion, billion dollars a year in IT infrastructure, they, over the last five years, have moved a lot of the use cases that are great for public cloud out to the public cloud, and who still have this very, very large need, be it for latency reasons or cost reasons, security reasons, regulatory reasons, where they need on-premises infrastructure in their own data centers and colo facilities, et cetera. And it is for those workloads in that part of their infrastructure that they are forced to live with enterprise technologies that are 10, 20, 30 years old, you know, that haven't evolved much since I left Dell in 2009. And, you know, when you think about, like, what are the capabilities that are so compelling about cloud computing, one of them is yes, what you mentioned, which is you have an idea at nine o'clock at night and swipe a credit card, and you're off and running. And that is not the case for an idea that someone has who is going to use the on-premises infrastructure of their company. And this is where you get shadow IT and 16 digits to freedom and all the like.Corey: Yeah, everyone with a corporate credit card winds up being a shadow IT source in many cases. If your processes as a company don't make it easier to proceed rather than doing it the wrong way, people are going to be fighting against you every step of the way. Sometimes the only stick you've got is that of regulation, which in some industries, great, but in other cases, no, you get to play Whack-a-Mole. I've talked to too many companies that have specific scanners built into their mail system every month looking for things that look like AWS invoices.Steve: [laugh]. Right, exactly. And so, you know, but if you flip it around, and you say, well, what if the experience for all of my infrastructure that I am running, or that I want to provide to my software development teams, be it rented through AWS, GCP, Azure, or owned for economic reasons or latency reasons, I had a similar set of characteristics where my development team could hit an API endpoint and provision instances in a matter of seconds when they had an idea and only pay for what they use, back to kind of corporate IT. And what if they were able to use the same kind of developer tools they've become accustomed to using, be it Terraform scripts and the kinds of access that they are accustomed to using? How do you make those developers just as productive across the business, instead of just through public cloud infrastructure?At that point, then you are in a much stronger position where you can say, you know, for a portion of things that are, as you pointed out, you know, more unpredictable, and where I want to leverage a bunch of additional services that a particular cloud provider has, I can rent that. And where I've got more persistent workloads or where I want a different economic profile or I need to have something in a very low latency manner to another set of services, I can own it. And that's where I think the real chasm is because today, you just don't—we take for granted the basic plumbing of cloud computing, you know? Elastic Compute, Elastic Storage, you know, networking and security services. And us in the cloud industry end up wanting to talk a lot more about exotic services and, sort of, higher-up stack capabilities. None of that basic plumbing is accessible on-prem.Corey: I also am curious as to where exactly Oxide lives in the stack because I used to build computers for myself in 2000, and it seems like having gone down that path a bit recently, yeah, that process hasn't really improved all that much. The same off-the-shelf components still exist and that's great. We always used to disparagingly call spinning hard drives as spinning rust in racks. You named the company Oxide; you're talking an awful lot about the Rust programming language in public a fair bit of the time, and I'm starting to wonder if maybe words don't mean what I thought they meant anymore. Where do you folks start and stop, exactly?Steve: Yeah, that's a good question. And when we started, we sort of thought the scope of what we were going to do and then what we were going to leverage was smaller than it has turned out to be. And by that I mean, man, over the last three years, we have hit a bunch of forks in the road where we had questions about do we take something off the shelf or do we build it ourselves. And we did not try to build everything ourselves. So, to give you a sense of kind of where the dotted line is, around the Oxide product, what we're delivering to customers is a rack-level computer. So, the minimum size comes in rack form. And I think your listeners are probably pretty familiar with this. But, you know, a rack is—Corey: You would be surprised. It's basically, what are they about seven feet tall?Steve: Yeah, about eight feet tall.Corey: Yeah, yeah. Seven, eight feet, weighs a couple 1000 pounds, you know, make an insulting joke about—Steve: Two feet wide.Corey: —NBA players here. Yeah, all kinds of these things.Steve: Yeah. And big hunk of metal. And in the cases of on-premises infrastructure, it's kind of a big hunk of metal hole, and then a bunch of 1U and 2U boxes crammed into it. What the hyperscalers have done is something very different. They started looking at, you know, at the rack level, how can you get much more dense, power-efficient designs, doing things like using a DC bus bar down the back, instead of having 64 power supplies with cables hanging all over the place in a rack, which I'm sure is what you're more familiar with.Corey: Tremendous amount of weight as well because you have the metal chassis for all of those 1U things, which in some cases, you wind up with, what, 46U in a rack, assuming you can even handle the cooling needs of all that.Steve: That's right.Corey: You have so much duplication, and so much of the weight is just metal separating one thing from the next thing down below it. And there are opportunities for massive improvement, but you need to be at a certain point of scale to get there.Steve: You do. You do. And you also have to be taking on the entire problem. You can't pick at parts of these things. And that's really what we found. So, we started at this sort of—the rack level as sort of the design principle for the product itself and found that that gave us the ability to get to the right geometry, to get as much CPU horsepower and storage and throughput and networking into that kind of chassis for the least amount of wattage required, kind of the most power-efficient design possible.So, it ships at the rack level and it ships complete with both our server sled systems in Oxide, a pair of Oxide switches. This is—when I talk about, like, design decisions, you know, do we build our own switch, it was a big, big, big question early on. We were fortunate even though we were leaning towards thinking we needed to go do that, we had this prospective early investor who was early at AWS and he had asked a very tough question that none of our other investors had asked to this point, which is, “What are you going to do about the switch?”And we knew that the right answer to an investor is like, “No. We're already taking on too much.” We're redesigning a server from scratch in, kind of, the mold of what some of the hyperscalers have learned, doing our own Root of Trust, we're doing our own operating system, hypervisor control plane, et cetera. Taking on the switch could be seen as too much, but we told them, you know, we think that to be able to pull through all of the value of the security benefits and the performance and observability benefits, we can't have then this [laugh], like, obscure third-party switch rammed into this rack.Corey: It's one of those things that people don't think about, but it's the magic of cloud with AWS's network, for example, it's magic. You can get line rate—or damn near it—between any two points, sustained.Steve: That's right.Corey: Try that in the data center, you wind into massive congestion with top-of-rack switches, where, okay, we're going to parallelize this stuff out over, you know, two dozen racks and we're all going to have them seamlessly transfer information between each other at line rate. It's like, “[laugh] no, you're not because those top-of-rack switches will melt and become side-of-rack switches, and then bottom-puddle-of-rack switches. It doesn't work that way.”Steve: That's right.Corey: And you have to put a lot of thought and planning into it. That is something that I've not heard a traditional networking vendor addressing because everyone loves to hand-wave over it.Steve: Well so, and this particular prospective investor, we told him, “We think we have to go build our own switch.” And he said, “Great.” And we said, “You know, we think we're going to lose you as an investor as a result, but this is what we're doing.” And he said, “If you're building your own switch, I want to invest.” And his comment really stuck with us, which is AWS did not stand on their own two feet until they threw out their proprietary switch vendor and built their own.And that really unlocked, like you've just mentioned, like, their ability, both in hardware and software to tune and optimize to deliver that kind of line rate capability. And that is one of the big findings for us as we got into it. Yes, it was really, really hard, but based on a couple of design decisions, P4 being the programming language that we are using as the surround for our silicon, tons of opportunities opened up for us to be able to do similar kinds of optimization and observability. And that has been a big, big win.But to your question of, like, where does it stop? So, we are delivering this complete with a baked-in operating system, hypervisor, control plane. And so, the endpoint of the system, where the customer meets is either hitting an API or a CLI or a console that delivers and kind of gives you the ability to spin up projects. And, you know, if one is familiar with EC2 and EBS and VPC, that VM level of abstraction is where we stop.Corey: That, I think, is a fair way of thinking about it. And a lot of cloud folks are going to pooh-pooh it as far as saying, “Oh well, just virtual machines. That's old cloud. That just treats the cloud like a data center.” And in many cases, yes, it does because there are ways to build modern architectures that are event-driven on top of things like Lambda, and API Gateway, and the rest, but you take a look at what my customers are doing and what drives the spend, it is invariably virtual machines that are largely persistent.Sometimes they scale up, sometimes they scale down, but there's always a baseline level of load that people like to hand-wave away the fact that what they're fundamentally doing in a lot of these cases, is paying the cloud provider to handle the care and feeding of those systems, which can be expensive, yes, but also delivers significant innovation beyond what almost any company is going to be able to deliver in-house. There is no way around it. AWS is better than you are—whoever you happen to—be at replacing failed hard drives. That is a simple fact. They have teams of people who are the best in the world of replacing failed hard drives. You generally do not. They are going to be better at that than you. But that's not the only axis. There's not one calculus that leads to, is cloud a scam or is cloud a great value proposition for us? The answer is always a deeply nuanced, “It depends.”Steve: Yeah, I mean, I think cloud is a great value proposition for most and a growing amount of software that's being developed and deployed and operated. And I think, you know, one of the myths that is out there is, hey, turn over your IT to AWS because we have or you know, a cloud provider—because we have such higher caliber personnel that are really good at swapping hard drives and dealing with networks and operationally keeping this thing running in a highly available manner that delivers good performance. That is certainly true, but a lot of the operational value in an AWS is been delivered via software, the automation, the observability, and not actual people putting hands on things. And it's an important point because that's been a big part of what we're building into the product. You know, just because you're running infrastructure in your own data center, it does not mean that you should have to spend, you know, 1000 hours a month across a big team to maintain and operate it. And so, part of that, kind of, cloud, hyperscaler innovation that we're baking into this product is so that it is easier to operate with much, much, much lower overhead in a highly available, resilient manner.Corey: So, I've worked in a number of data center facilities, but the companies I was working with, were always at a scale where these were co-locations, where they would, in some cases, rent out a rack or two, in other cases, they'd rent out a cage and fill it with their own racks. They didn't own the facilities themselves. Those were always handled by other companies. So, my question for you is, if I want to get a pile of Oxide racks into my environment in a data center, what has to change? What are the expectations?I mean, yes, there's obviously going to be power and requirements at the data center colocation is very conversant with, but Open Compute, for example, had very specific requirements—to my understanding—around things like the airflow construction of the environment that they're placed within. How prescriptive is what you've built, in terms of doing a building retrofit to start using you folks?Steve: Yeah, definitely not. And this was one of the tensions that we had to balance as we were designing the product. For all of the benefits of hyperscaler computing, some of the design center for you know, the kinds of racks that run in Google and Amazon and elsewhere are hyperscaler-focused, which is unlimited power, in some cases, data centers designed around the equipment itself. And where we were headed, which was basically making hyperscaler infrastructure available to, kind of, the masses, the rest of the market, these folks don't have unlimited power and they aren't going to go be able to go redesign data centers. And so no, the experience should be—with exceptions for folks maybe that have very, very limited access to power—that you roll this rack into your existing data center. It's on standard floor tile, that you give it power, and give it networking and go.And we've spent a lot of time thinking about how we can operate in the wide-ranging environmental characteristics that are commonplace in data centers that focus on themselves, colo facilities, and the like. So, that's really on us so that the customer is not having to go to much work at all to kind of prepare and be ready for it.Corey: One of the challenges I have is how to think about what you've done because you are rack-sized. But what that means is that my own experimentation at home recently with on-prem stuff for smart home stuff involves a bunch of Raspberries Pi and a [unintelligible 00:19:42], but I tend to more or less categorize you the same way that I do AWS Outposts, as well as mythical creatures, like unicorns or giraffes, where I don't believe that all these things actually exist because I haven't seen them. And in fact, to get them in my house, all four of those things would theoretically require a loading dock if they existed, and that's a hard thing to fake on a demo signup form, as it turns out. How vaporware is what you've built? Is this all on paper and you're telling amazing stories or do they exist in the wild?Steve: So, last time we were on, it was all vaporware. It was a couple of napkin drawings and a seed round of funding.Corey: I do recall you not using that description at the time, for what it's worth. Good job.Steve: [laugh]. Yeah, well, at least we were transparent where we were going through the race. We had some napkin drawings and we had some good ideas—we thought—and—Corey: You formalize those and that's called Microsoft PowerPoint.Steve: That's it. A hundred percent.Corey: The next generative AI play is take the scrunched-up, stained napkin drawing, take a picture of it, and convert it to a slide.Steve: Google Docs, you know, one of those. But no, it's got a lot of scars from the build and it is real. In fact, next week, we are going to be shipping our first commercial systems. So, we have got a line of racks out in our manufacturing facility in lovely Rochester, Minnesota. Fun fact: Rochester, Minnesota, is where the IBM AS/400s were built.Corey: I used to work in that market, of all things.Steve: Really?Corey: Selling tape drives in the AS/400. I mean, I still maintain there's no real mainframe migration to the cloud play because there's no AWS/400. A joke that tends to sail over an awful lot of people's heads because, you know, most people aren't as miserable in their career choices as I am.Steve: Okay, that reminds me. So, when we were originally pitching Oxide and we were fundraising, we [laugh]—in a particular investor meeting, they asked, you know, “What would be a good comp? Like how should we think about what you are doing?” And fortunately, we had about 20 investor meetings to go through, so burning one on this was probably okay, but we may have used the AS/400 as a comp, talking about how [laugh] mainframe systems did such a good job of building hardware and software together. And as you can imagine, there were some blank stares in that room.But you know, there are some good analogs to historically in the computing industry, when you know, the industry, the major players in the industry, were thinking about how to deliver holistic systems to support end customers. And, you know, we see this in the what Apple has done with the iPhone, and you're seeing this as a lot of stuff in the automotive industry is being pulled in-house. I was listening to a good podcast. Jim Farley from Ford was talking about how the automotive industry historically outsourced all of the software that controls cars, right? So, like, Bosch would write the software for the controls for your seats.And they had all these suppliers that were writing the software, and what it meant was that innovation was not possible because you'd have to go out to suppliers to get software changes for any little change you wanted to make. And in the computing industry, in the 80s, you saw this blow apart where, like, firmware got outsourced. In the IBM and the clones, kind of, race, everyone started outsourcing firmware and outsourcing software. Microsoft started taking over operating systems. And then VMware emerged and was doing a virtualization layer.And this, kind of, fragmented ecosystem is the landscape today that every single on-premises infrastructure operator has to struggle with. It's a kit car. And so, pulling it back together, designing things in a vertically integrated manner is what the hyperscalers have done. And so, you mentioned Outposts. And, like, it's a good example of—I mean, the most public cloud of public cloud companies created a way for folks to get their system on-prem.I mean, if you need anything to underscore the draw and the demand for cloud computing-like, infrastructure on-prem, just the fact that that emerged at all tells you that there is this big need. Because you've got, you know, I don't know, a trillion dollars worth of IT infrastructure out there and you have maybe 10% of it in the public cloud. And that's up from 5% when Jassy was on stage in '21, talking about 95% of stuff living outside of AWS, but there's going to be a giant market of customers that need to own and operate infrastructure. And again, things have not improved much in the last 10 or 20 years for them.Corey: They have taken a tone onstage about how, “Oh, those workloads that aren't in the cloud, yet, yeah, those people are legacy idiots.” And I don't buy that for a second because believe it or not—I know that this cuts against what people commonly believe in public—but company execs are generally not morons, and they make decisions with context and constraints that we don't see. Things are the way they are for a reason. And I promise that 90% of corporate IT workloads that still live on-prem are not being managed or run by people who've never heard of the cloud. There was a decision made when some other things were migrating of, do we move this thing to the cloud or don't we? And the answer at the time was no, we're going to keep this thing on-prem where it is now for a variety of reasons of varying validity. But I don't view that as a bug. I also, frankly, don't want to live in a world where all the computers are basically run by three different companies.Steve: You're spot on, which is, like, it does a total disservice to these smart and forward-thinking teams in every one of the Fortune 1000-plus companies who are taking the constraints that they have—and some of those constraints are not monetary or entirely workload-based. If you want to flip it around, we were talking to a large cloud SaaS company and their reason for wanting to extend it beyond the public cloud is because they want to improve latency for their e-commerce platform. And navigating their way through the complex layers of the networking stack at GCP to get to where the customer assets are that are in colo facilities, adds lag time on the platform that can cost them hundreds of millions of dollars. And so, we need to think behind this notion of, like, “Oh, well, the dark ages are for software that can't run in the cloud, and that's on-prem. And it's just a matter of time until everything moves to the cloud.”In the forward-thinking models of public cloud, it should be both. I mean, you should have a consistent experience, from a certain level of the stack down, everywhere. And then it's like, do I want to rent or do I want to own for this particular use case? In my vast set of infrastructure needs, do I want this to run in a data center that Amazon runs or do I want this to run in a facility that is close to this other provider of mine? And I think that's best for all. And then it's not this kind of false dichotomy of quality infrastructure or ownership.Corey: I find that there are also workloads where people will come to me and say, “Well, we don't think this is going to be economical in the cloud”—because again, I focus on AWS bills. That is the lens I view things through, and—“The AWS sales rep says it will be. What do you think?” And I look at what they're doing and especially if involves high volumes of data transfer, I laugh a good hearty laugh and say, “Yeah, keep that thing in the data center where it is right now. You will thank me for it later.”It's, “Well, can we run this in an economical way in AWS?” As long as you're okay with economical meaning six times what you're paying a year right now for the same thing, yeah, you can. I wouldn't recommend it. And the numbers sort of speak for themselves. But it's not just an economic play.There's also the story of, does this increase their capability? Does it let them move faster toward their business goals? And in a lot of cases, the answer is no, it doesn't. It's one of those business process things that has to exist for a variety of reasons. You don't get to reimagine it for funsies and even if you did, it doesn't advance the company in what they're trying to do any, so focus on something that differentiates as opposed to this thing that you're stuck on.Steve: That's right. And what we see today is, it is easy to be in that mindset of running things on-premises is kind of backwards-facing because the experience of it is today still very, very difficult. I mean, talking to folks and they're sharing with us that it takes a hundred days from the time all the different boxes land in their warehouse to actually having usable infrastructure that developers can use. And our goal and what we intend to go hit with Oxide as you can roll in this complete rack-level system, plug it in, within an hour, you have developers that are accessing cloud-like services out of the infrastructure. And that—God, countless stories of firmware bugs that would send all the fans in the data center nonlinear and soak up 100 kW of power.Corey: Oh, God. And the problems that you had with the out-of-band management systems. For a long time, I thought Drax stood for, “Dell, RMA Another Computer.” It was awful having to deal with those things. There was so much room for innovation in that space, which no one really grabbed onto.Steve: There was a really, really interesting talk at DEFCON that we just stumbled upon yesterday. The NVIDIA folks are giving a talk on BMC exploits… and like, a very, very serious BMC exploit. And again, it's what most people don't know is, like, first of all, the BMC, the Baseboard Management Controller, is like the brainstem of the computer. It has access to—it's a backdoor into all of your infrastructure. It's a computer inside a computer and it's got software and hardware that your server OEM didn't build and doesn't understand very well.And firmware is even worse because you know, firmware written by you know, an American Megatrends or other is a big blob of software that gets loaded into these systems that is very hard to audit and very hard to ascertain what's happening. And it's no surprise when, you know, back when we were running all the data centers at a cloud computing company, that you'd run into these issues, and you'd go to the server OEM and they'd kind of throw their hands up. Well, first they'd gaslight you and say, “We've never seen this problem before,” but when you thought you've root-caused something down to firmware, it was anyone's guess. And this is kind of the current condition today. And back to, like, the journey to get here, we kind of realized that you had to blow away that old extant firmware layer, and we rewrote our own firmware in Rust. Yes [laugh], I've done a lot in Rust.Corey: No, it was in Rust, but, on some level, that's what Nitro is, as best I can tell, on the AWS side. But it turns out that you don't tend to have the same resources as a one-and-a-quarter—at the moment—trillion-dollar company. That keeps [valuing 00:30:53]. At one point, they lost a comma and that was sad and broke all my logic for that and I haven't fixed it since. Unfortunate stuff.Steve: Totally. I think that was another, kind of, question early on from certainly a lot of investors was like, “Hey, how are you going to pull this off with a smaller team and there's a lot of surface area here?” Certainly a reasonable question. Definitely was hard. The one advantage—among others—is, when you are designing something kind of in a vertical holistic manner, those design integration points are narrowed down to just your equipment.And when someone's writing firmware, when AMI is writing firmware, they're trying to do it to cover hundreds and hundreds of components across dozens and dozens of vendors. And we have the advantage of having this, like, purpose-built system, kind of, end-to-end from the lowest level from first boot instruction, all the way up through the control plane and from rack to switch to server. That definitely helped narrow the scope.Corey: This episode has been fake sponsored by our friends at AWS with the following message: Graviton Graviton, Graviton, Graviton, Graviton, Graviton, Graviton, Graviton, Graviton. Thank you for your l-, lack of support for this show. Now, AWS has been talking about Graviton an awful lot, which is their custom in-house ARM processor. Apple moved over to ARM and instead of talking about benchmarks they won't publish and marketing campaigns with words that don't mean anything, they've let the results speak for themselves. In time, I found that almost all of my workloads have moved over to ARM architecture for a variety of reason, and my laptop now gets 15 hours of battery life when all is said and done. You're building these things on top of x86. What is the deal there? I do not accept that if that you hadn't heard of ARM until just now because, as mentioned, Graviton, Graviton, Graviton.Steve: That's right. Well, so why x86, to start? And I say to start because we have just launched our first generation products. And our first-generation or second-generation products that we are now underway working on are going to be x86 as well. We've built this system on AMD Milan silicon; we are going to be launching a Genoa sled.But when you're thinking about what silicon to use, obviously, there's a bunch of parts that go into the decision. You're looking at the kind of applicability to workload, performance, power management, for sure, and if you carve up what you are trying to achieve, x86 is still a terrific fit for the broadest set of workloads that our customers are trying to solve for. And choosing which x86 architecture was certainly an easier choice, come 2019. At this point, AMD had made a bunch of improvements in performance and energy efficiency in the chip itself. We've looked at other architectures and I think as we are incorporating those in the future roadmap, it's just going to be a question of what are you trying to solve for.You mentioned power management, and that is kind of commonly been a, you know, low power systems is where folks have gone beyond x86. Is we're looking forward to hardware acceleration products and future products, we'll certainly look beyond x86, but x86 has a long, long road to go. It still is kind of the foundation for what, again, is a general-purpose cloud infrastructure for being able to slice and dice for a variety of workloads.Corey: True. I have to look around my environment and realize that Intel is not going anywhere. And that's not just an insult to their lack of progress on committed roadmaps that they consistently miss. But—Steve: [sigh].Corey: Enough on that particular topic because we want to keep this, you know, polite.Steve: Intel has definitely had some struggles for sure. They're very public ones, I think. We were really excited and continue to be very excited about their Tofino silicon line. And this came by way of the Barefoot networks acquisition. I don't know how much you had paid attention to Tofino, but what was really, really compelling about Tofino is the focus on both hardware and software and programmability.So, great chip. And P4 is the programming language that surrounds that. And we have gotten very, very deep on P4, and that is some of the best tech to come out of Intel lately. But from a core silicon perspective for the rack, we went with AMD. And again, that was a pretty straightforward decision at the time. And we're planning on having this anchored around AMD silicon for a while now.Corey: One last question I have before we wind up calling it an episode, it seems—at least as of this recording, it's still embargoed, but we're not releasing this until that winds up changing—you folks have just raised another round, which means that your napkin doodles have apparently drawn more folks in, and now that you're shipping, you're also not just bringing in customers, but also additional investor money. Tell me about that.Steve: Yes, we just completed our Series A. So, when we last spoke three years ago, we had just raised our seed and had raised $20 million at the time, and we had expected that it was going to take about that to be able to build the team and build the product and be able to get to market, and [unintelligible 00:36:14] tons of technical risk along the way. I mean, there was technical risk up and down the stack around this [De Novo 00:36:21] server design, this the switch design. And software is still the kind of disproportionate majority of what this product is, from hypervisor up through kind of control plane, the cloud services, et cetera. So—Corey: We just view it as software with a really, really confusing hardware dongle.Steve: [laugh]. Yeah. Yes.Corey: Super heavy. We're talking enterprise and government-grade here.Steve: That's right. There's a lot of software to write. And so, we had a bunch of milestones that as we got through them, one of the big ones was getting Milan silicon booting on our firmware. It was funny it was—this was the thing that clearly, like, the industry was most suspicious of, us doing our own firmware, and you could see it when we demonstrated booting this, like, a year-and-a-half ago, and AMD all of a sudden just lit up, from kind of arm's length to, like, “How can we help? This is amazing.” You know? And they could start to see the benefits of when you can tie low-level silicon intelligence up through a hypervisor there's just—Corey: No I love the existing firmware I have. Looks like it was written in 1984 and winds up having terrible user ergonomics that hasn't been updated at all, and every time something comes through, it's a 50/50 shot as whether it fries the box or not. Yeah. No, I want that.Steve: That's right. And you look at these hyperscale data centers, and it's like, no. I mean, you've got intelligence from that first boot instruction through a Root of Trust, up through the software of the hyperscaler, and up to the user level. And so, as we were going through and kind of knocking down each one of these layers of the stack, doing our own firmware, doing our own hardware Root of Trust, getting that all the way plumbed up into the hypervisor and the control plane, number one on the customer side, folks moved from, “This is really interesting. We need to figure out how we can bring cloud capabilities to our data centers. Talk to us when you have something,” to, “Okay. We actually”—back to the earlier question on vaporware, you know, it was great having customers out here to Emeryville where they can put their hands on the rack and they can, you know, put your hands on software, but being able to, like, look at real running software and that end cloud experience.And that led to getting our first couple of commercial contracts. So, we've got some great first customers, including a large department of the government, of the federal government, and a leading firm on Wall Street that we're going to be shipping systems to in a matter of weeks. And as you can imagine, along with that, that drew a bunch of renewed interest from the investor community. Certainly, a different climate today than it was back in 2019, but what was great to see is, you still have great investors that understand the importance of making bets in the hard tech space and in companies that are looking to reinvent certain industries. And so, we added—our existing investors all participated. We added a bunch of terrific new investors, both strategic and institutional.And you know, this capital is going to be super important now that we are headed into market and we are beginning to scale up the business and make sure that we have a long road to go. And of course, maybe as importantly, this was a real confidence boost for our customers. They're excited to see that Oxide is going to be around for a long time and that they can invest in this technology as an important part of their infrastructure strategy.Corey: I really want to thank you for taking the time to speak with me about, well, how far you've come in a few years. If people want to learn more and have the requisite loading dock, where should they go to find you?Steve: So, we try to put everything up on the site. So, oxidecomputer.com or oxide.computer. We also, if you remember, we did [On the Metal 00:40:07]. So, we had a Tales from the Hardware-Software Interface podcast that we did when we started. We have shifted that to Oxide and Friends, which the shift there is we're spending a little bit more time talking about the guts of what we built and why. So, if folks are interested in, like, why the heck did you build a switch and what does it look like to build a switch, we actually go to depth on that. And you know, what does bring-up on a new server motherboard look like? And it's got some episodes out there that might be worth checking out.Corey: We will definitely include a link to that in the [show notes 00:40:36]. Thank you so much for your time. I really appreciate it.Steve: Yeah, Corey. Thanks for having me on.Corey: Steve Tuck, CEO at Oxide Computer Company. I'm Cloud Economist Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this episode, please leave a five-star review on your podcast platform of choice, along with an angry ranting comment because you are in fact a zoology major, and you're telling me that some animals do in fact exist. But I'm pretty sure of the two of them, it's the unicorn.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.

Join Allie Clifton, Richard Jefferson, and Channing Frye for a captivating and hilarious game of Truth or Trash: Conspiracy Edition! In this episode of Road Trippin', the crew dives into some of the most intriguing conspiracy theories in the NBA. They discuss whether Michael Jordan's iconic "Flu Game" was actually caused by food poisoning or a hangover, share a funny story about their 2016 Cavaliers teammate throwing up in a car, and debate whether NBA stars will be tempted to play overseas. Have a question or topic for our next show? Text or leave us a VM at 657-522-5578 (6575-CALLRT) Cheers! ► YouTube!

On this episode, Nick Dais is joined George Carmona to talk about the week 2 NFL slate, are penalties on defensive players getting ridiculous, how public perception influences the betting markets and which 0-2 NFL teams is it time to panic for?! THANK YOU LEGENDS FOR ALL THE SUPPORT ON THE PATREON THE LAST FEW WEEKS!

Caitlin performed with Naomi last year when Naomi did a few road dates, and she was such a delight that we had to have her on the show! Now, maybe you've seen Caitlin Peluffo performing stand-up on any number of late night shows that we won't name because WE'RE ON STRIKE! Or maybe you've listened to her podcast Good Time Gal! Well, even if this is your first time getting to know Caitlin, you're gonna love her! We talk about freezing her eggs, dating a "clean comedian", being a "jizz raccoon" (?) and so much more! PLUS, obvi, we answer YOUR advice questions! If you'd like to ask your own advice questions, call 323-524-7839 and leave a VM or just DM us on IG or Twitter! Oh, and go see Caitlin on tour (and wear a goshdarn mask!), why don't ya?!Support the show on Patreon (two extra exclusive episodes a month!) or with a t-shirt (or a Jewboo shirt) and check out clips on YouTube! And why not leave a 5-star review on Apple Podcasts? It takes less than a minute! Plus! Check out Andy's old casiopop band's lost album! And discounted Couples Therapy Quarantine Crew t-shirts here (if you don't get one, we're gonna have A LOT of nightshirts over at the ol' Beckperigin household!)! And if you'd like to read our good friend Jo Firestone hilarious debut novel, you can pre-order it here! Hosted on Acast. See acast.com/privacy for more information.

James and Jon talk about the lovely indie from Sabotage, the same folks that made the Messenger. We also cover some news such as PS+ prices going up already. If you want to be a part of the conversation or if you have a pressing question that you want us to weigh in on… You can reach us on twitter @mngamerspodcast. If you don't use twitter you can send email the old fashion way to ⁠podcast@mostlynormalgamers.com⁠. Sign up for our new newsletter, Mostly Normal Monthly at mngamers.substack.com! Back issues can be found there too!  Text or VM to (507) 291-2991. VOD on the Mostly Normal Gamers YouTube channel (https://www.youtube.com/@mostlynormalgamers6377) Jon Swanson @jonnysamsonite Chris Stern @vgoccasion Angie @stellarsmalls James Halliday @buttlordprimus --- Send in a voice message: https://podcasters.spotify.com/pod/show/mostlynormalgamers/message

On this episode of Road Trippin', Richard, Channing and Allie welcome back Zach Collins. In this episode, the crew discusses USA Basketball's performance in the World Championship, debates who the best European player of all time is between Jokic and Giannis, and even plays a game of Truth or Trash. Plus, Zach Collins opens up about his experience being coached by Becky Hammon, and the crew discusses her Hall of Fame credentials. Have a question or topic for our next show? Text or leave us a VM at 657-522-5578 (6575-CALLRT) Cheers! ► YouTube!

Nyheter från Frankrike på lätt franska. En rekordsen värmebölja sveper över Frankrike samtidigt som skolorna börjar igen. Vi träffar Eliot och pratar om hur det är att gå i skolan när det är så varmt. Dags för VM i rugby som hålls i Frankrike! Vi intervjuar Orphéa som är rugbyfan. Till sist lyssnar vi på Hoshi, en ung artist som fått utstå homofobi och trakasserier.

Nyheter från Frankrike på medelsvår franska. En rekordsen värmebölja sveper över Frankrike samtidigt som skolorna börjar igen. Vi träffar Yanis och Eliot och pratar om hur det är att gå i skolan och bo i Paris när det är så varmt. Dags för VM i rugby som hålls i Frankrike! Vi intervjuar Orphéa som är rugbyfan. Till sist lyssnar vi på Hoshi, en ung artist som fått utstå homofobi och trakasserier.

De fleste opplever sorg i løpet av livet. Hvordan påvirker sorg kroppen? Og hvordan påvirker trening det mentale i en tøff sorgperiode? Toppidrettsutøver Mari Eide mistet søsteren sin et halvt år før hun tok sin VM-medalje. Hun forteller om hvordan dette halvåret var og hvordan det var mulig å prestere sitt livs løp i en svært vanskelig periode. Vidar Gjengedal Hansen mistet noen uker etter fødselen og forklarer hvordan treningen ble en del av krisehåndteringen. Mannen til Karen Marie Berg døde brått på en løpetur. Hun hadde stort utbytte av at venninner kom å dro henne ut i marka. Therese Johaug forteller hvordan hun taklet sterk sorg og trening i kombinasjon. Hjerneforsker Ole Petter Hjelle forklarer hva sorg og aktivitet gjør med hjernen. I tillegg har vi fått et eksklusivt møte med verdensmesteren på 1500 meter, Josh Kerr, som gir oss ukas økt. Og vi har ringt opp Yngvild Kaspersen etter prestisjetriumfen i fjellene rundt Chamonix. Hør episoden i appen NRK Radio

On this episode of Road Trippin', Richard, Channing and Allie sit down with special guest Zach Collins. The trio dives deep into various topics, including the young San Antonio Spurs team, rising star Victor Wembanyama, and how to navigate and deal with the criticism of legendary coach Gregg Popovich. The crew also gives their insight into the new Player Participation Policy, which will help the NBA curb load management, and gets Zach's perspective on missing time, and wanting to be on the court as much as possible. Have a question or topic for our next show? Text or leave us a VM at 657-522-5578 (6575-CALLRT) Cheers! ► YouTube!

Welcome episode 227 of the Cloud Pod podcast - where the forecast is always cloudy! This week your hosts are Justin, Jonathan, Matthew and Ryan - and they're REALLY excited to tell you all about the 161 one things announced at Google Next. Literally, all the things. We're also saying farewell to EC2 Classic, Amazon SES, and Azure's Explicit Proxy - which probably isn't what you think it is.  Titles we almost went with this week:

On this episode, Nick Dais is joined by Josh Williams Allen Strk and Bri Hunter to talk about the injury to Aaron Rodgers, why it's such a buzzkill for the Jets, their fans and all NFL fans, what should the Jets do at QB now? Then, Allen rejoins the show to talk about the week 2 games of the week in Dallas, Atlanta with his Falcons going up against the Packers and The Chiefs going into DUVALLL to play the Jaguars

Ian Mendes and Sean McIndoe return to discuss the latest in the Mike Babcock situation, as the NHL and NHLPA heads to Columbus to investigate. Also, the Jets name Adam Lowry captain, and they discuss the remaining teams in the league to have open captaincy positions. Then, in "Granger Things", Jesse Granger brings some playoff odds and questions about Tampa Bay's potential shot at the postseason this year. To wrap up, the origin of "Down Goes Brown" is revealed in the mailbag, and to wrap up, a look back with "This Week in Hockey History". Have a question for the show? Email theathletichockeyshow@gmail.com or leave a VM: (845) 445-8459! SUBSCRIBE TO THE ATHLETIC NHL'S YOUTUBE CHANNEL AT youtube.com/@theathletichockeyshow Get a new subscription to the Athletic for $/1 per month for 12 months when you visit theathletic.com/hockeyshow Right now, Nuts.com is offering new customers a free gift with purchase and free shipping on orders of $29 or more at nuts.com/hockey23. So, go check out all of the delicious options at nuts.com/hockey23. You'll receive a free gift and free shipping when you spend $29 or more! That's nuts.com/hockey23 Learn more about your ad choices. Visit megaphone.fm/adchoices

The absolutely lovely Karan Soni is on today's episode, and of course you know him from A LOT OF STRUCK SHOWS AND MOVIES; yes folks, we're still on strike so we're not gonna mention what Karan's been in, but obvi you know or feel free to look it up! Heck, we ain't striking against Google! Anyway, Karan understood the assignment of being on the show, and we get in deep about meeting his partner, coming out to his parents, being sent away to, uh, a weight loss boarding school and so much more! PLUS, obvi, we answer YOUR advice questions! If you'd like to ask your own advice questions, call 323-524-7839 and leave a VM or just DM us on IG or Twitter!Support the show on Patreon (two extra exclusive episodes a month!) or with a t-shirt (or a Jewboo shirt) and check out clips on YouTube! And why not leave a 5-star review on Apple Podcasts? It takes less than a minute! Plus! Check out Andy's old casiopop band's lost album! And discounted Couples Therapy Quarantine Crew t-shirts here (if you don't get one, we're gonna have A LOT of nightshirts over at the ol' Beckperigin household!)! And if you'd like to read our good friend Jo Firestone hilarious debut novel, you can pre-order it here! Hosted on Acast. See acast.com/privacy for more information.

El Land Cruiser nace como una copia del genuino Jeep Willys Overland… una copia fiel. ¿No te lo crees? Si pones uno junto al otro, resulta evidente y es lo que vamos a hacer para ti. Desde ese lejano 1951 hasta hoy el Land Cruiser no ha dejado de evolucionar y de mejorar, superando al original y convirtiéndose en uno de los pocos coches presentes en los 5 continentes. En el consultorio de este podcast os voy a contar por qué nació este canal… Pero, ¡hablemos del Land Cruiser! Porque este otro vídeo que tenía ganas de hacer y que tendrá unas cuantas anécdotas. Y como las historias deben arrancar desde el principio, no nos vamos al año 1951 sino a finales de los años 40. Para entender el nacimiento de este modelo hay que conocer la situación de Japón en esos años. El 15 de agosto de 1945 el Imperio Japonés firma su rendición incondicional en el USS Missouri: Japón se convierte en un país ocupado… Ocupado, destruido y desmoralizado. Los EE.UU. de Norteamérica ocuparon el país hasta 1952. Las ciudades y la industrias estaban destruidas. La tasa de suicidios se disparó en un país donde en el ejército no existe la palabra rendición y donde el suicidio, por cuestiones culturales, se considera algo digno… En 1950 estalla la guerra en Corea, cuando Corea del Norte invade Corea del Sur y Japón se convierte en una base de reavituallamiento para los norteamericanos, lo cual supone un espaldarazo a su industria y, especialmente, aumenta la producción de camiones destinados al ejército. Pero además de camiones se necesitaba un vehículo ligero, sencillo, barato y todo terreno ¿os suena? Y en 1951 nace el primer prototipo del Toyota Land Cruiser, una copia del Jeep, con chasis de un camión ligero y motor de 3,4 litros de gasolina… No hace falta ser ingeniero ni siquiera experto para ver que el Toyota es una copia muy fiel del Jeep. Es más, ¿sabéis cómo se llamaba inicialmente este coche? Jeep BJ… más claro, agua. Comienza la fabricación en serie del coche cuando Willys Company denuncia a Toyota. Esto tiene su gracia: Lo denuncia por el uso del nombre, no tanto por copiarlo. Esto es una opinión, pero parece que Willys no consideraba en esos momentos un rival peligroso a Toyota… ¡qué gran error! Es entonces, en 1954, cuando Toyota cambia la denominación y pasa a llamarlo “Land Cruiser”, un nombre que podríamos traducir como “Crucero terrestre” … me gusta, tanto en inglés como en español. Y comienza la evolución, rapidísima, de este modelo. El Serie 20 era mucho más que el paso del coche del mundo “civil” al “militar”, se mejora el confort y los faros pasan de las aletas a la parrilla central, dando lugar a una estética muy particular y que duraría muchos años. El Land Cruiser más bonito, con más personalidad, el que encumbró este modelo a la fama, la tercera generación, la llamada Serie 40 nace… ¡en 1960! ¡Qué buena cosecha la de ese año! De este modelo hubo multitud de variantes, con distintas distancias entre ejes, distintos motores y techo duro o de lona. A mí la versión de techo de chapa, con las esquinas acristaladas y redondeadas y los faros delanteros “juntitos”, un poco al estilo de los primeros Land Rover, me volvía loco… ¡me sigue volviendo loco! Y el Land Cruiser crece… y no parará de crecer, al menos en las versiones de batallas larga y cuatro puertas laterales. El FJ55 llegado en 1967 ofrece una versión con distancia entre ejes de 2,70 m y carrocerías más modernas… pero no más bonitas. En este Land Cruiser se abandonan las dos puertas traseras de acceso al maletero… se abandonan relativamente, porque esta opción coexiste con un portón que a su vez tiene el cristal descendente… una opción que a mí me gusta mucho y que probé por primera vez un Toyota 4Runner que, por consejo mío, compraron unos amigos… y que se podría considerar un derivado del Land Cruiser y, igual que él, indestructible. Hasta 1984 los Land Cruiser que podías comprar eran muchísimo mejores que el original, pero no dejaban de ser de algún modo un derivado del original y esto cambia con la serie 70, que conserva el nombre… y poco más. Una de las decisiones que se toman, acertadas, es hacer dos líneas distintas de Land Cruiser, una para profesionales denominada Heavy Duty y otra más cercana a un coche de turismo o Light Duty. Este modelo es mucho más refinado que su antecesor, por dentro, por fuera, en su mecánica… y le tengo especial cariño, pues mi primer contacto con los Land Cruiser, ya como probador, fue con este modelo, con el 250BJ73 “Made in Portugal”. Llevaba motor VM de 4 cilindros y 2,5 litros con 114 CV y los fabricaba Salvador Caetano en Portugal. El 1996 llega la serie 90, con unos acabados impecables, refinado, confortable, como siempre indestructible, nada barato… pero responsable de que, hasta hoy, este modelo compita sin complejos con los modelos “Premium” de otras marcas. Bueno, sin complejos o superándolos. Lo bueno de este Toyota es que se ha convertido en un coche confortable, incluso rápido, con una imagen inmejorable… pero sin renunciar a dos características claves: Fiabilidad y prestaciones en campo. A la serie 90 seguirían las series 100, 120, 150… ¡hasta la 300! Con motor V8 y más premium que nunca. Siempre manteniendo las cualidades que han hecho a este coche un coche único… por una cualidad o característica que me he dejado para el final… Muchas marcas han pretendido hacer un coche “Mundial”, que satisfaga las exigencias de todos los mercados, un espíritu con el que nació el Dacia Logan, el Fiat Palio y algunos modelos de Ford… y no funcionó, porque cada mercado tiene unos requisitos singulares. Pero el Land Cruiser si la ha conseguido. Ya sea como coche militar, en manos de ONG´s, de terroristas, de exploradores, en competición, en recorridos por caminos de todo el mundo, en países donde no hay carreteras o en urbanizaciones de lujo en países donde sí hay carreteras… lo cierto es que el Land Cruiser en un fenómeno único… que ha superado al original…

Professor Øyvind Sandbakk har samlet eksperter fra 15 land for å finne hva som har vært og blir trender treningsmessig. VM-snakkisene er også tema. Hør episoden i appen NRK Radio

On this episode, Nick Dais is joined by Josh Williams and Bri Hunter to talk about the UFC 293 PPV this weekend and why are we even having this fight? Will Adesanya be appreciated more when his time is done? Is Nick a POS for lying about being a black belt? What's the biggest lie you've ever told to try and bag someone at a bar. Then, Nick and Josh dive into the week 1 games of the week in Pittsburgh and in Chicago, why Week 1 is one of the best weeks to bet in the NFL and buckle up for massive overreactions no matter what happens in the 49ers game (45:00) Special Thanks To Our Sponsors! We've got a special deal for our listeners: Try BlueChew FREE when you use our promo code VM at checkout--just pay $5 shipping. That's BlueChew.com, promo code VM to receive your first month FREE. Visit BlueChew.com for more details and important safety information, and we thank BlueChew for sponsoring the podcast. @FlyMeOut Imagine if LinkedIn, AirBnB, and RAYA had a travel-loving baby. Whether you're looking to network with professionals on a beach or bond with creatives in the heart of a city, FlyMeOut has got you covered. Dive into curated experiences, and with their platform, it's never been easier to find your tribe and see the globe. Don't just travel, make memories with FlyMeOut! UseCode VM1 for expedited application review. Wager Attack Are you ready to take your sports betting game to the next level? Look no further than Wager Attack, the ultimate online Sportsbook for true sports enthusiasts. With a wide range of sports, live betting options, competitive odds, and a live casino. Wager Attack is where winners play. Join today using code VM and get bonuses & free play rollovers when depositing at the cashier  Wager attack is rocking with us through the NFL season & is the official odds provider of VM” Learn more about your ad choices. Visit podcastchoices.com/adchoices

Fotbollsmålvakten Zećira Mušović enorma bedrifter under fotbolls-VM 2023 kan inte ha undgått någon. Hennes föräldrar flydde det jugoslaviska inbördeskriget till Sverige och som nioåring började hon spela för Stattena IF. Redan som 13-åring kom hon att börja spela för A-laget och karriären tog henne sen vidare till FC Rosengård. Sedan 2018 så spelar hon i svenska landslaget och 2023 förlängdes hennes kontrakt för Chelsea FC.Vi får höra om hennes resa till att bli en målvakt på absoluta elitnivå. Vi pratar om hur hon arbetar med affirmationer, tacksamhetsövningar och sitt mindset inför varje match, och varför hon anser att processen är viktigare än resultatet. Vi går också in på varför Zećira alltid vill gå utanför sin comfort zone och om hennes projekt att stötta nästa generations drömmare. Tusen tack för att du lyssnar!Ta del av våra kurser på Framgångsakademin.Beställ "Mitt Framgångsår".Följ Alexander Pärleros på Instagram.Följ Alexander Pärleros på Tiktok.Bästa tipsen från avsnittet i Nyhetsbrevet.I samarbete med Convendum.Följ Zećira Mušović på instagram och besök hennes hemsida.Zećira Mušović - Next Generation DreamersZećira Mušović - Dröm stort, Zećira! Hosted on Acast. See acast.com/privacy for more information.

Fotbollsmålvakten Zećira Mušović enorma bedrifter under fotbolls-VM 2023 kan inte ha undgått någon. Hennes föräldrar flydde det jugoslaviska inbördeskriget till Sverige och som nioåring började hon spela för Stattena IF. Redan som 13-åring kom hon att börja spela för A-laget och karriären tog henne sen vidare till FC Rosengård. Sedan 2018 så spelar hon i svenska landslaget och 2023 förlängdes hennes kontrakt för Chelsea FC.Vi får höra om hennes resa till att bli en målvakt på absoluta elitnivå. Vi pratar om hur hon arbetar med affirmationer, tacksamhetsövningar och sitt mindset inför varje match, och varför hon anser att processen är viktigare än resultatet. Vi går också in på varför Zećira alltid vill gå utanför sin comfort zone och om hennes projekt att stötta nästa generations drömmare. Tusen tack för att du lyssnar!Ta del av våra kurser på Framgångsakademin.Beställ "Mitt Framgångsår".Följ Alexander Pärleros på Instagram.Följ Alexander Pärleros på Tiktok.Bästa tipsen från avsnittet i Nyhetsbrevet.I samarbete med Convendum.Följ Zećira Mušović på instagram och besök hennes hemsida.Zećira Mušović - Next Generation DreamersZećira Mušović - Dröm stort, Zećira! Hosted on Acast. See acast.com/privacy for more information.

Mom Stomp talks Bey's BeyDay show in LA, Brit giving up on Jesus, coulda/shoulda/wouldas of life, juicers, Karate Kid, couples being mean to each other in romance novels, lazy managers, overrated Instagram, hiding veggies and going Amish. Plus, we got a VM from FNLN, Megan Johns. #iwantedtobethereformyfamily #houseofjuice #keepdreamingbitch #anthranx #computerbyebye #igottohook #theepisodewherewecallourcongressman #handwritingisajoke #septemberisSNATCHED

In today's episode, we untangle the web of alphabet-soup technologies: CSPM, VM, SIEM, and Log Aggregators. We go beyond the buzzwords to give you a no-nonsense look at how these tools fit together, complement each other, or might even replace one another in specific use-cases. Selecting the right tool can be overwhelming, and we're here to guide you through the when, where, and how of leveraging these technologies effectively. Whether you're encountering overlapping features or unique challenges, we'll help you make a savvy, informed choice for your workloads. Tune in for a practical guide to navigating the complex landscape of cybersecurity tools.

You know her, you love her, that's right, writer, producer and friend Emily Gordon returns to the show for a solo outing so we can REALLY get to know her! Now, of course you know Emily from a number of Oscar and Emmy nominated things that we will not name because we are ON STRIKE, but feel free to look them up or look up her last appearance on THIS VERY show with her husband Kumail (episode 102?). And today we dig into her teenage goth phase and how The Cure saved her, what it was like being a therapist with TWO Masters Degrees, the circumstances of marrying and divorcing her first husband and SO much more! PLUS, obvi, we answer YOUR advice questions! If you'd like to ask your own advice questions, call 323-524-7839 and leave a VM or just DM us on IG or Twitter!Support the show on Patreon (two extra exclusive episodes a month!) or with a t-shirt (or a Jewboo shirt) and check out clips on YouTube! And why not leave a 5-star review along with the your wedding nightmare story on Apple Podcasts? (Every once in a while we'll do a Twitch show, if you want to also follow us there). Plus! Check out Andy's old casiopop band's lost album! And discounted Couples Therapy Quarantine Crew t-shirts here (if you don't get one, we're gonna have A LOT of nightshirts over at the ol' Beckperigin household!)! Hosted on Acast. See acast.com/privacy for more information.

Et kys har vendt op og ned på spansk fodbold. Allerede inden kysset indtraf var der konflikt og meget dårlig stemning. Kvindelandsholdet skændtes med både træner og fodboldforbund. De blev kaldt forkælede og truet med udelukkelse fra VM-truppen. Men alligevel går de på banen og vinder det hele. Og midt i jublen står præsidenten for deres eget fodboldforbund så klar med uønskede kys, klap og kram. Radiovært og medstifter af fanklubben for Kvindelandsholdet, Amalie Bremer, fortæller om den spanske fadæse, og hvad de spanske fodboldkvinder er oppe imod. Vært: Anna Ingrisch.

VM i Transschack, kast med liten bok i Rosengård och drogliberala Linnéa Bali slår till igen.Mejla in dina frågor till: inaktuellt@podplay.seLyssna på Inaktuellt Live VARJE torsdag från kl 09:30 på Podplay.se eller i Podplay-appen för att lyssna och ställa frågor direkt till Jonas, Hasse Brontén och producenten Dawwa.

In this episode of Road Trippin', Richard and Channing make a compelling case for why they believe LeBron's record for points will NEVER be broken. They break down the math, considering factors like age, injuries, and the overall talent level of future players to determine that they believe nobody will ever reach the same heights as LeBron James. The crew also returns to their game of Truth or Trash, and dives deep into whether or not they think Giannis Antetokounmpo will be a member of the Milwaukee Bucks in two years. Have a question or topic for our next show? Text or leave us a VM at 657-522-5578 (6575-CALLRT) Cheers! ► YouTube!

Veckopanelen med Paulina Neuding, Emil Källström och Jonas Lundgren under ledning av Staffan Dopping. Ännu en vecka i koranbränningarnas tecken, med hårda ordväxlingar om huruvida aktionerna är religionskritik eller ska etiketteras som hat och hets. Utrikesminister Tobias Billström anser att en lagändring är nödvändig när "rikets säkerhet är satt ur spel". Migrationsministern talar om skärpta regler för återvändande. Nobelstiftelsen bjuder in både Jimmie Åkesson och Rysslands ambassadör i Sverige, vilket verkar leda till serieavhopp från Nobelfesten. Och hur mycket betyder en ovälkommen VM-kyss? Hosted on Acast. See acast.com/privacy for more information.

Veckopanelen med Paulina Neuding, Emil Källström och Jonas Lundgren under ledning av Staffan Dopping. Ännu en vecka i koranbränningarnas tecken, med hårda ordväxlingar om huruvida aktionerna är religionskritik eller ska etiketteras som hat och hets. Utrikesminister Tobias Billström anser att en lagändring är nödvändig när "rikets säkerhet är satt ur spel". Migrationsministern talar om skärpta regler för återvändande. Nobelstiftelsen bjuder in både Jimmie Åkesson och Rysslands ambassadör i Sverige, vilket verkar leda till serieavhopp från Nobelfesten. Och hur mycket betyder en ovälkommen VM-kyss? Hosted on Acast. See acast.com/privacy for more information.

Der var glæde og jubel, da det spanske kvindelandshold vandt VM i fodbold. Men glæden er for mange blevet erstattet med vrede og protester, efter præsidenten for Spaniens fodboldforbund, Luis Rubiales, valgte at fejre sejren ved at kysse en af spillerne på munden. Kysset har antændt en ophidset debat om Spaniens mandsdominerede machismo-kultur og udstillet, hvordan Spanien er splittet mellem progressiv politik og fasttømrede familieidealer. Når vi taler om ødelæggelsen af regnskoven, fokuserer vi oftest på Amazonas. Men faktisk er skovrydningen langt voldsommere på det afrikanske kontinent, og i de seneste år er den bare accelereret yderligere. Så hvorfor sker fældningen af Afrikas skov under vores radar? Gæster: Svend Rybner, forfatter og historiker og Peder Frederik Jensen, forfatter. Tilrettelæggelse: Elise Normann og Sven Johannesen. Vært: Kirstine Dons Christensen. Lyddesign: Malte Winter Bothe. Redaktør: Tine Møller Sørensen.

Vi snakker med professor Bent Rønnestad om å starte intervalldragene hardere enn man avslutter, bolklegging av hardøkter og innlagte spurter på rolige langturer. Forskning og praksis på øverste nivå i sykkel gir positive svar på dette. Er det noe for løpere også? Kristian er storfornøyd med hvordan han trener om dagen, mens Jann prøver å holde kroppen i gang i VM-byen Budapest. På løpetur traff han Bernard Lagat og fikk et løpende intervju med legenden som er den eneste som har vunnet 1500m og 5000 m i samme VM. Mesterskapets første dager er selvfølgelig oppe til diskusjon sammen med to lytterspørsmål. Og ukas økt ble gjennomført som siste hardøkt av en VM-løper langs Donau. Hør episoden i appen NRK Radio

Andreas Mogensen er ombord på rumstationen. Eller er det et filmstudie i Værløse? Kommende interviews planlægges grundigt.Månedens medarbejder kåres. Åbenbart...Breinholt har været til VM i badminton. Lund Madsen blærer sig med Lene Køppens autograf. Vi ringer til Poul-Erik Høyer (og hans kæreste). For hvad sker der egentlig med maskot-ænderne efter stævnet? Er de til salg? Samtalen tager en uventet drejning.Og husk: Man skal ikke skue hånden med hårene, før hunden rigtig har bidt dig.Hvis du vil høre hele afsnittet, så kom over på Podimo. Her finder du et godt tilbud på 30 dage gratis! Brug det her link, så lyttes vi ved på Podimo: https://go.podimo.com/dk/andersogandersKærlig hilsen Anders og Anders

On this episode, the 9th Annual NFL Preview Show with host Nick Dais being joined by George Carmona, Jared Smith and Josh Willams! NFC East (10:00) NFC South (34:00) NFC West (51:00) NFC North (1:16:00) NFC Playoff Seeds (1:48:00) Ad Break And Shoutout To Our Sponsors (1:54:00) League Leaders (1:58:00) AFC North (2:07:00) AFC West (2:25:00) AFC South (2:40:00) AFC East (2:54:00) AFC Playoff Seeds (3:21:00) Yearly Awards (3:24:00) AFC/NFC Title & Super Bowl Champion (3:28:00) Guests: George Carmona Jared Smith Josh Williams Special Thanks To Our Sponsors! We've got a special deal for our listeners: Try BlueChew FREE when you use our promo code VM at checkout--just pay $5 shipping. That's BlueChew.com, promo code VM to receive your first month FREE. Visit BlueChew.com for more details and important safety information, and we thank BlueChew for sponsoring the podcast. @FlyMeOut Imagine if LinkedIn, AirBnB, and RAYA had a travel-loving baby. Whether you're looking to network with professionals on a beach or bond with creatives in the heart of a city, FlyMeOut has got you covered. Dive into curated experiences, and with their platform, it's never been easier to find your tribe and see the globe. Don't just travel, make memories with FlyMeOut! UseCode VM1 for expedited application review. Wager Attack Are you ready to take your sports betting game to the next level? Look no further than Wager Attack, the ultimate online Sportsbook for true sports enthusiasts. With a wide range of sports, live betting options, competitive odds, and a live casino. Wager Attack is where winners play. Join today using code VM and get bonuses & free play rollovers when depositing at the cashier  Wager attack is rocking with us through the NFL season & is the official odds provider of VM” Learn more about your ad choices. Visit podcastchoices.com/adchoices

In this episode of Road Trippin', Richard and Channing dive into a heated debate: Magic Johnson vs. Steph Curry, who is the true king of point guards? They discuss the stats, accolades, and impact of both players, offering their own perspectives and engaging in some friendly roasting along the way. But the conversation doesn't stop there. They also tackle the topic of NBA champions being called "world champions" and share their thoughts on the players they would put on their NBA Mount Rushmores. Don't forget to leave your comments and let us know who you think is the greatest point guard of all time! #RoadTrippin #NBA #MagicJohnson #StephCurry #Debate Have a question or topic for our next show? Text or leave us a VM at 657-522-5578 (6575-CALLRT) Cheers! ► YouTube!

Naomi first heard Gearóid Farrelly on sister-podcast (???) Ask Ronna, and introduced him into the household where we fell in love with him, and so we had to have him on the show! Now, maybe you are a listener across the pond, can you know Gearóid from his stand-up, his award winning Edinburgh Festival show, supporting Joan Rivers on tour, or from his podcast Agony Rants? Well, even if you don't know Gearóid from Adam, you're gonna go gaga for him after today's episode! We talk about his love of convenience, how his relationship with his boyfriend works, the Irish medical system & mental health, grief, and so much MORE! PLUS, obvi, we answer YOUR advice questions! If you'd like to ask your own advice questions, call 323-524-7839 and leave a VM or just DM us on IG or Twitter!Support the show on Patreon (two extra exclusive episodes a month!) or with a t-shirt (or a Jewboo shirt) and check out clips on YouTube! And why not leave a 5-star review along with the worst person you ever dated on Apple Podcasts? (Every once in a while we'll do a Twitch show, if you want to also follow us there). Plus! Check out Andy's old casiopop band's lost album! And discounted Couples Therapy Quarantine Crew t-shirts here (if you don't get one, we're gonna have A LOT of nightshirts over at the ol' Beckperigin household!)! Hosted on Acast. See acast.com/privacy for more information.

We're kicking off Season 7 with containers! Spinning up a VM may not be such a big deal anymore; however, most of us still have to request from another group one and wait. Even waiting on an Azure VM can be somewhat painful. Wouldn't it be nice to forget about setting up another development environment just to test something that isn't going to stick around? Our guest today is Chuck Bryan, and he talks to us about how he is using containers to support his environments and the flexibility it provides to him in his development. While the Linux containers used to get lots of love, there haven't been too many feature updates lately as much of the focus is on azure services. What is cool to me is there are tools out there that can help us folks running windows get up and running without having to wait on our infrastructure to upgrade to Windows server 2016--or have Azure spend. Chuck gives us some insights on how he got started with containers. We discuss what environments might benefit from them--and which ones won't. He also gives us a couple of tips on the best places to get started. The show notes for today's episode can be found at Episode 266: Working With Containers. Have fun on the SQL Trail!

Angie finally watched Pokemon: Detective Pikachu and also throws a little shade at James and Jon.  When she's not talkin' shit, she's been playing TOTK and the original Dead Space.  Chris has been playing the game that must not be named (it rhymes with Larval Slap) as well as KOTOR.  On news, they talk about GamesCom opening night and Green Bay getting a new development studio! If you want to be a part of the conversation or if you have a pressing question that you want us to weigh in on… You can reach us on twitter @mngamerspodcast. If you don't use twitter you can send email the old fashion way to ⁠podcast@mostlynormalgamers.com⁠. Sign up for our new newsletter, Mostly Normal Monthly at mngamers.substack.com! Back issues can be found there too!  Text or VM to (507) 291-2991. VOD on the Mostly Normal Gamers YouTube channel (https://www.youtube.com/@mostlynormalgamers6377) Jon Swanson @jonnysamsonite Chris Stern @vgoccasion Angie @stellarsmalls James Halliday @buttlordprimus --- Send in a voice message: https://podcasters.spotify.com/pod/show/mostlynormalgamers/message

Millioner af mennesker har fulgt det netop afsluttede VM i atletik i Ungarns hovedstad. Og premierminister Viktor Orban brugte anledningen til at pleje venskaber; på gæstelisten var blandt andre emiren af Qatar og præsidenterne fra Tyrkiet, Azerbaidjan, Kirgisistan, Uzbekistan og Turkmenistan - mens ikke én eneste leder fra et EU-land var inviteret. Så er Ungarn ved at isolere sig endegyldigt fra resten af Europa? I Ecuador har befolkningen ved en bemærkelsesværdig afstemning stemt for at stoppe olieudvindingen i regnskoven, selv om det vil gå ud over landets indtægter. Viser den her afstemning, at befolkningen kan være mere progressive end politikerne, når de selv får lov til at bestemme over deres naturressourcer? Gæster: Rasmus Nørlem Sørensen, sekretariatsleder og chefanalytiker i oplysningsforbundet DEO og Stine Krøyer, antropolog ved Københavns Universitet. Tilrettelæggelse: Henrik Lerche og Elise Normann. Vært: Kirstine Dons Christensen. Lyddesign: Malte Winter Bothe. Redaktør: Morten Narvedsen.

The latest In Touch With iOS with Dave he is joined by guest Chuck Joiner, Jeff Gamet, and Ben Roethig. We talk about Apple Pencil alternatives and then Jeff geeks out how he uses it. eSIM is the way to go on iPhone now with the physical SIM finally being retired? In Touch with MacOS we talk about Sonoma Beta 6 and the new release of Parallels 19 VM with Touch ID support.  The show notes are at InTouchwithiOS.com 
Direct Link to Audio  Links to our Show Click this link Buy me a Coffee to support the show we would really appreciate it. intouchwithios.com/coffee  Another way to support the show is to become a Patreon member patreon.com/intouchwithios Website: In Touch With iOS YouTube Channel In Touch with iOS Magazine on Flipboard Facebook Page Mastadon Twitter Instagram News Apple Will Soon Send Payments in $500 Million 'Batterygate' iPhone Throttling Lawsuit T-Mobile's 'Go5G Next' Plan Lets Customers Upgrade Smartphones Every Year Samsung's 'Try Galaxy' Feature Uses Two iPhones to Demo Z Fold5 Experience and hers is the link to experience it on the iPhone. https://trygalaxy.com/ Apple Support App Now Offers More Info on Nearby Locations Good news for podcast creators. Apple Podcasts Launches New Subscription Analytics Dashboard Apple Pay to Support U.S. National Park Foundation This Week  Tesla App Update Adds Over 20 Apple Shortcuts Actions Threads Social Network Expands to the Web    Topics Beta this week. iOS17 Beta 7 was released this week. Apple Seeds Seventh Betas of iOS 17 and iPadOS 17 to Developers [Update: Public Beta Available] Apple Seeds Seventh Beta of watchOS 10 to Developers Apple Seeds Seventh Beta of tvOS 17 to Developers Everything New in iOS 17 Beta 7 eSIM. What is it and do we think a physical SIM days are numbered? Well they are in the iPhone. Plus How to travel with an eSim iPhone What is an Integrated SIM (iSIM)? Is it better than eSIM? Are there any good alternates to Apple Pencil? ZAGG's new Pro Stylus 2 takes on Apple Pencil with magnetic charging and five fun colors and Jeff geeks out on how he uses his Pencil.  Astropad Debuts Screen Protector and Apple Pencil Tip for a Realistic Paper Feel on iPad In Touch with MacOS Segment MacOS Sonona Beta 6 was released. Apple Seeds Sixth Beta of macOS 14 Sonoma to Developers Dave uses Parallels Desktop  to keep virtual machines available, most notably Windows 11. Parallels release version 19 this week and we discussed its new improvements and features. Parallels Desktop 19 Adds Password-Less Sign-In With Touch ID Support, macOS Sonoma Compatibility, and Mor Apps GoodNotes 6 Brings AI-Powered Handwriting Spellcheck and Autocomplete Features - MacRumors Macstock 7 is in the books for 2023. Purchase a virtual pass to see Dave, Brittany, Chuck, and Jeff and their presentations.  Our Host Dave Ginsburg is an IT professional supporting Mac, iOS and Windows users and shares his wealth of knowledge of iPhone, iPad, Apple Watch, Apple TV and related technologies. Visit the YouTube channel https://youtube.com/intouchwithios follow him on Mastadon @daveg65, Twitter @daveg65.and the show @intouchwithios   Our Regular Contributors Jeff Gamet is a podcaster, technology blogger, artist, and author. Previously, he was The Mac Observer's managing editor, and Smile's TextExpander Evangelist. You can find him on Mastadon @jgamet as well as Twitter and Instagram as @jgamet  His YouTube channel https://youtube.com/jgamet Ben Roethig Former Associate Editor of GeekBeat.TV and host of the Tech Hangout and Deconstruct with Patrice  Mac user since the mid 90s. Tech support specialist. Twitter @benroethig  Website: https://roethigtech.blogspot.com About our Guest Chuck Joiner is the host of MacVoices and hosts video podcasts with influential members of the Apple community. Make sure to visit macvoices.com and subscribe to his podcast. You can follow him on Twitter @chuckjoiner and join his MacVoices Facebook group.

chippen har bytt livsstil och kallat Malin Wollin för en fegis. K har försökt få sin dotter att älska honom med ord. Perseus Karlström var med om ett mardrömslopp i VM i "trav" En spansk fotbollschef fick sparken efter sitt övertramp att kyssa en spelare på munnen Och så får vi höra två personer från Kristianstad tala med varandra. Missa inte årets standup-show K och chippen åker på en turné med start 8 oktober underproduktion.se/biljetter

Levi McCormick, Cloud Architect at Jamf, joins Corey on Screaming in the Cloud to discuss his work modernizing baseline cloud infrastructure and his experience being on the compliance side of cloud engineering. Levi explains how he works to ensure the different departments he collaborates with are all on the same page so that different definitions don't end up in miscommunications, and why he feels a sandbox environment is an important tool that leads to a successful production environment. Levi and Corey also explore the ethics behind the latest generative AI craze. About LeviLevi is an automation engineer, with a focus on scalable infrastructure and rapid development. He leverages deep understanding of DevOps culture and cloud technologies to build platforms that scale to millions of users. His passion lies in helping others learn to cloud better.Links Referenced: Jamf: https://www.jamf.com/ Twitter: https://twitter.com/levi_mccormick LinkedIn: https://www.linkedin.com/in/levimccormick/ TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. A longtime friend and person has been a while since he's been on the show, Levi McCormick has been promoted or punished for his sins, depending upon how you want to slice that, and he is now the Director of Cloud Engineering at Jamf. Levi, welcome back.Levi: Thanks for having me, Corey.Corey: I have to imagine internally, you put that very pronounced F everywhere, and sometimes where it doesn't belong, like your IAMf policies and whatnot.Levi: It is fun to see how people like to interpret how to pronounce our name.Corey: So, it's been a while. What were you doing before? And how did you wind up stumbling your way into your current role?Levi: [laugh]. When we last spoke, I was a cloud architect here, diving into just our general practices and trying to shore up some of them. In between, I did a short stint as director of FedRAMP. We are pursuing some certifications in that area and I led, kind of, the engineering side of the compliance journey.Corey: That sounds fairly close to hell on earth from my particular point of view, just because I've dealt in the compliance side of cloud engineering before, and it sounds super interesting from a technical level until you realize just how much of it revolves around checking the boxes, and—at least in the era I did it—explaining things to auditors that I kind of didn't feel I should have to explain to an auditor, but there you have it. Has the state of that world improved since roughly 2015?Levi: I wouldn't say it has improved. While doing this, I did feel like I drove a time machine to work, you know, we're certifying VMs, rather than container-based architectures. There was a lot of education that had to happen from us to auditors, but once they understood what we were trying to do, I think they were kind of on board. But yeah, it was a [laugh] it was a journey.Corey: So, one of the things you do—in fact, the first line in your bio talking about it—is you modernize baseline cloud infrastructure provisioning. That means an awful lot of things depending upon who it is that's answering the question. What does that look like for you?Levi: For what we're doing right now, we're trying to take what was a cobbled-together part-time project for one engineer, we're trying to modernize that, turn it into as much self-service as we can. There's a lot of steps that happen along the way, like a new workload needs to be spun up, they decide if they need a new AWS account or not, we pivot around, like, what does the access profile look like, who needs to have access to it, which things does it need to connect to, and then you look at the billing side, compliance side, and you just say, you know, “Who needs to be informed about these things?” We apply tags to the accounts, we start looking at lower-level tagging, depending on if it's a shared workload account or if it's a completely dedicated account, and we're trying to wrap all of that in automation so that it can be as click-button as possible.Corey: Historically, I found that when companies try to do this, the first few attempts at it don't often go super well. We'll be polite and say their first attempts resemble something artisanal and handcrafted, which might not be ideal for this. And then in many cases, the overreaction becomes something that is very top-down, dictatorial almost, is the way I would frame that. And the problem people learn then is that, “Oh, everyone is going to route around us because they don't want to deal with us at all.” That doesn't quite seem like your jam from what I know of you and your approach to things. How do you wind up keeping the guardrails up without driving people to shadow IT their way around you?Levi: I always want to keep it in mind that even if it's not an option, I want to at least pretend like a given team could not use our service, right? I try to bring a service mentality to it, so we're talking Accounts as a Service. And then I just think about all of the things that they would have to solve if they didn't go through us, right? Like, are they managing their finances w—imagine they had to go in and negotiate some kind of pricing deal on their own, right, all of these things that come with being part of our organization, being part of our service offering. And then just making sure, like, those things are always easier than doing it on their own.Corey: How diverse would you say that the workloads are that are in your organization? I found that in many cases, you'll have a SaaS-style company where there's one primary workload that is usually bearing the name of the company, and that's the thing that they provide to everyone. And then you have the enterprise side of the world where they have 1500 or 2000 distinct application teams working on different things, and the only thing they really have in common is, well, that all gets billed to the same company, eventually.Levi: They are fairly diverse in how… they're currently created. We've gone through a few acquisitions, we've pulled a bunch of those into our ecosystem, if you will. So, not everything has been completely modernized or brought over to, you know, standards, if you will, if such a thing even exists in companies. You know [laugh], you may pretend that they do, but you're probably lying to yourself, right? But you know, there are varying platforms, we've got a whole laundry list of languages that are being used, we've got some containerized, some VM-based, some serverless workloads, so it's all over the place. But you nailed it. Like, you know, the majority of our footprint lives in maybe a handful of, you know, SaaS offerings.Corey: Right. It's sort of a fun challenge when you start taking a looser approach to these things because someone gets back from re:Invent, like, “Well, I went to the keynote and now I have my new shopping list of things I'm going to wind up deploying,” and ehh, that never goes well, having been that person in a previous life.Levi: Yeah. And you don't want to apply too strict of governance over these things, right? You want people to be able to play, you want them to be inspired and start looking at, like, what would be—what's something that's going to move the needle in terms of our cloud architecture or product offerings or whatever we have. So, we have sandbox accounts that are pretty much wide open, we've got some light governance over those, [laugh] moreso for billing than anything. And all of our internal tooling is available, you know, like if you're using containers or whatever, like, all of that stuff is in those sandbox accounts.And that's where our kind of service offering comes into play, right? Sandbox is still an account that we tried to vend, if you will, out of our service. So, people should be building in your sandbox environments just like they are in your production as much as possible. You know, it's a place where tools can get the tires kicked and smooth out bugs before you actually get into, you know, roadmap-impacting problems.Corey: One of the fun challenges you have is, as you said, the financial aspect of this. When you've got a couple of workloads that drive most things, you can reason about them fairly intelligently, but trying to predict the future—especially when you're dealing with multi-year contract agreements with large cloud providers—becomes a little bit of a guessing game, like, “Okay. Well, how much are we going to spend on generative AI over the next three years?” The problem with that is that if you listen to an awful lot of talking heads or executive types, like, “Oh, yeah, if we're spending $100 million a year, we're going to add another 50 on top of that, just in terms of generative AI.” And it's like, press X to doubt, just because it's… I appreciate that you're excited about these things and want to play with them, but let's make sure that there's some ‘there' there before signing contracts that are painful to alter.Levi: Yeah, it's a real struggle. And we have all of these new initiatives, things people are excited for. Meanwhile, we're bringing old architecture into a new platform, if you will, or a new footprint, so we have to constantly measure those against each other. We have a very active conversation with finance and with leadership every month, or even weekly, depending on the type of project and where that spend is coming from.Corey: One of the hard parts has always been, I think, trying to get people on the finance side of the world, the engineering side of the world, and the folks who are trying to predict what the business was going to do next, all speaking the same language. It just feels like it's too easy to wind up talking past each other if you're not careful.Levi: Yeah, it's really hard. Recently taken over the FinOps practice. It's been really important for me, for us to align on what our words mean, right? What are these definitions mean? How do we come to common consensus so that eventually the communication gets faster? But we can't talk past each other. We have to know what our words mean, we have to know what each person cares about in this conversation, or what does their end goal look like? What do they want out of the conversation? So, that's been—that's taken a significant amount of time.Corey: One of the problems I have is with the term FinOps as a whole, ignoring the fact entirely that it was an existing term of art within finance for decades; great, we're just going to sidestep past that whole mess—the problem you'll see is that it just seems like that it means something different to almost everyone who hears it. And it's sort of become a marketing term more so that it has an actual description of what people are doing. Just because some companies will have a quote-unquote, “FinOps team,” that is primarily going to be run by financial analysts. And others, “Well, we have one of those lying around, but it's mostly an engineering effort on our part.”And I've seen three or four different expressions as far as team composition goes and I'm not convinced any of them are right. But again, it's easy for me to sit here and say, “Oh, that's wrong,” without having an environment of my own to run. I just tend to look at what my clients do. And, “Well, I've seen a lot of things, and they all work poorly in different ways,” is not uplifting and helpful.Levi: Yeah. I try not to get too hung up on what it's called. This is the name that a lot of people inside the company have rallied around and as long as people are interested in saving money, cool, we'll call it FinOps, you know? I mean, DevOps is the same thing, right? In some companies, you're just a sysadmin with a higher pay, and in some companies, you're building extensive cloud architecture and pipelines.Corey: Honestly, for the whole DevOps side of the world, I maintain we're all systems administrators. The tools have changed, the methodologies have changed, the processes have changed, but the responsibility of ‘keep the site up' generally has not. But if you call yourself a sysadmin, you're just asking him to, “Please pay me less money in my next job.” No, thanks.Levi: Yeah. “Where's the Exchange Server for me to click on?” Right? That's the [laugh]—if you call yourself a sysadmin [crosstalk 00:11:34]—Corey: God. You're sending me back into twitching catatonia from my early days.Levi: Exactly [laugh].Corey: So, you've been paying attention to this whole generative AI hype monster. And I want to be clear, I say this as someone who finds the technology super neat and I'm optimistic about it, but holy God, it feels like people have just lost all sense. If that's you, my apologies in advance, but I'm still going to maintain the point.Levi: I've played with all the various toys out there. I'm very curious, you know? I think it's really fun to play with them, but to, like, make your entire business pivot on a dime and pursue it just seems ridiculous to me. I hate that the cryptocurrency space has pivoted so hard into it, you know? All the people that used to be shilling coins are now out there trying to cobble together a couple API calls and turn it into an AI, right?Corey: It feels like it's just a hype cycle that people are more okay with being a part of. Like, Andy Jassy, in the earnings call a couple of weeks ago saying that every Amazon team is working with generative AI. That's not great. That's terrifying. I've been playing with the toys as well and I've asked it things like, “Oh, spit out an IAM policy for me,” or, “Oh, great, what can I do to optimize my AWS bill?” And it winds up spitting out things that sound highly plausible, but they're also just flat-out wrong. And that, it feels like a lot of these spaces, it's not coming up with a plausible answer—that's the hard part—is coming up with the one that is correct. And that's what our jobs are built around.Levi: I've been trying to explain to a lot of people how, if you only have surface knowledge of the thing that it's telling you, it probably seems really accurate, but when you have deep knowledge on the topic that you're interacting with this thing, you're going to see all of the errors. I've been using GitHub's Copilot since the launch. You know, I was in one of the previews. And I love it. Like, it speeds up my development significantly.But there have been moments where I—you know, IAM policies are a great example. You know, I had it crank out a Lambda functions policy, and it was just frankly, wrong in a lot of places [laugh]. It didn't quite imagine new AWS services, but it was really [laugh] close. The API actions were—didn't exist. It just flat-out didn't exist.Corey: I love that. I've had some magic happen early on where it could intelligently query things against the AWS pricing API, but then I asked it the same thing a month later and it gave me something completely ridiculous. It's not deterministic, which is part of the entire problem with it, too. But it's also… it can help incredibly in some weird ways I didn't see coming. But it can also cause you to spend more time chasing that thing than just doing it yourself the first time.I found a great way to help it—you know, it helped me write blog posts with it. I tell it to write a blog post about a topic and give it some bullet points and say, “Write in my voice,” and everything it says I take issue with, so then I just copy that into a text editor and then mansplain-correct the robot for 20 minutes and, oh, now I've got a serviceable first draft.Levi: And how much time did you save [laugh] right? It is fun, you know?Corey: It does help because that's better for me at least and staring at an empty page of what am I going to write? It gets me past the writer's block problem.Levi: Oh, that's a great point, yeah. Just to get the ball rolling, right, once you—it's easier to correct something that's wrong, and you're almost are spite-driven at that point, right? Like, “Let me show this AI how wrong it was and I'll write the perfect blog post.” [laugh].Corey: It feels like the companies jumping on this, if you really dig into what we're talking about, it seems like they're all very excited about the possibility of we don't have to talk to customers anymore because the robots will all do that. And I don't think that's going to go the way you want to. We just have this minor hallucination problem. Yeah, that means that lies and tries to book customers to hotel destinations that don't exist. Think about this a little more. The failure mode here is just massive.Levi: It's scary, yeah. Like, without some kind of review process, I wouldn't ship that straight to my customers, right? I wouldn't put that in front of my customer and say, like, “This is”—I'm going to take this generative output and put it right in front of them. That scares me. I think as we get deeper into it, you know, maybe we'll see… I don't know, maybe we'll put some filters or review process, or maybe it'll get better. I mean, who was it that said, you know, “This is the worst it's ever going to be?” Right, it will only get better.Corey: Well, the counterargument to that is, it will get far worse when we start putting this in charge [unintelligible 00:16:08] safety-critical systems, which I'm sure it's just a matter of time because some of these boosters are just very, very convincing. It's just thinking, how could this possibly go the worst? Ehhh. It's not good.Levi: Yeah, well, I mean, we're talking impact versus quality, right? The quality will only ever get better. But you know, if we run before we walk, the impact can definitely get wider.Corey: From where I sit, I want to see this really excel within bounded problem spaces. The one I keep waiting for is the AWS bill because it's a vast space, yes, and it's complicated as all hell, but it is bounded. There are a finite—though large—number of things you can see in an AWS bill, and there are recommendations you can make based on top of that. But everything I've seen that plays in this space gets way overconfident far too quickly, misses a bunch of very obvious lines of inquiry. Ah, I'm skeptical.Then you pass that off to unbounded problem spaces like human creativity and that just turns into an absolute disaster. So, much of what I've been doing lately has been hamstrung by people rushing to put in safeguards to make sure it doesn't accidentally say something horrible that it's stripped out a lot of the fun and the whimsy and the sarcasm in the approach, of I—at one point, I could bully a number of these things into ranking US presidents by absorbency. That's getting harder to do now because, “Nope, that's not respectful and I'm not going to do it,” is basically where it draws the line.Levi: The one thing that I always struggle with is, like, how much of the models are trained on intellectual property or, when you distill it down, pure like human suffering, right? Like, this is somebody's art, they've worked hard, they've suffered for it, they put it out there in the world, and now it's just been pulled in and adopted by this tool that—you know, how many of the examples of, “Give me art in the style of,” right, and you just see hundreds and hundreds of pieces that I mean, frankly, are eerily identical to the style.Corey: Even down to the signature, in some cases. Yeah.Levi: Yeah, exactly. You know, and I think that we can't lose sight of that, right? Like, these tools are fun and you know, they're fun to play with, it's really interesting to explore what's possible, but we can't lose sight of the fact that there are ultimately people behind these things.Corey: This episode is sponsored in part by Panoptica.  Panoptica simplifies container deployment, monitoring, and security, protecting the entire application stack from build to runtime. Scalable across clusters and multi-cloud environments, Panoptica secures containers, serverless APIs, and Kubernetes with a unified view, reducing operational complexity and promoting collaboration by integrating with commonly used developer, SRE, and SecOps tools. Panoptica ensures compliance with regulatory mandates and CIS benchmarks for best practice conformity. Privacy teams can monitor API traffic and identify sensitive data, while identifying open-source components vulnerable to attacks that require patching. Proactively addressing security issues with Panoptica allows businesses to focus on mitigating critical risks and protecting their interests. Learn more about Panoptica today at panoptica.app.Corey: I think it matters, on some level, what the medium is. When I'm writing, I will still use turns of phrase from time to time that I first encountered when I was reading things in the 1990s. And that phrase stuck with me and became part of my lexicon. And I don't remember where I originally encountered some of these things; I just know I use those raises an awful lot. And that has become part and parcel of who and what I am.Which is also, I have no problem telling it to write a blog post in the style of Corey Quinn and then ripping a part of that out, but anything that's left in there, cool. I'm plagiarizing the thing that plagiarized from me and I find that to be one of those ethically just moments there. But written word is one thing depending on what exactly it's taking from you, but visual style for art, that's something else entirely.Levi: There's a real ethical issue here. These things can absorb far much more information than you ever could in your entire lifetime, right, so that you can only quote-unquote, you know, “Copy, borrow, steal,” from a handful of other people in your entire life, right? Whereas this thing could do hundreds or thousands of people per minute. I think that's where the calculus needs to be, right? How many people can we impact with this thing?Corey: This is also nothing new, where originally in the olden times, great, copyright wasn't really a thing because writing a book was a massive, massive undertaking. That was something that you'd have to do by hand, and then oh, you want a copy of the book? You'd have to have a scribe go and copy the thing. Well then, suddenly the printing press came along, and okay, that changes things a bit.And then we continue to evolve there to digital distribution where suddenly it's just bits on a disk that I can wind up throwing halfway around the internet. And when the marginal cost of copying something becomes effectively zero, what does that change? And now we're seeing, I think, another iteration in that ongoing question. It's a weird world and I don't know that we have the framework in place even now to think about that properly. Because every time we start to get a handle on it, off we go again. It feels like if they were doing be invented today, libraries would absolutely not be considered legal. And yet, here we are.Levi: Yeah, it's a great point. Humans just do not have the ethical framework in place for a lot of these things. You know, we saw it even with the days of Napster, right? It's just—like you said, it's another iteration on the same core problem. I [laugh] don't know how to solve it. I'm not a philosopher, right?Corey: Oh, yeah. Back in the Napster days, I was on that a fair bit in high school and college because I was broke, and oh, I wanted to listen to this song. Well, it came on an album with no other good songs on it because one-hit wonders were kind of my jam, and that album cost 15, 20 bucks, or I could grab the thing for free. There was no reasonable way to consume. Then they started selling individual tracks for 99 cents and I gorged myself for years on that stuff.And now it feels like streaming has taken over the world to the point where the only people who really lose on this are the artists themselves, and I don't love that outcome. How do we have a better tomorrow for all of this? I know we're a bit off-topic from you know, cloud management, but still, this is the sort of thing I think about when everything's running smoothly in a cloud environment.Levi: It's hard to get people to make good decisions when they're so close to the edge. And I think about when I was, you know, college-age scraping by on minimum wage or barely above minimum wage, you know, it was hard to convince me that, oh yeah, you shouldn't download an MP3 of that song; you should go buy the disc, or whatever. It was really hard to make that argument when my decision was buy an album or figure out where I'm going to, you know, get my lunch. So, I think, now that I'm in a much different place in my life, you know, these decisions are a lot easier to make in an ethical way because that doesn't impact my livelihood nearly as much. And I think that is where solutions will probably come out of. The more people doing better, the easier it is for them to make good decisions.Corey: I sure hope you're right, but something I found is that okay we made it easy for people to make good decisions. Like, “Nope, you've just made it easier for me to scale a bunch of terrible ones. I can make 300,000 more terrible decisions before breakfast time now. Thanks.” And, “No, that's not what I did that for.” Yet here we are. Have you been tracking lately what's been going on with the HashiCorp license change?Levi: Um, a little bit, we use—obviously use Terraform in the company and a couple other Hashi products, and it was kind of a wildfire of, you know, how does this impact us? We dove in and we realized that it doesn't, but it is concerning.Corey: You're not effectively wrapping Terraform and then using that as the basis for how you do MDM across your customer fleets.Levi: Yeah. You know, we're not deploying customers' written Terraform into their environments or something kind of wild like that. Yeah, it doesn't impact us. But it is… it is concerning to watch a company pivot from an open-source, community-based project to, “Oh, you can't do that anymore.” It doesn't impact a lot of people who use it day-to-day, but I'm really worried about just the goodwill that they've lit on fire.Corey: One of the problems, too, is that their entire write-up on this was so vague that it was—there is no way to get an actual… piece of is it aimed at us or is it not without very deep analysis, and hope that when it comes to court, you're going to have the same analysis as—that is sympathetic. It's, what is considered to be a competitor? At least historically, it was pretty obvious. Some of these databases, “Okay great. Am I wrapping their database technology and then selling it as a service? No? I'm pretty good.”But with HashiCorp, what they do is so vast in a few key areas that no one has the level of certainty. I was pretty freaking certain that I'm not shipping MongoDB with my own wrapper around it, but am I shipping something that looks like Terraform if I'm managing someone's environment for them? I don't know. Everything's thrown into question. And you're right. It's the goodwill that currently is being set on fire.Levi: Yeah, I think people had an impression of Hashi that they were one of the good guys. You know, the quote-unquote, “Good guys,” in the space, right? Mitchell Hashimoto is out there as a very prominent coder, he's an engineer at heart, he's in the community, pretty influential on Twitter, and I think people saw them as not one of the big, faceless corporations, so to see moves like this happen, it… I think it shook a lot of people's opinions of them and scared them.Corey: Oh, yeah. They've always been the good guys in this context. Mitch and Armon were fantastic folks. I'm sure they still are. I don't know if this is necessarily even coming from them. It's market forces, what are investors demanding? They see everyone is using Terraform. How does that compare to HashiCorp's market value?This is one of the inherent problems if I'm being direct, of the end-stages of capitalism, where it's, “Okay, we're delivering on a lot of value. How do we capture ever more of it and growing massively?” And I don't know. I don't know what the answer is, but I don't think anyone's thrilled with this outcome. Because, let's be clear, it is not going to meaningfully juice their numbers at all. They're going to be setting up a lot of ill will against them in the industry, but I don't see the upside for them. I really don't.Levi: I haven't really done any of the analysis or looked for it, I should say. Have you seen anything about what this might actually impact any providers or anything? Because you're right, like, what kind of numbers are we actually talking about here?Corey: Right. Well, there are a few folks that have done things around this that people have named for me: Spacelift being one example, Pulumi being another, and both of them are saying, “Nope, this doesn't impact us because of X, Y, and Z.” Yeah, whether it does or doesn't, they're not going to sit there and say, “Well, I guess we don't have a company anymore. Oh, well.” And shut the whole thing down and just give their customers over to HashiCorp.Their own customers would be incensed if that happened and would not go to HashiCorp if that were to be the outcome. I think, on some level, they're setting the stage for the next evolution in what it takes to manage large-scale cloud environments effectively. I think basically, every customer I've ever dealt with on my side has been a Terraform shop. I finally decided to start learning the ins and outs of it myself a few weeks ago, and well, it feels like I should have just waited a couple more weeks and then it would have become irrelevant. Awesome. Which is a bit histrionic, but still, this is going to plant seeds for people to start meaningfully competing. I hope.Levi: Yeah, I hope so too. I have always awaited releases of Terraform Cloud with great anticipation. I generally don't like managing my Terraform back-ends, you know, I don't like managing the state files, so every time Terraform Cloud has some kind of release or something, I'm looking at it because I'm excited, oh finally, maybe this is the time I get to hand it off, right? Maybe I start to get to use their product. And it has never been a really compelling answer to the problems that I have.And I've always said, like, the [laugh] cloud journey would be Google's if they just released a managed Terraform [laugh] service. And this would be one way for them to prevent that from happening. Because Google doesn't even have an Infrastructure as Code competitor. Not really. I mean, I know they have their, what, Plans or their Projects or whatever they… their Infrastructure as Code language was, but—Corey: Isn't that what Stackdriver was supposed to be? What happened with that? It's been so long.Levi: No, that's a logging solution [laugh].Corey: That's the thing. It all runs together. Not it was their operations suite that was—Levi: There we go.Corey: —formerly Stackdriver. Yeah. Now, that does include some aspects—yeah. You're right, it's still hanging out in the observability space. This is the problem is all this stuff conflates and companies are terrible at naming and Google likes to deprecate things constantly. And yeah, but there is no real competitor. CloudFormation? Please. Get serious.Levi: Hey, you're talking to a member of the CloudFormation support group here. So, I'm still a huge fan [laugh].Corey: Emotional support group, more like it, it seems these days.Levi: It is.Corey: Oh, good. It got for loops recently. We've been asking for basically that to make them a lot less wordy only for, what, ten years?Levi: Yeah. I mean, my argument is that I'm operating at the account level, right? I need to deploy to 250, 300, 500 accounts. Show me how to do that with Terraform that isn't, you know, stab your eyes out with a fork.Corey: It can be done, but it requires an awful lot of setting things up first.Levi: Exactly.Corey: That's sort of a problem. Like yeah, once you have the first 500 going, the rest are just like butter. But that's a big step one is massive, and then step two becomes easy. Yeah… no, thank you.Levi: [laugh]. I'm going to stick with my StacksSets, thank you.Corey: [laugh]. I really want to thank you for taking the time to come back on and honestly kibitz about the state of the industry with me. If people want to learn more, where's the best place for them to find you?Levi: Well, I'm still active on the space normally known as—formerly known as Twitter. You can reach out to me there. DMs are open. I'm always willing to help people learn how to cloud better. Hopefully trying to make my presence known a little bit more on LinkedIn. If you happen to be over there, reach out.Corey: And we will, of course, put links to that in the [show notes 00:30:16]. Thank you so much for taking the time to speak with me again. It's always a pleasure.Levi: Thanks, Corey. I always appreciate it.Corey: Levi McCormick, Director of Cloud Engineering at Jamf. I'm Cloud Economist Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice, and along with an insulting comment that tells us that we completely missed the forest for the trees and that your programmfing is going to be far superior based upon generative AI.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.