Tariffs hit Enterprise Cloud || Tech Field Day News Rundown: June 4, 2025

AI application Delivery. Victoria has a big secret inferring at the edge. VMware's partner purge Walmart using AI for automation.

Quantum might break RSA faster than we thought. And we're gonna take a closer look at the impact on tariffs and cloud computing. And this week's episode of the Tech Field Day Rundown.

Hello everyone, and welcome to the Tech Field Day rundown. Today is Wednesday, June the fourth. My name is Tom Hollingsworth, and I'm very glad to be back from Super Secret Security Field Day.

Uh, and it's a very important day. It's a national hug your Cat Day, also known as Wise. Is this Cuis and Arc trying to kill me?

Um, you know, it's, you take the good, you take the bad, right? Um, hugging a cat is always an exercise in restraint on somebody's part. Uh, but luckily I am not restrained in welcoming my new co-host for this episode.

Mr. Brad Gregory. Brad, welcome to the show.

Tom, great to see you again. It's been a while. Good to see You.

It is, and we're very glad to have Brad joining us on National Cheese Day. But I promise you the only thing cheesy around here is the day the news is very important, and we've got some great stories coming up. The first one that I wanna launch into is about AI and inferencing, because AI inferencing and networking isn't about using AI to manage the network.

It's about delivering AI workloads with the same precision, scalability, and resilience that we apply to modern application delivery. Inferencing is really just another demanding workload that thrives on optimized load balancing, latent sensitivity, routing, and secure edge delivery. And Brad, this is something that I know is near and dear to your heart.

So why don't you give us a little bit of background into why you think that AI is really just another workload and not something super special that's gonna revolutionize the way that networking packets are sent? Yeah, thanks, Tom. Because in fact, that's what it is, right?

Uh, I think we've spent so much time in, in, uh, talking about training, talking about how, you know, we knew the alters and that consortium and how we have to do all these things different for training. Uh, it's totally different networks. We have to learn new things, um, uh, and, and rightly so, right?

I mean, you gotta train it before you can put it out there for everybody to, to consume. Um, and then, and then we move to inferencing, right? Uh, inferencing, it's still kinda like, uh, old networking, but, but with a few tweaks, right?

The, the network's gonna have to behave function a little differently. Um, so there, there's a lot to learn in the inferencing, uh, in the training space. There's some to learn in the inferencing space, but I would argue there's not a whole lot to learn in the application delivery space, right?

We've been talking so much about training, so much about inferencing, but even at that inferencing is just the front door, right? I, I've gotta have, uh, just like a web server was the front door for applications, right? You, you, you've, you gotta have something to serve, uh, the, the, the trained models up.

So, uh, once I started digging into it, uh, more, uh, and trying to figure out, okay, what does the application delivery look like? It became pretty obvious that it looks like what it's always looked like, right? I, I've got a load balance to it.

Um, I, I've gotta look at the context of what I said to it, to load balance on the backend. You know, when load balance was first starting many, many years ago, they were pretty rudimentary load balancers. Then, uh, they started getting a lot more sophisticated.

Uh, and then they became application delivery controllers. So when I look at, um, how we, um, offer up AI applications to users, it's simply application delivery. You have to, you know, think about a couple little tweaks.

You know, in the old days it was SQL injection, uh, attacks that got you in trouble. Now it's prompt injection that'll get you in, uh, attacks that will get you in trouble. Um, you wanna load balance to different models based on the, what the prompt sent, right?

So if you type in, um, you know, how do I write some something in Python, then maybe load balance me to LAMA instead of, you know, claw, for example, right? So I think just the, the, uh, the availability, the contextual information, sending me to the correct, uh, resource on the backend, uh, how do I secure? It sounds a lot like what we've been doing for the last 25 years, right?

Since low balance really, really came to the fore. So, um, so not a lot think, think old, old is new again, and just apply those same principles. And I think, uh, the application delivery aspect for AI will be easier to understand and easier to wrap your hands around.

Not so much for training and kind of, kind of for inferencing. You, you, you know, a lot of the old still applies with inferencing, but, uh, but a lot of the old really applies for, um, application delivered, uh, Victoria's Secret, I heard they had a pretty long weekend last week. They spent a lot of time fighting a security incident, took their website offline for almost, uh, four days.

Uh, customers, uh, attempting the shop were greeted with a pink screen telling 'em the site was offline due to an issue that was being addressed. Details surrounding the event have been dis disclosed, but there were some communications issues between the website team, the PR team, as the website at one point disclosed the nature of the security breach, while the PR team released a statement said it was an upgrade gone wrong. Your thoughts.

So there's two things to think about here. The first thing, which is kind of the important thing is always make sure that your PR team and security team are on the same page when they talk about what's going on. Because if the PR team is like, oh yeah, we tried to, you know, fix PHP and something broke, sorry, no big deal.

And the website team this that's working with security team is like, oh yeah, it was a breach. Like, one of those things is no big deal. Although it would've really been hard to justify it being an upgrade that was, you know, took your website off for four days.

Um, but security thing is gonna get everybody's attention. And that's kind of what happened last week, was that everybody noticed that this was, it, it actually started happening kind of like Sunday, but it wasn't until we got into the hours of Monday that, that everything went offline. Here's the second thing though.

You've gotta read between the lines a little bit because of course they're not ready to disclose exactly what happened. And they may not tell us the exact story, but they took the website offline and you couldn't order anything. And I've heard from some sources, according to Reddit and other places, that a lot of what was going on in the stores was also offline.

It's like you couldn't order things that were not already on the shelves and stuff like that. That to me says there was a breach of the ordering system, and they probably got some PII of the users probably credit card data. That's what my worry is.

Um, the only reason you would not immediately disclose what was going on is if it involves something that's massively PII, in this case, P-C-I-D-S-S, um, impacts. Uh, you got credit cards, that's a problem. Why are you even storing credit card data?

Well, I know because you click little boxes says remember this for, for future stuff. But, um, you know, they're gonna have to sort this whole thing out. There's probably gonna be some impacts with their customer base.

Um, realistically speaking, I don't know if this's gonna be huge impact or not, because one of the things we've seen over the last few months and years is that ultimately, uh, customers are brand loyal. So they're gonna probably come back to buy things here. I mean, it's not like you have a ton of options to shop for.

Um, and especially ones that have local storefronts, uh, you know, like I can ship it to the store or whatever, especially if you feel uncomfortable having things like that shipped to your home. But I think that, that they're gonna have to actually come out and say what it was like, they, they can't play this game anymore. I think really what they're doing is they're trying to get their ducks in a row so that they know if there's going to be, you know, um, charges filed or some kind of a class action lawsuit, um, that they're ready to fight it.

Um, so sorry if you couldn't buy some fun stuff last week, uh, but, you know, as Marshall Stacker, Pentecost always says, you know, reset the clock because it's just gonna be another breach before you know it. And, and next time it might not be something nearly so fun. Brad, there's some new reporting out that discusses the likelihood that AI inferencing is gonna be huge for Edge computing, uh, per this report.

Doing inferencing on the edge reduces time and costs for transferring data in and out of cloud storage, as well as lowering latency for decision making. And by doing all of the work on the compute edge, you can reduce huge cloud overhead costs. I know how much it costs to spin up and Amazon instance, and it ain't cheap anymore.

Um, also one of those little side benefits to all those of us in the security space is the fact that you can be relatively certain, you know, where that data is, so you don't have to worry about data sovereignty issues. Uh, I guess the question that I have for you, Brad, is should we be looking at moving all of our AI inferencing data out to the edge instead of loading it all in the cloud? Yes, probably.

Um, you know, I think for the longest time we've been looking for that Edge killer app, right? The, um, and it, the edge has been kind of a nebulous term, but I think, um, uh, inferencing could be the killer app that, uh, that the Edge is looking for, for a couple of reasons. One is, you know, um, users a lot more dispersed than they used to be.

You know, not everything happens around the major major metros. Uh, and then two, um, there, uh, just from a, a standpoint of space power cooling, you know, uh, you can't really build that many ash, uh, data centers around Ashburn anymore. So, um, you'll see training can be done anywhere and inferencing needs to be pushed out closer to the, to the users that are, are literally anywhere now, right?

So, um, and then two, um, it's hard to do everything in the cloud because you've got a lot of data that means a lot to you that's proprietary or that sovereign that you wanna, you know, you know, you wanna keep close to the vest. So, um, you know, I think you'll start seeing things like, uh, rack retrieval, augmentation generation, uh, federated AI things where that, that, uh, that the trained data or the data that will be presented back to you will be a combination of, uh, a foundational public model, uh, with your own individual tailored data, you know, for, uh, or, or your own data that's tailored to your, to your needs. Uh, you know, that's the retrieval augmentation generation, right?

I'm gonna, I'm gonna send a query out there. Some part of it will come from the foundational model that's more public. Some part of it will become, uh, will come from your data that that's more private.

Put those two together and, you know, I've got an augmented, uh, or augmented response, it comes back to you. So, um, that's one great use case where I think, uh, inferencing at the edge as it as it applies to ai, specifically in the rack context, in the federated AI context, might be the killer app that the Edge has been looking for for quite a few years. Now, if you're a registered partner of VMware by Broadcom, we've got some bad news.

The company's eliminating the lowest partner tier. Completely existing partners have 60 days to either move up or move on. According to Lori Falco head of Global Partner programs, the vast majority of these partners are inactive and lack capabilities to support customers.

This means VMware by Broadcom has three partner tiers, pinnacle, premier, and select. These tiers will now have increased requirements to maintain the relationship, including dedicated sales and support personnel. Analysts are suggesting that the move could force smaller customers away from VMware in the future.

So here's my problem with this. Um, we just got through with this whole big bruhaha about VMware's partner program, right? They wanted to take their top thousand or 2,500 accounts private inside of VMware.

They've been slowly pushing everyone to be selling only VMware Cloud Foundation. Um, there's no essentials bundles anymore. What did they think the natural outcome of this was going to be Like?

I know a lot of people who were registered as VMware partners that really only resold to a couple of places, like, you know, maybe themselves and a couple of other local partners. Well, if you don't have a foundations bundle to sell anymore, like, like if that was the reason why you registered, this makes total sense, right? We're cutting out the people on that low end to the comment by Lori Falco.

Yes. If there's nothing for them to sell, then they're all gonna be inactive, right? Like we, we've been doing the stance for the last year and change of, you know, what's, what's gonna be available?

How can we do this? And any partner program worth its salt is gonna say that you have to have people who are trained on the solutions that are trained in the way that they need to be sold and to go out there and do it. And I think that this could potentially be the carrot for some of those larger organizations that are trying to look to differentiate themselves to be able to offer these solutions, right?

It's like if you go out and you dedicate personnel to being able to do this, if you kind of follow our guidelines for selling VMware Cloud Foundation, if you, you know, have a high attach rate, you know, maybe we'll toss you some of these bigger partners so that you know, you can continue to maintain the relationships you have with them. 'cause I have a funny feeling what's happened is that a lot of those large partners, uh, had really good relationships. And when VMware came knocking without the partner, the companies were like, well, I'd rather deal with the people that I know.

And so I think this is kind of pushing back on the partners. However, I I, I do agree with some of the analyst talk. If you're cutting people out completely, then the first thing they're gonna wanna do is say, screw you.

And they're gonna go sell somebody else. Now, I don't necessarily know that that's gonna work the way that you think it's gonna work. Um, I think ultimately what's gonna end up happening is that Amazon and Nutanix are gonna gain, and then the rest of everybody is going to, um, you know, they're gonna be picking up the pieces.

I don't know what this means for VMware customers, but I promise you it's probably time to start thinking about what your migration strategy is gonna be. 'cause you're either gonna be moving to Cloud Foundation, or you're gonna be moving to something that's not VMware, right? Walmart is using a new approach to AI by focusing on small tasks, specific agents instead of large all-in-one platform systems.

These AI agents handle specific jobs like data entry or even speeding up product design, which is leading to clear improvements in how the company runs. Uh, Walmart also combines multiple agents to manage much more complex tasks like their smart shopping assistant, which uses both in-house and external AI models. This focus strategy makes AI a lot easier to scale and a lot more cost effective, and it could serve as a model for other businesses looking to improve automation.

Um, Brad, does Walmart's approach to maybe smaller discrete AI agents instead of one big behemoth? Make a lot of sense considering that Walmart is kind of the behemoth in the retail space. Uh, yeah, it does.

You know, a lot of agents are a good thing. A lot of agents can be a bad thing too, right? That, that's a lot of, uh, that's a lot of crosstalk that's gonna happen.

That needs to be secured. It needs to be, um, you know, probably thought about in a little different way. And it kind of goes back to the discussion we were having a minute ago, right?

This is just another way to talk about, um, you know, it's, it's just retrieval augmentation generation on a grand, grand scale, right? Instead of having, you know, one master model talking to a, a tailored model, you can have all these models talking to each other, right? You know, what in the future, what would dictate a model?

Is it one agent? You know, is what what is a small language model at some point, right? Um, so I think once, uh, yes, that's the power, right?

I mean, you get a lot of intelligence out there and a lot of data points, and they all come together and they start, um, you know, the, the collective power of all those data points to come together to give you one, um, one retrieval. Augmented generated AI output is really the power of any system, right? It's kinda like MetCast Law in motion.

You know, the, the power of the system is, is vastly, exponentially more powerful. The, the more agents are talking to each other, the more, you know, connections are talking to each other. So I think this might, um, you know, agents talking to each other will be the what interconnection has been for the last, you know, decade or 15 years, right?

The, the power of getting people to talk directly to each other, peer to peer, you know, I think the agents is just the agents. Uh, AI agents are just the next iteration of that. And it's powerful, also dangerous, uh, new study from Google quantum AI shows that breaking the 2048 bit rs a encryption may require far fewer quantum resources than once thought.

Instead of 20 million cubits, the task could now be done with under a million noisy cubits in about a week. While today's quantum computers aren't powerful enough, yet, this major drop in requirements highlight just how quickly quantum computing is advancing. Since RSA is widely used to secure data, the finding fresh, the urgent need to switch to quantum safe encryption to protect against future threats.

Your thoughts, This is the same old problem that we know we've had ever since sneakers came out, right? Is we know that eventually someone will create a computer that is strong enough to instantly factor primes and, and be able to figure out these keys. And honestly, even in a million cubits, you're still looking at days to break any one specific RSA encrypted key.

And the problem that I have with this is, yes, it's an attention grabbing headline, but you have to understand something. The most powerful quantum computer on the planet right now from Google has about 1100 qubit capacity. You need a million to even consider this.

And notice that it said a million noisy qubits. So for those of you who may not have seen my conversation about this, one of the problems that we have with quantum computing is just the amount of noise that's generated. You have to have lots of cubics to solve every potential permutation of the equation.

And then you have to find that equation. That's why error correction is so important to quantum computing. And if you can get the right amount of error correction, you can significantly reduce the number of qubits that you need to brack break any particular key.

The problem is, even with the leaps and bounds that we've had over the last few years, we're still nowhere near as powerful as we need to get, even with exponential growth. We've still got several more years before we get there, but we already have candidate keys that are quantum resistant, that use lattice based encryption technologies, which is really difficult for quantum computers to break. And for those of you out there who are on the crypto chain, you don't have to worry about Bitcoin being broken anytime soon because that whole proof of work thing and elliptical curve technology make it a lot harder to break than, than just if it was just a simple, and I say simple, uh, RSA 2048 bit key.

The the issue is, is that we really do have to be looking at what the likelihood is, is that we either are gonna need to re-encrypt the data that's already at rest that is insecure, or that we're gonna need to, you know, basically remove it and then move on to these more resistant keys. But I'll tell you, this is not the first time, the second time, or the 15th time we solved this problem. I can go back to just about any hashing or encryption algorithm that was weak in the past, that is effectively broken today.

And we saw we've had these problems forever. The, the key is that we always have to be one step ahead of where we're at. And we did that whenever we submitted those candidate keys to the, uh, to NIST to be, um, authorized.

I mean, I, I don't remember what they got named, they're just numbers now, but, you know, it was di lithium and, uh, kyber and all the rest of them because they're solving the problem that we have, and they're doing it early enough that we're not like falling all over ourselves to implement fixes that will eventually cause problems. See, also the Y 2K problem, like that was admittedly a herculean effort, but it was very late. We should have been way ahead of that.

And here I think we are. And what we're seeing out of this is people that are starting to ask the right questions, not just how can I encrypt this data, but is this data that I should be keeping, that I'm going to need to encrypt? And I think that that is a better question to be asking.

'cause if we can, if we can stop storing so much data, then it's less likely that the encryption that we're using is gonna be broken. Alright, we had a story we wanted to take a closer look at. And undoubtedly, if you have been watching the news at all, you are familiar with tariffs because they are the thing that has been dominating the economic talk.

Well, new global tariffs are making it more expensive and complicated for enterprises to manage their cloud services across regions changes are causing wildly unpredictable costs and creating challenges for organizations that wanna adopt a global cloud strategy. And in order to stay ahead of that, companies are gonna need to improve visibility. They're gonna need to automate processes, and they're gonna tailor their governance to each region.

Now, what I think is funny is, is that we've been talking about data sovereignty issues for years, right? Where is my data located? How is it being accessed?

And those are security questions. So they're not that big of a deal, right? We'll solve them.

But now that we're seeing that those data sovereignty issues are coupled with economic considerations such as the price of certain resources in, uh, in instances being wildly higher because of additional, uh, tariffs not just, uh, demand. Uh, now suddenly the people who didn't care about data sovereignty care about their pocketbook. So, Brad, I'm gonna let you start off on this.

Um, what is it about this that's causing people consternation? Is it just the fact that there's a tariff on cloud computing, uh, incidentally, or is it more that they're worried that this could create asymmetrical demand? You know, that's a good question.

I, I think what's causing all of us consternation is you don't know what it's gonna be, right? If, if, if a tariff rate was locked in at X percent over the next 12 months, 18 months, and that was the new agreement, then you could say, okay, we, we have some certainty. We know how to work around it, right?

I think what's frustrating is, uh, is just the whiplash of the tariff rate itself. Do I refactor applications? Do I, do I adopt as a service instead of, you know, or, or do I adopt, uh, opex instead of CapEx?

It, it's the unknown. Um, just like everybody else, the the, uh, it industry's not insulated from it because to your point, we're all, uh, you know, economics is driving everything behind the scenes. So I think, I think just the unknown, not knowing what to do is very, very frustrating.

If you had something to deal with, like, we dealt with supply chain issues and, uh, during COVID, right? You knew it was gonna take quite a while to, you know, to, to get, you know, whatever piece of hardware you were working with. So you, you figured out ways around it.

You, you figured out a way to get to the other side of the supply chain problem. Um, what is the other side of this problem? I don't think anybody knows yet.

'cause nobody knows what the rates are gonna be. Nobody knows, you know, um, what agreements are gonna be signed. Nobody knows who's gonna be at the table, who won't be at the table, who's gonna pay a bigger price, uh, you know, than the others.

So the uncertainty, it manifests itself in so many ways, right? It just paralyzes everything It does. And, and I'm gonna say two words that I think everybody gets tired of hearing is chilling effect, right?

But this is absolutely something that you need to take into account when you look at what's going on. People don't make decisions on the spur of the moment, even when it comes to something admittedly as ridiculous as spot pricing for cloud instances, right? Like, that is the number one thing that I've always heard that people wanna use multi-cloud for is arbitrage.

Um, this, AWS instance is expensive for the next three and a half hours. So I'm gonna move it over to, to Azure, and I'm gonna run it in Azure because they've got a discount on storage or whatever. Who knows what it's, you're, you're playing around with the money.

But what you're doing that's more important is, is you are forcing people into making specific decisions for their workloads that exclude other areas. So for example, if there is a tariff on importing cloud computing workloads into a specific country, then I'm gonna craft my policy so that I don't import those into that country no matter what. And it's one thing if, if the tariffs are asymmetrical, right?

Like one country has higher tariffs for certain things, but lower tariffs for other things, the problem ultimately is going to be that companies are just gonna throw their hands up in the air and say, I'm gonna go where it makes the most sense, where it's the most stable and I'm going to stay there. Because that's the other thing. If this was just a blanket tariff across the entire organization and we didn't have to worry about things moving too much, then I could maybe see like, maybe I'll raise the prices to my customers.

I'll eat some of this. But what we're seeing is whiplash, right? One day we have a tariff, the other day we don't, but maybe we might have another one in the future.

We don't know yet. It's up to the whims of whoever's putting the tariff in place. I can't plan my organization around how somebody wakes up in the morning and decides that they want to do things.

And this goes against every classical economic definition of a tariff that you've ever seen, right? Tariffs are considered to be protectionists, and that's why I don't understand why this is happening, right? Like, why would you put a blanket tariff on everything?

Like, if you're trying to be protectionist about things like industry, you'd put a tariff on finished goods, but not on raw materials to encourage people to import raw materials into your country and produce finished goods. Here, it's a little bit different when it comes to cloud computing, which is why I don't understand it. It'd be like saying, I, I'm gonna put a, a tariff on storage but not compute because I want you to do the work but not save the data.

And by putting a blanket on everything, then they're just gonna say, okay, well we're gonna stay in this instance over here. And if cloud computing companies like Amazon, Microsoft, Google, Oracle, IBM, whomever are really smart about this, what they're gonna do is they're gonna offer instances that are local, but are not impacted by this. And that is gonna cause a lot of these global organizations to realign a little bit differently.

And what you're gonna get out of it is effectively islands of data out there in the cloud that can never move. So you're gonna have to be more robust in the way that you build your applications because you can't just migrate from Reston to Corvallis and hope that US East or US West one is up instead of us East one. And I don't know that that's something that developers are really prepared to do right now.

Well then you, everything you're we're talking about is in the context of hardware, you know, physical asset. What about when tariffs, you know, they've talked about applying tariffs to services, right? So if, if you have services, if you wanna buy services to refactor or rewrite applications to get around a hardware tariff, right?

Or, or an asset tariff, what, what does that look like? You know, it, so it's almost like this matrix of tariffs that you have to apply in, you know, this three dimensional chess, uh, matrix. And it's like, I don't know how people are gonna gonna figure it out.

You know, again, certainty, bad certainty is better than no certainty, right? And I, I just, we, we don't even have bad certainty right now. It's just uncertainty on top of uncertainty, it changes.

They, I don't, you know, yeah, a very, very tough time on so many levels to try to figure out what you wanna do with your org and what you wanna do with the technology based on the, the way the stuff is coming at you in so many directions. Well, there may not be a lot of certainty around that, but I can tell you one thing that I am absolutely certain of, and that is Tech Field Day, because we have great events that are coming up over the next couple of weeks that you're gonna want to tune in for. One of them is happening now.

com, you can check out Cloud Field A 23 where we're talking about some of the very same things that we just discussed in this episode. Uh, Alistair Cook is out in San Francisco. He's talking to some great companies.

com. You can tune in for the live stream, but you can also check out the list of presenters. Uh, you're not gonna wanna miss that.

And then I am gonna be winging my way to California at the end of the week because I am gonna be at Cisco Live next week. We're gonna be hearing great presentations from Open Gear, Cisco and Avi. com for more details and the presentation schedule.

And then I'm gonna take like a week off and maybe enjoy the weather, okay? I'm not, it's, I'm kidding. It's summer.

I'm not gonna enjoy the weather, but I'm gonna be back in July after Independence Day. We're gonna be back with Networking Field Day 38. We've signed some really great companies.

In fact, we just signed a couple of them this week. com and learn more details about who's gonna be there presenting, who's gonna be there as a delegate, uh, I encourage you to do that. But I also encourage you to check out some of Brad's stuff.

So Brad, if people wanna learn more about what you do and see some of your writing, where can they go to do that? Yeah, thanks. Uh, LinkedIn's a good sp uh, place.

I'll put 'em out on LinkedIn. com, which is, uh, my consulting company. So yeah, I would love to get people's feedback.

Um, and if, if there's a subject you wanna delve into, uh, let me know. I'd be glad to research and write a blog out there for the, for the larger community to, to consume. So thanks Tom.

Absolutely. And we want to thank h and every one of you for watching this episode of The Tech Field Day Rundown. Remember that we post new episodes every Wednesday.

Uh, we post them on YouTube. So if you wanna subscribe to the Tech Field Day plus YouTube channel, you can check that out. You can also subscribe to us in your favorite podcast application of choice.

Just look for the Tech Field Day rundown, and we're streaming it on Techstrong TV as well. Don't forget that there is now a Techstrong TV app for your tablet phone, and your set top box. So if you want to have us up running in the background or maybe program it at your dentist office, we would love to, uh, bore the kiddos with all of this great tech talk.

I mean, they may not even need, uh, laughing Gas anymore. Uh, don't forget that we can, you can also catch us on your other tech strong and future and group properties, um, because we always pop up and we always have fun things to say. We're gonna be back next Wednesday.

Well, somebody will be, because I'm gonna be in San Diego. I'm gonna be out there with a, a beach chair and, and trying to avoid the sun, actually. Uh, but there will be great co-hosts here for the rundown.

And, um, we will be talking about all of the great IT news that has come out over the last week. Until then, for myself, Tom Hollingsworth, and for my great cohost, Mr. Brad Gregory, thanks for tuning in For the rundown.

Go eat some cheese and give that cat a hug for us. We'll see you next week.