2023 Predictions and Hopes

Episode 250 · Tue, 13 Dec 2022 14:05:52 +0100 · 37:56 · SRT · archive.org · all Tanzu Talk

Well, this episode, you know, I think it's going to be the last episode we do this year, at least that I know of, you know, we'll see if it's not. And we come across one that is scheduled that I don't show up for. I didn't know about it. So I hope this is it. So I thought we would do the classic thing in a format that I think will be more palatable for us to do it. And that is, we'll do not only some predictions for next year, and just in case you're listening to this in the future, 2023 next year, I'll let the listener do an exercise to figure out what year this is. And, and not only that, like I have to do these prediction thing have to, I am asked to participate in prediction stuff frequently. But I thought what we could also do is the our hopes and dreams, because the prediction is sort of like, you know, what the real prediction for next year always is, is probably pretty much the same thing that happened last year. That's, that's, that's the kind of, that's, I've tried to get away with that over the years sometimes. And people don't like that. But it is fun to say what your hopes and dreams are. So I thought we would come to that. And so we have, of course, the three of us are here, Coté, Ed, and Ben. And I thought I would invite our friend, ChatGPT, to also give some of its predictions. So I've asked it, I will do it last, since it's not human, and it can't be insulted. But the prompt that I had for it is, can you write a 2023 predictions piece? It should be predictions for CIOs at large organizations, paying attention to what's happening with cloud, low code and security. So we'll get to what ChatGPT thought for a while, I fed it a little more things to kind of prime its pump, as it were. But I'll start off since I sort of gave this to you two, about a few minutes ago. So now you can think of something. So here is, you know, my sort of easy projection of predictions, and it's a little bit of hopes and

dreams, we'll do hopes and dreams in the second round, is I think that there will be much evolution of the platform engineering idea. Because I think, you know, to go over it slightly, I think it more or less, you know, it was kicked off long ago, when when Spotify, several years ago, released its backstage thing, and started developing this notion of an internal developer platform, which is really just to put it in a brief snarky way, an evolution of the Atlassian portfolio, with a few more things, but it does seem like prime to kind of like, replace that. I don't know if that's good or bad. But that's, that's a, that's a question I was asking, you know, one of my analyst friends who cover software development, Bola, in a Twitter thing is like, maybe I wasn't this direct, but I was like, shouldn't Atlassian be doing this? So I don't know, we'll find out. But I think just, you know, as far as like an internal portal or collaboration thing for developers, it's really evolved into sort of like, here's like, a framework, or a platform, if you will, for building like, this is not the right thing. So this is the other thing is we need language for this, but the single pane of glass, that developers would use for existing in their inner developer community, right? In other words, the internet that developers use, but behind their own firewall, and there's all sorts of stuff going on there. Plus, you bring in all of the stuff of actually running the platform, which I'm still not quite sure if that's part of platform engineering, as we know it nowadays, or if that's what the site reliability engineering people do. We've got to sort that out, right? Because I feel like I should go back and talk to the people in our community who have been doing this, excuse me, for a while, and see if they have time to actually run and troubleshoot the platform while they're treating their developers as customers and building their stuff. I kind of suspect that's a lot to ask for one team.

But we'll see. Of course, unless they're using Cloud Foundry available in the Tanzu application service, in which case, they can eliminate the need to run a lot of their stuff. Hopefully, that will be the case with the Tanzu application platform as well, especially now that there is a Cloud Foundry like interface on top of it. But whatever, we'll see. We'll see how that evolves. But yeah, I think there's enough interest in platform engineering now. And I think people are over the hump of getting Kubernetes up and running that hopefully, finally, will coast back into the developer layer of the stack and see how that goes. So I think the way to test this out will be, one, that idea is used more. But whenever the next round of talking about platform engineering comes, whether it's the conference that Humanitech puts on or just kind of at DevOps days or in conferences, there should be a lot more talks from like big end users about what they've been doing there. So that's my one prediction. How about Ed? I'll just say, so I can paraphrase your prediction, Ed. It's not the same as last year. We are indeed going back to 2000-ish. So we need a developer intranet and developers and ops are going to go back to being developers and ops. Am I right there? We're sort of undoing everything, right? We've put stuff in and now we're like, you know what? We do need operations teams. There's operations teams, whatever we call them. But it's more than the web ones. That would be a great panel. Maybe we should, you know, people don't like the word webinar, but what are you going to do? That maybe I should propose like a webinar panel. We can bring maybe some, not outsiders, whatever, but maybe it could only be VMware people. And we'll say like, so is dev and ops going to be separate? Or we should say, practically speaking, are dev and ops as we know it actually separate? And, you know, that would be the whole prompt,

right? Because of course, you've got to have like 30 minutes of setting up context and nuance and it depends and all of that, which we can maybe just edit out of the recording because that stuff's always boring. But it is, I think that is a question that largely has been unresolved. There was that time, y'all must remember, when would this have been? Maybe even five or four years ago when Gartner came out with its bimodal IT thing and the DevOps people just freaked out. Like that was the last time I think this, we were allowed to ponder this question. But then the DevOps people came in and just like carpet bombed that whole notion. And you're not really allowed to think about it anymore, which is unfortunate. But yeah, I think a good summary. Now, what do you think? What's your prediction for 2023 yet? Which I've had to think of five. So I don't have any great predictions. Let's go with, it will be the year of edge. I'm actually not convinced it will be in a way, but you know, Oh, that's good. It's leaking ever nearer. It's a bit like, you know, the year of the desktop, isn't it? Or the year of Linux or whatever it's going to be sort of Linux on the desktop. Edge has been talked about for what, probably six, seven years at least, as that was going to be the inflection away from centralized clouds, hyperscalers, having everything on cloud. Actually, edge meant it was going to go back towards some on-prem, some more distributed cloud. Now there's cloud, all these different things. But I haven't seen a huge amount of it in a way. Lots of people had edge and then it kind of went away. Then people have tried to get their taxonomies of what edge is, thin edge, thick edge, all these different bits. And you are starting to see sort of more products, especially in the Kubernetes area, you know, lightweight versions of Kubernetes. But it still doesn't feel like it's gone as sort of mainstream as everyone said it would. Maybe that's just me, right? I'm sitting in a vendor. I'm not out there in factories and retail. I know it's all there, but I still just haven't quite seen it as the big thing it was meant to be. I wonder if I'm talking about it five years from now. I like that because I think using my funny thing of what's going to happen next year is more of what

happened this year. I feel like this past year, and you probably read about it more than I do, but I finally have figured out that edge isn't just some goofy marketing thing. And to personify it, I think that edge has figured that out. My sense is that there was a long time where edge was like, part of the 5G PR initiative, right? And then maybe like cars or something. But then I think what happened is there's an old category that when I was at Dell, we would delightfully called robo, which is remote office branch office. And I think maybe that's been pulled into edge. And then we have a few use cases. Well, I don't know if it's named or not, even though it's a named customer of ours, so I won't name them. But there are certain, as they say, logistics companies that use edge stuff in warehouses, right? And so I think there is an appreciation of edge. I think Kelsey Hightower had a tweet that edge just is a new word for private cloud, or whatever. But I think maybe what it means is small, not public cloud cloud, which is fine, right? It's totally cool. And I think how I came to accept this category of edge of not being just some goofy thing is that like there is a category of like a small data center, whether it's in a car or like a office that is something, right? And if you run it in a cloud native style, it's different than just older systems that it's probably worth thinking of that as a category because it probably has its own unique needs and constraints. And therefore, pardon another marketing term solutions that it requires.

That's my recap of your prediction. There we go. That's fair enough. So more of it and still no clear, is it the year of edge or not? No, I'm near of a bit more of it. Yeah. Edge reach escape velocity. Edge escape jumps over the edge. You don't want to jump over the edge because that implies you fall down. I don't know. How about yourself, Ben? What's a prediction for next year? I want to riff on what you were talking about, really. I think consolidation is my prediction. And what I'm hoping will get consolidated is the various aspects of things that have gone before. So we had we had the whole platform as a product thing. And I think the consolidation that I'm hopeful about is that developers, security and ops do kind of coalesce around a common sort of platform, common way of doing things. That's why I'm that's why I'm so invested in the in the Tanzu application platform, because I really believe in that vision. And I think that we're starting to see this sort of the roots of that in more discussion of platform engineering. So, you know, having developers being able to use a single pane of glass based around backstage, which everybody seems to really like, I really like it. I'm looking forward to learning more about it. Also having, you know, supply chains in the mix. I think that's really useful as well. You know, so we can try and cut back on some of the sprawl that we've seen around things like build pipelines, but also add in there the extra stuff that is required around security as well. So, so sort of having DevSecOps, but as part of platform engineering and and where it's consolidated and and unified around a vision of the world that helps folks to just get stuff done more easily. So I'm really looking forward to that. And I think

next year will be the, I'll be a really good year for that sort of stuff. I think it will be, it will hopefully accelerate and we'll, we'll pick up some pace and we'll, we'll also pick up some folks who, who share that vision as well. I like that. Like, I think there's a common thread in, in, in our three things, if I can try to common thread it, if that's a verb. And that is like, boy, can we stop the analysis and just build the stack, right? Like in, in the sense of like, there's all of these different components or definition of what edge is. And like, it'd be nice to, uh, try to hop over to use the diffusion of innovation, you know, Gartner hype cycle thing. Like let's, uh, let's use the, the upward, you know, ramp to just get to that plateau of productivity and just start working on stuff rather than spending all this time sorting out what, uh, what works and doesn't work. And, you know, I, I had to, I had to say, Ben, as maybe you're, uh, uh, it's not our fiscal year isn't over yet, but calendar year 2022, uh, performance review. I think you've been doing a great job, Ben, like just finding all these little parts of our stack and big parts and making, uh, educational videos about them. I think it's, it's nice. Like the, uh, the backstage one recently was, was impressive. I, I can tell you spend a lot of time on that because like me, it didn't take you two hours to explain like, uh, uh, you know, 10 different things and demo it. It was well thought out. That's, that's, that's, and the reality was that there weren't many hours spent on that. So I was feeling for someone else. Ah, that's the best way to do it then. So I got sort of, yeah, it was a very deep end sort of thing, but I am, I have only scratched the surface there and I am really looking forward to, uh, to going deeper. Just before we, we started talking on this show, I was working on, um, I was working with someone else on a script that have some videos that they're going to produce around, uh, backstage. And, and there's so much debt, there's so much more to say about it. I, I only scratched the surface in that,

in that last video. So I'm looking forward to doing more of that for sure. Yeah. Yeah. Yeah. I'm, I'm, I'm, you know, I'm, I've learned over the last 20 odd years, I should never promise anything that I'm going to do in the future. Uh, that's, that's always terrible, but like, I, I think it'll be good to get some more, uh, backstage talk on, on this. Cause I think it is like, you know, a good platform for building stuff out or, you know what? I don't even know if it's technically good. I'll have to take people's words, but it seems to be what people want to do, which, which is as, as someone who only makes slides, that's what I care about. Uh, so that's, that's, we have that. All right. So as promised, let's check in with our friend chat GPT and see what their prediction, uh, for the years now, part of the prompting that I did, as I said, you know, it could use some forecasting from Forrester and Gartner about things. And as, as is a good disclaimer with all chat GPT things, I did not actually go fact check any facts that it's included. So it could have totally made this up, but you know, maybe, maybe, uh, you know, you probably have a sense for this stuff, Ed, maybe you can do some casual fact checking. Now it is prediction piece that wrote, you know, that obligatory first paragraph of just nonsense, which is good, good job for it, but let's, let's go to it. I like its little style here. Uh, first let's talk about the cloud. According to recent forecasts from Gartner and Forrester, the global cloud market is set to continue its rapid growth with spending on cloud services and expected to exceed 500 billion by 2023. Again, I don't know if that's true or not. This growth is driven by a number of factors, including the increasing popularity of cloud-based collaboration and productivity tools, the rise of remote work and growing demand for cloud-based data and Linux and machine learning. I still don't know what it's predicting CEOs at large organizations must be prepared for this continual growth in cloud and must consider how they can take advantage of it to improve their own operations. Additionally, they must consider investing in cloud-based data, Linux data analytics and machine

learning. So it really hasn't made a prediction. It's just saying what you should do. And I must say, however, the accuracy of this prediction, I think according to our rule is probably 100% because this is basically what you should have done last year as well. So I used to write essays like this in high school and I would get a solid B plus because the notes from the teacher would say, very well reasoned, but this was not what I asked you to do. So we'll give this prediction a B plus. All right. Well, so the next round is the old hopes and dreams, which I have learned when you write a predictions piece, this is what you actually need to kind of weasel your way into writing because no one wants to predict stuff. You just want to tell people what your hopes and dreams are. And I think I think, I think my hopes and dreams for our space is, I mean, I've already alluded to a little bit, but I think it would be great. And I mean, I'm kind of, I'm coasting off what you were saying here a little bit, Ben, but I think it would be great if we started to standardize a lot of the stuff in the stack. Right. And like, and, and what we've seen, I believe is that all the container-based stuff and the infrastructure layer for people who care about applications development. I mean, I don't think there was a vote or anything taken, but like, everyone's basically like, yeah, we're going to use Kubernetes for that. And even, even if it's not the case, like, I mean, last I checked, I think estimates about the total number of workloads that are running on Kubernetes is something like, I don't know, 10 or 15%. I guess it depends how you count it. If you're counting like sheer processes, it might look different than if you count applications, who knows? But for example, I saw a, um, an estimate from IDC that there's like 500 million legacy applications running in the world. So I assume there's at least 500 million applications that

are not running in Kubernetes. I don't know. My point being that it seems like people have agreed that Kubernetes is the way of the future. However, I don't think there's much consolidation about what the overall platform looks like, nor even what the language that we use is. So it'd be great if there was further, just like, oh, we're just going to use this way of doing stuff instead of kind of like debating a bunch of different, uh, things for it, you know, even having the language of what we would call application lifecycle management or the software delivery lifecycle, whatever all those tools are. I mean, I really hope it's not going to be internal developer portal, because not only does that sound horrendously boring, but it has the word portal in it, uh, which is just like, I don't know. I've made this joke before, but I think if people, whoever is using the word portal clearly didn't live through Java enterprise stuff in the 2000s, uh, because you, you would never use the word portal again after that. Uh, it just, you know, I don't even like to say it, or maybe, maybe the video gamers though, Coté, you know, portal, amazing video game, right? Oh, okay. Okay. I guess, I guess maybe since the days of J2EE, there has been a, a, a deep cultural acceptance of sci-fi time travel and fantasy nerd culture, it's, it's gone mainstream. And so maybe the word portal now has very positive associations to it because it's like a portal into fun and enjoyment and even culture. And so, uh, I'm, I'm just the old here. No, it's just the game. That was the only good tip. Yeah. Doctor Strange would be hella boring without portals, right? That's true. And that, that, you know, I, I think, I think that, uh, that Spider-Man movie with, with the, the time travel and the dimensions, that was pretty good. So portals are good, just not in the actual IT world. Yeah.

All right. Well, how about yourself, Ed? What's your hopes and dreams for, for calendar year 2023? Funnily enough, I was thinking along very similar lines, because I was going to say, I just want to be able to push a button and have everything work. You know, I'm kind of fed up in a way of, I do bits of hands-on work and it's like, I've got to figure this, sort that and sort this. And there's just tons and tons of it. And occasionally, especially when you want to get your marketing and your slides done, right? Which I always do as well. But this is just a chore. This is a pain. And there's eight different versions of that. I want to try out and learn. So I was like, I just kind of want that to get simpler. But on the other side of it, actually, I would get bored if that happened. I've actually loved the last few years, because there was a point when I did get very bored of IT. And I mean, we're going back 20 years or something. So probably pre vSphere and things in a way, but it was like, hey, there's another version of Windows, whatever. There's another version of it. There's no excitement at all that. Another smooth upgrade. How boring. Yeah. Exactly. Actually, you know, the last, whatever it's been, five, six years, more than that in a way, there was suddenly a load of new stuff. And the whole cloud native thing, at least for me, has been a really good journey of learning new technologies. There's a wealth of stuff. There's always more to learn, but it got me more engaged. And now it's platform engineering and there's a whole layer that goes on top. So once you scratch that little itch of, I need to know about Kubernetes, it's like a Mandelbrot set. There's an infinite amount to learn. And my kind of geek brain likes that. I like having new stuff. I can go also that area over there. And you know, it distracts me from my work, even that kind of ease work. So I could spend weeks learning about backstage when actually I need to know the top 10 things and that might be it. But, um, so yeah, my hopes and dreams, I suppose, more of the complexity, but I don't get fired for not doing the right things. That's, that's, yeah, I like that last part. That's, that's always my, that's my constant hope and dream always. But, you know, you know, you're reminding me of like, I don't know if it's a theory, but this thought that I have in the back of my head. And since, since, you know, in, in your area, you, you, uh, week to week cover closely everything that's going on in the cloud native space.

And, uh, you know, you're evolving the theory I have in my head. And this, this, this, this line of thought is that it's kind of impossible to cover like the cloud native space because you can't just like spin up your own lab to actually like compare and contrast different cloud stuff. Like if you are, it just, it wouldn't be economically feasible to compare the different Kubernetes distros for private or edge. Like, how would you even do that? Right. And, and therefore it's just like the way that, for example, analysts and others cover that stuff is, I mean, the first word that popped in my head was fraught, but it's really hard. Like all you can go off is like your intuition and what people have told you, like, I don't know. It's, it's different than like testing out word processors. Right. And however, what you're saying does get me thinking that like, this is an area where public cloud theoretically could be different because that's the whole point of public cloud is you can do that like very easily. And so it's almost, it almost makes it extremely difficult to compare public cloud to like private cloud cloud native stuff. Because a lot of the times, if you were like, I got to write this report, it's got to be out in like three days or a week. And it's going to take me that long. I mean, like, and that means that I need to basically test the stuff out in a day, because then I got to think about how to write this stuff up. Then I need several rounds of edits. Then it's got to go into like frame maker to do the formatting. And then I got to do the final proofing. And so like, I basically have a day to test this stuff out and you can't do that. So it's, I don't know, difficult. I mean, you know, AWS probably have 120 releases a day. It's just infeasible to keep up with one, let alone three, six, 10, 100 different companies releasing things, different projects, which is

great, right? That's what keeps my brain going. But it's getting very hard to do. It's sort of a very noisy environment, compared to previously, you kind of just knew it's three main options and the rest are irrelevant. That's right. So, so, so Ben, when you, when you're not experiencing a smooth upgrade, what, what are your hopes and dreams for the, for the coming year? I, I really hope this is the year of the Linux desktop, specifically known desktop. Oh, wow. Going deep. I'm going deep. So I've been using Linux known for a long time now. It must be like nearly two years or so. So, so I've, so I've done the trifecta. I've done the windows. I've done macOS and now I'm on Linux, uh, known, known desktop, uh, with Fedora hat tip to our friends with the red hats, uh, for, uh, for, uh, for creating that. And, and I love it. Right. And the reason I love it is because I think every developer should experience it. And the reason I say that is because the known desktop is so productive, it's ridiculous. It's much more productive than Mac desktop. It's much more productive than windows desktop. And you get access to all the tools that are already running 99% of the cloud. So why you would come out of that ecosystem for the sake of a desktop baffles me. You might as well give it a try. So if you haven't tried it, please go and try it. Give it a try next year, make it your new year's resolution to give known desktop a try because, uh, it's very, very, very productive. And I think as we care about developer productivity, we should also care about which desktop environment they're using and not having to jump through as many hoops to, uh, to do their work. So try it. I think you'll like it.

That's, that's a good one. I like that. You know, what I think about this every now and then I used to use, I don't remember which windowing manager, but some X windows thing way, way back when. And the, the, the, the number one thing, at least that I remember that I miss is, is you could set up the exact layout, like pixel perfect of all your windows and like save that. And then basically like, you know, every time you would, you would start again, it would just like open up all your windows exactly where you wanted them. And I don't know, maybe there's a way to do that on, on the Mac, but like, it's definitely not built into the system as, as far as I could tell, let alone like some text file, I could just move around and putter with, but yeah, that was good stuff. If you want to revisit those heady days, Coté, then you could try, uh, I think there's a Fedora spin with the i3 window managing desktop in there. So there's no regular desktop, just i3 window manager. And you get exactly, I think what you're describing. So yeah, you could relive those heady days. Uh, for me, that would probably mean going back to when I had hair. I'm not sure I want to do that. Uh, a different type of heady day. Hair was a fact. I seem to remember paying people to cut it. I seem to style it into various different shapes. Uh, you know, uh, usually laboring under the, uh, uh, you know, idea that somehow it made me more attractive. Uh, I don't think that was ultimately true, but so yeah, I think, uh, yeah, you could definitely go and revisit those heady days if you want to do, but I, I love known desktop and I, I think folks should try it. I really do. Well, I don't mean this to be an ad, but it's just because I was catching up with my old friend, Bart and George yesterday, but have you ever checked out the, the Dell developer laptop that like ships with, uh, with the Boone channel? What do you think of that? Yeah, I think that's brilliant. And it, and Dell are not the only ones who do that. Now you can buy,

uh, laptops that way from HP and Lenovo as well. So they've come ready shipped with some sort of flavor of, uh, of Linux on there. Usually Ubuntu, uh, 22 Ubuntu uses known desktop. So okay, good. You'll get exactly that experience. So yeah, I think it's brilliant. Yeah, I was, I go ahead. I would say my last experience with Linux desktop, which is going back quite a long way. And the difference is probably, I wasn't a developer, so I was tinkering and learning it and all that was, it was the least productive thing I'd ever done, purely because it let you tweak everything. And you know, I'm having to figure out your monitor stats and fine tune all the various parameters to get your screen looking right. But you could spend weeks tailoring either the UI, swapping everything in and out, trying to make this thing look nice or do, it didn't make any difference in the end. So I just went, I'll pick one of them. I'll have a Mac or a Windows or whatever. Um, but that was because I wasn't doing much with it. I was playing with it and learning it and configuring it back when Linux needed that and everything else just installed it and it worked. I think, I think it's, it's, it's, it's like a lot of these, these tools, like the AI stuff now where you're like, this tool is going to make me so productive once I figure out, once I stop figuring out how to be productive with it. Like too many, too many needles and bells and whistles, none of which I actually needed or did anything useful with, uh, just good distractions. I think Linux ties together all the threads of everything we've talked about today. You know, if you're going to be on edge, then you might be familiar with like a Raspberry Pi device or something like that. Linux desktop, right? If you want to run your like Raspberry Pi with a Linux desktop, you can, you can even get that shipped with, uh, Ubuntu or Fedora as well, or just use the regular Raspbian. You know, I, you're, you're, you're solidifying something that, uh, I've had in the back of my head, Ben, which is you are, you are a Linux fan. Like I, I, uh, I, in fact, let me, I think I only know, well, no, you're the only surviving Linux fan desktop Linux fan that I know. And I don't mean

that in a bad way. I, uh, uh, it's, it's delightful. You still use that. There's probably some people, there's probably some people on my developer relations team who actually are. I just don't know of it. So whereas I know about you, you, you should do some videos going over, uh, Linux desktop stuff. That'd be great. Maybe I should. And, and maybe, uh, for any of Coté's friends who know him, who are on Linux desktop, just drop him a line and remind him who you are so that, uh, so that, uh, so that he can put names to faces and all that. Well, well, you know, you know, maybe I should have Barton on here because I actually have like a, uh, unexpected history in the Linux desktop stuff. Like way back in 2010, I was one of the three people who was like running the, uh, the internal innovation like thing at Dell. And that Dell developer laptop was, was the main thing that we, uh, selected and funded to, uh, to launch. And, uh, that, that Barton there launched with everyone else. And the whole premise of it was that when I started working at Dell in 2010, like the number one thing people would tweet at me or write at me is like, Oh, can you get them to finally like make a Linux desktop that I can just order? And then, uh, that's what we did. It was, uh, there was a fun, like, um, it was also a good, a good, uh, lesson in the idea of doing lean startup stuff, which is to say, don't presume to know what you, what features you should have on your software. Cause we had one big feature that was actually inspired by pivotal labs at the time, uh, that we spent a lot of time on that turned out to be just a total dud that we should have, uh, done more incrementally, but whatever. I'll, it, I, I want to, I want to have him on here to kind of go over, like, how do you do internal innovation at a big company? I think it would be a fun discussion for him. Well, I, I didn't, I was scrolling through, I didn't ask our friend chat GPT to do a hopes and dreams thing, but I remember that I gave, I gave, uh, I gave him a prompt to do a unexpected, you know, you know,

when you write an essay, uh, Ed and Ben, it's one of the things they teach you in intermediate, uh, rhetoric is that it's fun to put an unexpected surprise in the conclusion, something that is related to or unrelated to the topic that you went over. That's a little, a little delight, uh, at the end. And so I always try to not always, I frequently try to do that in my writing and I prompted it to do something. And so here's your, your, uh, your unexpected thing at the end, uh, from our friend chat GTP, uh, which is as an unexpected bonus, here's a hangover cure for all those new year's Eve celebrations. Try drinking a glass of water before bed. And then another one, when you wake up, this can help to rehydrate your body and flush out the toxins that cause the symptoms of a hangover. Additionally, eating a small meal before bed, such as toast or crackers can help to absorb the alcohol and prevent your blood sugar from dropping too low. Now I did not fact check this. Uh, but this is, this is just what the, uh, the AI generated as a delightful, uh, maybe this is a hope and dream, uh, at the end. I think, I think dreams summed up as yes. I think there's only one way to fact check this. I think immediately after this recording, we should all go and get a bottle of hard liquor and hit it real hard and then try some toast and crackers, a glass of water and a snooze and see what happens. Some toast and crackers. Oh man. Uh, well, last one to sober up is the loser. How are you managing that observability there, Ben? What, what metrics are you using to check a hangover strength? I think, I think we'll do what, what, uh, what U S cops do and make you walk outside in a straight line and then touching your nose and all that sort of stuff, you know, closing your eyes and trying to grab something, all that kind of thing. Yeah. We all get drunk, then do a

podcast, allegedly having had degrees of crackers and water and the, the voters, the, the viewers can decide who is the most sober. Maybe that I wouldn't be able to do this, but maybe for the more technical listeners, uh, the, the, the, uh, the D the, the drunk test is to see if you can from scratch deploy an application to Kubernetes. And, uh, if you can successfully do it, maybe you're not inebriated. Now, if you can successfully do it and you are inebriated, usability is high. Uh, they've, they've done a great job, uh, on, on that there. Well, you know, not to, uh, not to brag too much, but if we're allowed to use the Tanzu application platform, I'm pretty sure I could do that. That's right. The, the, the, the Tanzu application platform is like, instead of driving your car home, you just, uh, you, you take the, the tube or the bus or, you know, whatever public transportation you have available. Thank you for the alcoholic platform. And that is not an official marketing name. No. Oh, that's good. Yeah. Yeah. Well, well, speaking of that, uh, I think, I think this will be the, uh, I, I don't think I'll come up with any bonus episodes to sneak into the feed, but this will be the last episode for the year. I think it's been, it's been great. You two do kind of rebooting this podcast. Finally, it's fun. I think, I think I am now the disorganized one who scrambles and does things at the last minute. It has to reschedule. You two are very reliable and professional about it. And, uh, which is what, what I always treasure in a podcast host. So I, I appreciate the work, uh, in, in rebooting it here and, uh, we'll, we'll be back next year with more, uh, news on more or less a weekly basis. And, uh, like I was saying, kind of interviews in the overall cloud native space and things like that. And, uh, you know, hopefully all y'all listeners will have then and people who view it will have a nice, uh, rest of the end of the year, a good, relaxing time. What I like about this time of year, not to be all boasty or, or whatever, but like th this, I feel like is the one time of year where you can be guilt-free about goofing off. You don't really have anything in the back of your

head of like, even though this is, this is the sanctioned, uh, I deserve it time where I have vacation. No one else is thinking about work. So I don't really need to either. There's a, every, everyone can just take a break, which is, uh, relaxing. Of course, those of us who are parents, we still have that to put up with, but you know, at least, at least we don't have to, uh, worry about the work area. So, uh, yeah, have a good time. And if you want to get the show notes for this, you can go to tanzutalk.com and you should subscribe to it. And, uh, you know, the great thing, if, if, if you're by, if you, uh, if you're of, of the cultures that gift things to people during this time, uh, before you gift it to them or after you should get their device and subscribe it to this podcast, uh, whether they listen to it or not is inconsequential to the gift you will be giving us of driving more downloads. And you could also, whenever you're sending out your, your automated gift things, tell them, oh, and by the way, you should subscribe to the tanzutalk podcast. Uh, it'll be delightful. Uh, that's the gift you can give to people that we gift to you for gifting. And with that, we'll see everyone next year. Bye-bye. Bye.

Tanzu Talk · 🍕 Get more pizza.