#25 Why VMware Tanzu if there are soooo many open source choices?

Exactly. Yeah, 25th episode of evoilcast. Well, hopefully you'll get to 25,000 episodes. That would be amazing. Hopefully, you know, but I will, you know, my beard will grow a little bigger, I think. So today, with us, Michael Kotę, my name is Maciek Lelusz. I'm running the podcast over last years and we talk generally about case studies here. So we think about technology and how to use this technology in your infrastructure, in your organization. Depends, you know, on what level it's something important to be changed, right, by this technology. Names mentioned because the VMware is in the air, right? So what is Tanzu? Could you could you say to our listeners a little bit, just a brief explanation?

Więc, co masz, to wielka skomplikacja, wielka standardizacja z, jak powiedziałeś, ekosystemem wokół tego. Więc, na przykład, jeśli patrzysz na sposób Kubernetes w robieniu stacku Tanzu, gdzie budujesz na górze, wiesz, Tanzu Kubernetes, Tanzu dla operacji Kubernetes i platformę aplikacji Tanzu, a na górze, jeśli robisz, jeśli używasz frameworku Spring, jeśli robisz aplikacje Java i piszesz aplikacje Spring Boot, There is an out of the box way to do all of that, that you can start doing things rapidly. But it's been my experience that the larger the organization, for better or worse, hopefully for better, people really want to customize and tinker with things.

It's very business talk to match that desire that we have. And so, yeah, I mean, I think. And that gets back to kind of like the other reason why it takes a long time. And a lot of what I study is that like Not only does taking a year to get a lot less done than you think you should, and also trying to standardize and remove as much variation as possible, but the other thing why it's important to be up for learning and experimenting with what's going on is that, kind of as I alluded to, also you're going to be refactoring is a fun word to use, but you're going to be reprogramming and rewriting the organization itself. Hopefully, right? Hopefully, exactly. Right. And that's also why, you know, from kind of like, I don't know how you want to think about it, but kind of the enterprise architect to the low level executive to the high level executive, like they need to think about their role as being programmers of the organization, right?