Hi everyone, thanks for coming. My name is Henrik Blickst. I'm a product manager in the NFE BU at VMware. So I was going to talk to you a little bit about what I've been hearing from the service providers we've been talking to, some of the customers that I meet with a little bit on their feedback and what they've been seeing in terms of using OpenStack, what they love about OpenStack, maybe some of the challenges they're seeing and I'll talk a little bit about what can be done to mitigate that. So just a standard disclaimer, I wasn't planning on presenting any roadmap but sometimes I talk about shooters anyway and being a product manager or anything I say will be used against me so the only thing I can promise you is that any roadmap things I talk about will change so please don't hold it against me. So just quickly some high-level challenges, the promise of OpenStack I think most of you in here know OpenStack pretty well. How many in here are from a service provider, work for a service provider or with a service provider? About half of you maybe. Okay, and I'll talk a little bit about how I came back to loving OpenStack again. So what are some of the concerns that you know when I meet with these service providers, you guys, some of your colleagues, some of your, some of your other companies are out there. One is that breaking free from legacy hardware. A lot of the hardware that's out there is legacy and purpose built hardware for your network services and that's one of the driving forces behind NFD as well. Getting off from all these purposeful built hardware, getting to something that's a little bit more agile, a little bit easier to manage, getting away from having something that's very uniquely built for a specific thing which makes it very inflexible because if something is built into the hardware to solve a certain thing, making that hardware thing do something else is pretty hard. It also means that upgrading it is pretty hard. If you need to, if something is built in, if there's this switch or a certain functionality, a certain card built into that hardware and you need a new feature that needs a new card, you actually need to send someone to that machine and replace something or replace the whole thing. And once you start getting into distributed deployments and make architectures where you might have tens or hundreds or thousands of these boxes, sending out thousand people to replace a card or a whole box is getting pretty tricky and expensive. And it's going to take time too. It's not just going out to all this place. It's actually all of you that have been SUSE, I started my day as a SUSE, being in the data center, pulling cables and doing all that takes time. So trying to get away from that and doing something that can be done by fewer people, more automated and faster. And some of these, the hardware life cycles for a lot of these boxes, since they're pretty expensive, they're hard to get out there, are also pretty long. So that means that the skills for maintaining this hardware thing or the card that is, might be very legacy. So maintaining the people that know these skills might be hard, might be hard to find people that know the skills for a hardware box that was only sold for a few years, you know, 10 years ago. Something else that there are a lot of concerns around is innovating faster. Not just innovating, because innovating is fairly easy, but innovating faster is what the way I want to do. And the networks they have based on what we just talked about, the legacy hardware, they're not really prepared to innovate because of the slowness of doing anything to the network. And they need to roll out features faster. And especially when they're getting into the NFV and virtualizing, they have their upcoming competitors that have a newer, more modern architecture that can roll out features a lot faster because they're virtualized versus rolling out new hardware. So they need to get into that thinking of getting things out faster. And also innovate continuously. It's not a big bang innovation that, hey, we have a great idea, let's build a box for it, roll it out, and then five years later, hey, we have a new great idea, let's roll out this new box. It needs to be continuous. You can't have innovation cycles that are five, or even two years, even one year, you need to get new things out all the time, maybe not daily, but as new ideas come up, they need to get out faster so you can get feedback. Because when you have that long innovation cycle, it's also going to get very costly because it takes years to build the box. And then rolling it out takes a while. So it's going to take a while to get feedback. I'm not really sure it's this really the thing that people want, the feature that my customer is asking for. So if you can do that innovation faster, you also get feedback faster, and you know that maybe I should roll this back and maybe I should focus more on this. And that also helps them shorten the time to revenue. Because there's also a lot of risk when you innovate slowly, it's also going to take you time to get to the revenue. It might be a good revenue, but the risk of getting that large revenue is going to take you so long that you want to make sure that it's better to take a little bit less revenue, but getting it faster because it makes it easier to do your planning and so on. And one that's attended any session here this week has probably heard a lot about Kubernetes Cloud Native containers and asked the telecom service providers to start looking at how they're virtualizing, they're also looking at containers. And they're realizing that it's more than just containerizing. And everyone that's done anything with containers know that, or tried to put anything with containers into production, it's more than just taking, hey, I have an application, I'm going to package it up in a container, and I'm done. Anyone that's tried to do this in production, it's quite a lot more than that. It's a different way of thinking. It's a different tool set. So there's more than just the packaging that need to happen. And if you have an organization that's more legacy focused and with the thinking, actually getting the processes changed might be much harder than just the packaging. You might need new tools. Instead of learning how to deploy a VM, you need to figure out how to plug something into a CI CD tool chain or something like that, which is a different way of thinking, different way of working. You need to learn a new set of technologies. And another issue that, for those of you that have attended more sessions or more than one summit or maybe a CUBE console like that, you also know that these technologies change a lot. Three years ago, it was all about Docker. Then a couple of years before that, it was mesos. Now it's all Kubernetes. So trying to keep up with that, figuring out what technologies to bet on, what to invest in, is another risk. And they're moving very fast. Not only do you need to figure out what do I bet on and bet my money on, also what people do are higher, what do I train these people for. So that's an area of concern as well, because the telecos want to make sure that whenever they bet on something, it's going to be in the networks, it's going to be there for a while. So they want to make sure that it's something that they can actually support so they don't end up with the same legacy situation they have today with the hardware, but just with software instead. Just telling you that would be almost as bad. And building a software-based care grade environment. A lot of these networks and network services are very mission critical. If you try and use your phone and your phone is not working, you're going to get pretty upset. You might even be in a life and death situation. So you can't have something that you're trying to call 911 or 112 and you get an exception in your phone or you can't connect to the network. It's not going to be very popular. How many in here has seen software or written software with bugs in it? Probably most of you, right? And that's just something we as software developers, we just accept the fact that if you write software, there's going to be bugs in it. If you deploy a VNF, a virtualized function that has bugs in it and you can't call 911 or 112 depending on where in the world you are, that's a little bit different. So when you do this hardware-based, it seems like for some reason, no offense to all the software engineers in here, but it seems like hardware engineers are better at building stuff than software engineers because it seems like there are fewer bugs in these older purposeful built switches or boxes they have than the software that we build. So that's one of the challenges. How do we make sure that what we build doesn't have those bugs and something that's as stable and mission critical with all four, five, six, nine as they have today in their hardware-based platforms? As we build all these various software and we do microservices, we build all various software parts, we also need to stitch them together. In some way, it was almost easier in one way earlier when you pulled one cable out here and you plugged it in over here and you're like, hey, my integration is done. We're trying to figure out the various payloads in terms of text files or whatever it needs to be sent between the various system and how they interact with each other. They can show that the APIs are compatible. The APIs aren't getting removed or changed. It's also a bit of a challenge. With the hardware, it was also pretty figuring out the resource allocation was pretty easy. Hey, here's a box. It has this many resources in it. That's how much resources you have. If you need more resources, you need to put another box in.  You might have a couple of VNFs on the same infrastructure. The one that handles those emergency calls doesn't get resource starvation. If someone is watching Netflix or watching your favorite TV show on the subway, it probably won't be too upset if it pauses for a second or two. If you can't reach one or two, you're going to get a little bit more upset. So you need to make sure that the critical software applications that you have deployed here actually have the resources they need and making sure we can carve those out in this virtualized environment. And not only that, you also need to make sure that the software doesn't crash. And for those of you that have seen a bug or two or written a bug or two, it's also the same somewhat similar to what you said before about the hardware. The hardware boxes, for some reason, don't seem to crash as often as our software. So you want to make sure that whatever we build has the resilience in AHA because eventually we are going to run into one of these bugs. And when we do want to make sure that whatever was running will actually survive, we'll come back up again. And for those of you that were here for the previous session, you heard Vanessa talk about distributed clouds and MEC. And that brings in another set of challenges as well because these boxes that were placed, they were pretty autonomous. They were sitting there doing their stuff. But they were also not very distributed. You might have had a couple of data centers in the U.S. or a handful at the most or spread across the world. When you start looking at distributed architecture and MEC and you might have hundreds or thousands of deployments, then you can't have a SUSE item and logging on to every box to do a dot slash update. So you need to make sure how do you automate this and how do we handle these new environments at scale? So all this hide and the service write is scratched on the head. How do you figure this out? How do you do this? What are the best tools to do this? And there's been a lot of excitement around OpenStack. And for those of you that have been in the community for a while, you've seen that telecoats and service providers have started coming out in larger and larger numbers and looking at OpenStack. So what is so cool about OpenStack and what do they love about OpenStack? One of the big things is the community, all of us working together. When we had more specialized hardware, you had five vendors who were all building their own little box. There was no, this vendor was sitting in here building their box. The next vendor was sitting over here building their box. Here we are in thousands of people all working together building the infrastructure for all those things. So service providers usually are very nervous about sticking to one vendor. They have maybe multiple vendors. And here in the open source community, in the OpenStack community, we have all vendors collaborating. So instead of having the vendor sitting in their own labs, their own rooms, building these hardware boxes, we have all the software vendors here working together trying to figure out how to build the best platform that they and you guys can use. And that also helps the, and talking about that in some of the keynotes as well, how this collaboration helps foster innovation and helps innovate faster, helps us innovate more when we're sharing ideas across all the companies. You know, coming from, coming from VMware, you know, I have one view of the world. Someone coming from Red Hat has a slightly different view of the world. But here we can actually sit together, talk together, figuring out the best way to just solve these problems that, you know, work for all our customers. And that also helps drive standardizations because we want to make sure that something that works on one version of OpenStack works in a different distribution of OpenStack. You know, this was back in the day when we were all doing, most of us, a lot of us were doing Java, trying to deploy Java to different application servers. Now there's always the problem. It's like you can deploy it here and, or build it here and deploy it everywhere. Didn't really work back then, but now actually, you know, a few years later down the road actually come to a point where all the APIs are in OpenStack are standardized. So if you can deploy it to one, you're very, very likely to be able to deploy it to something else. Just that standardization, getting telcos, you know, out of the single vendor lock-in and making sure that they can have, not only because they want to pitch the vendors against Dodgers, make sure they can push down prices, but also making sure, you know, if someone goes out of business or start focusing on something else, you know, they can, they have some options and choices and flexibility. We already talked about it and touched a bit about the simplified APIs, but they, you know, as they develop their application, as they do the VNFs, they do a lot of testing with these VNFs, having the same, the same APIs to the underlying platform makes that testing a lot easier, because they don't have to write a bunch of different tools to test different APIs. They can basically write, write it once and use it everywhere, right? So that makes that a lot easier, cheaper. And also, you know, you don't have to build different skillset and learn different APIs. Say, here's one API, we can use this for everything. And it also helps, you know, the people that actually develop the VNFs, because they know that there's one, there's one platform that they're going to get deployed on, might be different vendors, but they all have the same Northbound, Southbound APIs. So whatever network functions I write, if they have any resource needs, I know exactly how to deal with any, whether it's storage or compute or networking or secret management, whatever it may be. And there's also a common architecture, and what I mean by that is when you write an application, you might have, that application might have certain expectations in terms of how distributed deployments are done, how HA is done. And having open stack underneath, with the standardized APIs we just talked about, we have the same concept of regions, availability zone, host aggregates or whatever those various constructs might be. So if you have an application that has some expectations around that, they're going to be the same across, you know, across all the various platforms and all the vendors. Another massive benefit is open stack itself. And that's why, you know, we built open stack is to have standardized APIs that's detached from the underlying drivers. So whether I want to have a VM that gets deployed onto KVM or ESX or Zen or something else, it's the same API call basically. So it's hidden from my VNF developers or my users, what's actually running underneath. And I can plug and play basically the various drivers and have a unified experience no matter if I decide to change something in the underlying platform. And then that gives them maybe portability into the best word, but they can deploy and move these VNFs between these various platforms and make sure that if it works here, it's going to work over here. And I don't really need to change anything in my application to make it run on a different platform as long as that platform is open stack, whether it's runs on a Red Hat stack, whether it's a VMware stack, maybe it's a Rackspace public cloud. It doesn't really matter anymore, right? It's all open stack. And there are also a lot of the workloads that run in these environments that are, there are very few workloads that are truly cloud native, even though there's a lot of talks and sessions about cloud native here, there are very few companies except maybe some newer and younger startups that had everything containerized. Is there anyone in here that runs a deployment environment where everything is containerized, everything is cloud native? Maybe someone may be thinking about raising a hand, but I don't see any hands in the air really. I mean the truth of the matter is that everyone pretty much has something that's either containers or VMs or even bare metal. And we've been trying to virtualize on the enterprise side for the last 15, 20 years. How many in here still has bare metal running in your data center somewhere? Yes, quite a few. And the thing when I talk to customers, it feels like it's almost, almost everyone still has something bare metal running. And I think that's a reality that we're going to live with and maybe even see more now when we start deploying containers to bare metal and things like that. We're going to have environments, we're going to have workloads that have parts of it deployed to bare metal, parts of it deployed to VMs, parts of it deployed to containers. How do we get all these workloads talking together? How do we stretch the network between them? And how do we manage and deploy these in a single unified way? And that's where OpenStack shines. Right now, if you want to do this outside of OpenStack, you might have one API, one way of doing bare metal. You have one way of deploying VMs and something completely different deploying your containers. And that's one of the things where OpenStack helps as well, where we can have the same tendency models, you know, have the same networking. If we're here listening to Marcus's talk earlier about NSX-T, showing how you can share network between VMs and containers. And when you take that a step further and have that stretched onto bare metal as well, bare metal as well. And that's something that OpenStack can help with. Another thing that's cool with OpenStack is that a lot of the VNFs, even if we're working towards virtualizing the world, a lot of workloads still require direct access to the hardware. It might be because of performance reasons. Might be other reason that it's just more efficient in some way to just talk directly to the hardware. So even in this new virtualized world, we still have workloads that need to talk directly to our NICs. There might be a GPU or something similar. You want to make sure that we still have the capability, even as we're virtualizing containerizing, we can still get that, whether it's streaming or whatever it may be, that they can talk directly to those cards. And then on the other hand, there's a lot of work also going on and have been going on for a while on enhanced performance, on DPDK, and enhancing network performance in a non-hardware specific way. So you want to make sure that we can do both of these and all of these together. So even if we're doing SRV, for example, for one workload, we can still share the same environment that virtualizes network and get the high performance network with DPDK without having to choose one of the other and have them all coexist. And there are some projects like Cyborg within OpenStack that's looking at how do we handle this more hardware-centric view of the world in an OpenStack environment and making it play nicely alongside all this virtualized stuff. That all sounds awesome, right? And if all that just worked, life would be all good and dandy. But it turns out, that even moving from your hardware view into OpenStack, there are still some challenges. If you've tried, anyone that's tried to deploy OpenStack in production knows that there are still, even though we've come a long way, there are still some rough corners in there. One of the things that is still a bit of a challenge and is both good and bad is that OpenStack has a lot of knobs and things to turn and configure. So that's good because we can cover all use cases. We can do pretty much everything with OpenStack because there are so many things we can change. But that also means that we're building a lot of snowflakes. If you look at OpenStack and look at the various deployments that we have out there, if you have 100 deployments, you might have 100 different deployments. Something goes wrong over here. It's going to be very different from something going on over here. It's really hard to troubleshoot figuring out what's going on because they're all slightly different. So that makes it hard to very efficiently manage all these various deployments. Even within a company, you have a large company like a telechore service provider, they might have a fair number of different OpenStack deployments. And if they're all different, the configuration management and making sure that all the drivers are the same, configured the same way gets really, really hard. And even though OpenStack has come a long way from where we've been in the last few years, it's not really any better than the platform you run on. So OpenStack has a framework. If the platform it runs on isn't super stable and has the resiliency and the high availability that we talked about earlier in the drivers and in the platform underneath, it doesn't matter how good OpenStack is, it's still not going to be able to be better than that. We talked a little about a little bit earlier about global deployments and scale and OpenStack, though it's getting better on some projects around this, trying to address this. If you have a global presence and you want an OpenStack deployment that spreads across the globe, there's still some challenge involved in that. There's our RabbitMQ that we all know and love, still has some challenges. Now you start getting into, it all works fine maybe if you're all within the US, it's all deployed within Germany, and start stretching it into other countries where you might not have the same bandwidth, higher latency, you start running into some issues. Just a sheer scale of things as well is back to the edge use case that you mentioned earlier, once you get into hundreds or even thousands of nodes, it starts to get challenging as well. And even in smaller deployments, monitoring and operations for OpenStack is still hard. The tools have definitely gotten a lot better since I started working on OpenStack, but there's still some challenges in doing things like root cause analysis, trying to figure out in which of my log files do I need to look at, or how does the error that shows up in this log file actually relate to something that's in the log file over here, and how do I correlate those and figure out what's the actual root cause of this. And that makes it pretty expensive and costly to operate these OpenStack clouds, because it just takes too much time to figure out what the issue is, because every now and then we do hit one of those bugs that unfortunately is still right. So we need to get a lot better at that. How do we do some more, I mean even better, there's a lot of work going on on AI and predictive analysis to figure out how do we figure out where something's going to crash, or which bug are we going to hit before we've been hit it, so we can take some measures to prevent that before it even happens. And lastly, if we want to do migrations, if we want to do the import, I know that most workloads today don't run under OpenStack. And we all want that to happen, and we're trying to get there, but there's a lot of real estate, a lot of workloads that run on KBM, that run on ESX, that run anywhere, and we want to get that into OpenStack. Importing those workloads into OpenStack might be tricky, depending on what those workloads are. If they're all ephemeral workloads, then yeah, it's not really a big deal. Once you start getting into workloads that have advanced networking, they have some persistence, they have dependencies between them, it starts to get a lot harder. We might also want to consolidate data centers or consolidate workloads, and if we have 25 data centers, we want to move to two large ones, getting that the workloads are running all those five data centers into two data centers, and not having to take a lot of downtime is also tricky. We might want to move from a OpenStack version, for some reason we're not happy with the vendor we have now, we want to move to using a different vendor, or just we have a really old version of OpenStack, we don't really want to upgrade this because it's running, you know, grisly, and we want to move to queens, then doing all those 10 upgrades in between might be easy, just trying to do a migration, but how do we do that with that, and killing all those workloads? So, I've been working OpenStack for a while now, I've been with VMware for a year and a half, so some of those things are things we've tried to address and worked with some of the, some of the things, some of you guys in here, some of your colleagues and competitors, and how do you solve this, and how do you take those, because it all sounds good, and the promise of OpenStack is really great, but how do we take that promise and overcome those challenges, and what do we need to do to overcome that? So, we have something called VMware Integrated OpenStack, I don't know how many of you know that VMware actually has an OpenStack distribution, we have that for four years now, and it's, even though the name might imply that it's something proprietary, I can assure you that it's not, we basically take upstream OpenStack, like all the other vendors, we package it up, deploy it on, we're installing on Ubuntu, package it up in VMs, deploy it on ESX. So, we have this OpenStack distribution, the biggest difference between other vendors is that we run on AV and VMware on platform, and that is, you know, one of the challenges that we've had, a lot of telecos and vendors already run VMware somewhere in their, and mine might be on the IT side, maybe not the NFV side, but they, almost all companies today, or a lot of companies today, run something VMware, so extending that environment to also cover OpenStack, and get some of the benefit of that virtualization platform that we've been working on for two decades, and extending that to get those benefits we talked about earlier, and all those things that the service provider is looking for, but having that stable platform underneath, and that's pretty much what we're saying, that you're saying that you can get the best of both worlds, you can get all that's so good about OpenStack, and also get that on that stable platform, so that was the main driving force behind us doing OpenStack, because it might confuse some people that, you know, why is VMware doing OpenStack, but it's actually a really good fit, because we get a lot of requests for having those open APIs and the open standards, but having that solid platform underneath, so some of the core things that we've been working on is, just like I just said, like the open APIs on that core platform, being virtualized means that we've taken some of the pain away out from installing it, that's at least early in the OpenStack days, especially installing an upgrade, and we're really big pain points in OpenStack, by doing that with VMs, we can do some really cool things where we basically, when we do an upgrade, we basically use the same workflows we do for install and just install new VMs on the same host that we were already running on, and then the last step in the upgrade process, we just sync the databases over to the new VMs, point the load balancer to the new VMs, and we're done with the upgrade. If one of those nasty bugs still happens after we've upgraded, we can just point the load balancer back to the old VMs, and we basically rolled back to the previous version with zero downtime or having to restore machines or bring something else up from tape or whatever it might be. VMware has also worked a lot on, we have a very comprehensive operation suite, and if you have admins that already know VMware, they already manage that IT side of the house, then extending that and having them manage the infrastructure that runs the VNFs comes natural, and they can use all the root cost analysis and the cost estimation tools that we have and just extend that into the NFV world. And I think we're starting to run a little bit short on time, so I might have to speed it up for the last ones. So we do some of the things we do a little bit different than a KVM-based OpenStack, for example. In the KVM world, you have one Nova Compute, for example, per host, and that means that if you deploy your Nova Compute host, at the edge you get those latency issues that we've heard in several sessions here before. We just let things slide differently where we have a Nova Compute map to a ESX cluster, so that means that instead of having a one-to-one mapping, we have a one-to-many mapping, which means that underneath the cover, OpenStack really just sees an aggregated pool of resources, which means that we can use some of the functionality and some of the benefits of the virtualization platform like DRS, for example, and do automatic workload rebalancing underneath the covers. How many here have tried to do workload rebalancing on KVM? A couple of hands. It's pretty hard, and it's not something that just comes out of the box, but since we aggregate that pool, it's transparent to OpenStacks. We can do that underneath. If a host goes down, we can fail them over to different hosts and do that automatically without crashing OpenStack or making Nova get really sad and unhappy. We also have something called valuing the box, and they talked about that in one of the keynotes, so this is somewhat similar to what they're doing with Starling XX-Wall, where we package up OpenStack in a single box, both for a branch office use case or maybe a opinionated edge use case, maybe, if you like, where we can deploy OpenStack to a single box and you can take that, ship it as an appliance, ship it as an edge, and then we expose all the lifecycle APIs through, we have something called the Oracle, not the Oracle, the OpenStack management service, so all the lifecycle management APIs to patch and extend the capacity are exposed to three APIs, so you can, if you have an orchestrator or some automated tool, you can use those to manage all those thousands or hundreds of nodes that you have deployed across your infrastructure. And we have a couple of different modes to deploy that, and we actually have one mode where we have almost similar to DevStack, where we've taken all the OpenStack service and put them together into a single VM, which makes it really quick and easy to deploy and very small foot prints that you can use for these single box deployments. And I think lastly, I think we've shown some demos on this, we have something called HCX Store for Hybrid Cloud Connect, which is a way where we can extend network fabric between on-prem and public cloud, and there's something that connects into what we do with AWS, the VMware on AWS, where we can actually extend the network fabric from your on-prem data center into the cloud data center and as we continue to build on these, we'll be able to start doing things like doing live migration from an on-prem data center into your cloud. It'll also help us do migrations we can do, basically do a live migration of a VM from one environment to another, which will help us do some of these migration use cases. And we've also plugged this into some of the IP we got for the acquisition we did some time back, so we can actually do a warm migration from a KVM-based open stack into a VMware-based open stack. So I think with that, I have about five seconds left for questions. So I'll stay here for a few more minutes. I'll be outside afterwards as well when they kick me out if you want to ask me some more questions. So thanks everyone for coming. Have a great rest of your summit.


National Police Week is really just a time to be able to recognize America's law enforcement community, specifically paying tribute to those officers who lost their lives in the line of duty. The job that the men and women of the Thin Blue Line do is so unique, they're called upon every day to make incredibly difficult decisions and I think that those especially who have paid that ultimate sacrifice, it's important that we come out and that we recognize that and that we share those stories with our communities. Some of the events obviously are tied into Police Week, I think that the purpose of them is one, you know, to strengthen our ties with the communities, strengthen our comradery amongst each other, not just with our on-base law enforcement but our off-base counterparts as well. But some of our specific events, such as our bowling tournament on Wednesday, all proceeds will go back to the families of some of our fallen defenders from this last year. Defender Nation, we're out there every single day, seven days a week, 24-7 and really it's our job to make sure that everybody else is able to do their job. Whenever I see a plane in the air, whenever I see medical professionals able to do their jobs, our pilots doing their job, maintainers doing their job, I know that they're able to focus on that and do their job and do it well because the defenders are out there protecting the base, making sure that their families are secure, that they're secure and that peace of mind is really priceless when it comes to accomplishing the mission.


Good morning you guys, I didn't want to talk until now because everybody is still sleeping and it almost feels like illegal to be awake right now Like honestly talking if this feels illegal right now like it feels too early to talk You do not know how tempting it was to go back to bed and to just like not do this video like to be honest I was literally like contemplating it in bed And I was like okay can either just not do the video today or I can do it and Kick myself out of bed pretty much But I decided to do it because I know that if I didn't get up and do it today I would not do it tomorrow like I would like hate myself for leaving it to do tomorrow Rather than doing it today. You know what I mean? Like I just like anything done So doing it today and that's what's honestly really hard Okay, it's different if like you have something to wake up for to get out of the house for like if you have an appointment or whatever it is something that's early that you have to get up for but when you work from home like I do And you make your own hours waking up at five that makes it even harder because it's like I don't need to be above five right now Like I can work any hours I want so it makes it even more difficult to convince my brain to actually wake up You know what I mean? Anyways, so the only thing that I have to get out of the house and do today is I have a COVID test at I can go in between the window of 8 a.m. And 11 a.m. It's for the movie industry So yeah, that's like all I have to get out of the house to do today That's like priority to get out so we'll do that later But we still have a lot of frickin time until then I've already guys into the laundry room because I figured that Since I don't know what else to do with myself at this time It feels weird to do my usual routine with stretching and meditation I feel like I'm too tired for that right now like my body won't be able to do that right now like meditation I would just fall asleep and stretching. I guess I can be stretching. I'll do that a little later though because right now I just I just feel like sitting down to me. It's like I'm really tired I'm definitely gonna take a nap at some point in today anyways I've laundry to fold because I put a load on last night, so let's do that as a first morning task I literally don't think I've ever done laundry a flatbed in the morning before in my life So it's gonna be in the world record book or something Why the hell are you? He's like so confused all the other people that I saw do this challenge I had coffee right away, but I don't really want to have my coffee right away because I usually like wait a little bit To have that anyways like waking up about my normal time So I honestly don't think that I'm gonna have it until like go to my Kobe test I think I'm gonna like save it for driving on the way and not have it right now because I feel like having coffee this early It's gonna make me crash Rather than like keep me awake the longest I could stay awake. You know what I mean? So I'm definitely gonna wait out the coffee and for now I'm just gonna have a lemon water because that's what I usually start my mornings off with anyways So we're gonna do that Cheers to my 5 a.m. Lemon water doesn't taste so good at 5 a.m. to be honest I feel like I'm in a dream right now like I Can go back to it so easily Stay awake. Come on. You literally feel so tired. It's not even funny I did go to bed at 10 30. No, I didn't I went to bed at 11. It wasn't 10 30 That's sparse. So I only got six hours to see it shit I only got six hours to see that's why I'm so tired and calculate that right literally don't know to say right now Okay, I need to turn this into a productive morning. The thing that I don't get is people that can work out at this time That's probably the last thing I'll ever do is work out at this time 8 a.m. Is a little different than working out at like five six a.m. For me like I could do 8 a.m. I guess I mean still wouldn't but I could probably working on it this time If I work out too early, I feel sick and I just don't have a good workout because I'm lacking the energy So whoever couldn't work out like this early is like last like good for you because that's a bit I cannot do I'm trying to think of what I should do right now If I should just start working if I should do my stretches Definitely not meditation because we know how that's gonna turn out. You know fall asleep It's too early to want to walk because it's literally dark outside like that's unsafe for me I can do the dishes The dishwasher didn't even go on last night. So that's actually really great, which means I don't need to unload this I'm gonna do this like these dishes here though Okay, so the sun is starting to come up So I think that I'm gonna take my dog on a walk right now and go on a quick like half an hour to 45 minute walk and Just yeah, I feel like it's gonna be nice because everybody's asleep You know what I mean? So it's kind of cool going on a walk at this time. So yeah, it's going to walk I'm literally the crack of dawn.  Let's go Okay, guys, so I just got back from the walk and I'm Rabbiness for food like I am so hungry and while I was on the walk I was dreaming about avocado toast and I was like that would be so good But I didn't think that we have had avocados those that go shit We probably don't have avocados and I literally look in the fridge and we have like the most avocados I've ever seen in my fridge ever so I'm so happy right now And I'm gonna show you guys like my perfect avocado toast recipe because I feel like I like to make it a certain way I don't like to make avocado toast like plain and just like like I like to spice it up We're gonna make a good a good avocado toast today. I think I'm just gonna make one like a big one Let's put bread to oh my god. This is gonna be the best avocado toast ever I usually don't need breakfast until like 11 or 12 like I usually wait, but I'm so hungry I feel like since it's early my body needs to be at least some oh my god fresh sourdough My favorite type of bread to ever live on the planet earth like so good in the smell Okay, so I'm actually gonna do a poached egg I love poached eggs. I don't know why but they just taste superior on avocado toast I don't know why but they do so I'm gonna boil my water And I'm also gonna heat up a skillet because I'm gonna toast the bread on the pan instead of toasting it in the toaster And you will see why it's the best method. I'm telling you toasting bread on here I add some garlic and butter versus just putting it in the toaster makes the world of a difference Yes, this is very intricate. Okay, like I know this takes like a way more time than just making your basic avocado toast But it's so good if I had a restaurant I can literally charge like 20 bucks for this and people would not think twice about it because avocado toast is expensive Like if you go to a restaurant, it can be up to like 20 bucks at least. Okay, so while these things are heating up I'm going to get some garlic and butter, so I'm actually using vegan butter This one is obviously the best one ever like it's so good. So I'm just gonna put a bit Let me show you guys the pan more. So I'm just gonna put a bit of butter in the pan and heat it up I'm just gonna take like one kind of big clove of garlic and put it in this garlic Fingering where you crush it and I'm just gonna put this in the pan as well The smell of garlic and butter together in a pan. Oh my god, like I'm so awake right now Okay, so now I'm gonna take my bread and I'm gonna put it on the pan With the garlic and the butter and just put it like right over top with that sizzle in the bread and then This is almost boiling my water is now boiling and I'm gonna add a bit of salt And I'm gonna add like a teaspoon or two of vinegar. So I crack my egg in here I'm gonna turn the water down and I'm gonna make a whirlpool here and then drop the egg in I don't know why but it's that's how you do it Set timer for three minutes. Okay, so while that's doing its thing one more minute for the egg I'm gonna get the avocado. Oh This one is literally perfect. Oh My god, I don't think you could get a more perfect avocado. Oh my egg. Okay, so the bread is officially Done. I burnt it just a tiny bit. That's fine We're both gonna give this exquisite presentation But I kind of like it like that. So anyways back to this exquisite avocado Avocado, okay, so I'm just gonna season the avocado real quick before putting the egg on I'm gonna put salt Chili flakes and then I'm gonna put pepper I'm actually quaking right now because of how good this looks.   Anyways, let's eat I'm so hungry Okay Bon appetit. Oh my god, the eggs are cooked to perfection. You will not believe this literally.  I was like I need to take a nap or else I'm gonna be falling asleep on the road because I was exhausted and that power nap Just really did it for me I find that like 20 minute naps are the perfect medium for me and it just like rejuvenates me like completely so I just made a coffee and I'm just gonna put the address on my GPS and then get going this coffee is so good. Um, this is gonna definitely help wake me up I have a love-hate relationship with coffee where like I love coffee But I don't let myself drink more than one cup a day because I don't want to get like too addicted to it And I don't want my body to rely on it I don't want to need coffee. I want coffee to need me No, I'm kidding But like actually like I just don't want to become too dependent on it and also that's why I have it kind of like later Or at a different time every day so that my body doesn't get adjusted to the time that I have it either so Yeah, let's get going. This is my fit.   I haven't finished this because I don't want to make myself pee more So it's kind of a struggle right now I am such a browser like I almost like can't come to stores alone because like I'll spend all day just like walking Around looking at the fancy stuff like it's actually bad like it's not It's not good. It's really not good But you know what we're so here looking like but I got to get home and start my work So I should really get home because I got the shit that I needed so let's go home Joel You'd be proud of me for leaving right now because whenever me and Joel go together Heals like grabs me because he hates whenever I was so you'd be proud of me right now. I'm leaving Okay, so I didn't do like an outro for this video explaining like my last thoughts my last word So I'm gonna do that right now. Would I ever do this again out of my own will? No, I don't think that it benefited me a lot because I was just so exhausted when I woke up first of all Second of all waking up at 5 a.m. You would have to go to bed super early So it kind of cuts into the same times anyways and third of all I just felt like I was almost less productive because I was so tired and I had to nap and usually I'm fine without Taking a nap waking up my normal time I can do it like let's say if I had a job that required me waking up at 5 a.m. Or earlier I can do it for that if it's a priority that I need to be up at that time Then I would have to make things work with that being said I do make my own hours Therefore I think that for me it is pointless and I will never be doing this out of my own will again Because I love my sleep and being exhausted really has a huge impact on how my Productiveness is throughout the day. I didn't even get my meditation done I didn't even do my stretching that day because I just felt too exhausted to towards the end of the day I just started getting really tired and I went to bed super early that night. So yeah overall I would not do this again. It was fun to try it out But I wouldn't do it again out of my own will just because I have the luxury of making my own hours So it's not worth it to me, but I know everyone's different and I just love my sleep. So yeah, hope you guys enjoyed I love you guys so much and I'll see you guys in my next one Peace out


Item number SCP-3200 Object Class Keter Special Containment Procedures At present, primary containment procedures consist of exploring waves to slow down the expansion of SCP-3200. All potential research inquiries along this line are open for consideration, as no current solution, permanent or temporary, has been found. Unabiliated researchers have been suitably implanted into civilian scientific institutions in order to both discourage series inquiry into the nature of SCP-3200, while also conducting independent research into the anomaly. Rescue attempts for the crew members of the Peregrine-9 expedition are not being considered at this time. Description SCP-3200 is a region of space currently 300 million light-years in diameter, located at approximately right ascent in 14 hours 50 minutes and declination 46 degrees, commonly referred to as the Boots Boyd by civilian scientists. At present, the exact properties of SCP-3200 are unknown, as most research into the anomaly was conducted by the now-defunct Peregrine expedition program. As such, there is considerable debate into how exactly SCP-3200 functions, though the following principles are considered to be accurate by majority consensus. SCP-3200 represents an exceptionally thin and potentially open region of space-time such as trans-universal contact is possible through SCP-3200. The anomaly is expanding at a rate of 1 million light-years per year. The expansion of SCP-3200 poses a non-zero threat of a UK-class universal collapse scenario. All other points concerning the exact properties of SCP-3200 are considered to be highly speculative. Researchers looking for more information concerning the anomaly may consult the following compiled reports on SCP-3200. History of the Anomaly The anomaly was first discovered by civilian scientists who noted that the region of space possessed significantly fewer galaxies than one would expect from any other region of space. Notably, while a similar size region of space should contain 2,000 galaxies, SCP-3200 only possessed 60. Foundation researchers at Site-118 conducting research into extra-solar anomalies noted extremely high-hume levels arising from SCP-3200, but were unable to determine any reason for this. Continued research into SCP-3200 would not be seriously conducted until the launch of the Peregrine Expedition in 2008. Original Peregrine Expedition Mission Statement With the creation of ever-specific technology by members of our Applied Sciences divisions, we often find uses for various advances that we had never before considered. The creation of the first temporal stings by Foundation researchers showed us that time can be manipulated, slowed down, or even held constant from the perspectives of different viewers. As such, we aim to use modified temporal sink devices in the launch of a new Foundation space initiative in order to better understand non-terrestrial anomalies. By speeding up time relative to us on Earth where the crew members of our planned spacecraft, we can accomplish advanced space travel to many distant locations. Temporal sinks allow us to maintain the natural flow of time for both us observers on Earth and the crew members of the expedition, maintaining causality in all frames of space. It is a simple matter of cryogenically freezing our crew members for however long they intend to travel, activating our modified temporal sinks, and then waking them up when they arrive as their destination, in a frame of time that is usable by our standards, all without violating causality. Small-scale tests indicate that we could use these temporal sinks aboard fuel-efficient ion thruster-powered spacecraft to send researchers hundreds of millions of light years away and back into space in a few months, allowing us to vastly improve our knowledge of extra-solar anomalies. Dr. Alexi Dimitrov The approval of this experimental technology in order to study extra-solar anomalies led to the launch of the Peregrine Expeditions in order to glean more data on several different extra-solar anomalies. SCP-3200 was selected as the target of the Peregrine-9 expedition, launched November 29, 2010. Peregrine-9 Expedition Details Objective Conduct research into the nature of SCP-3200 and ascertain origins of abnormally high HUME levels. Crew members Misha Commander Pilot Captain Mikhail Kuznetsov Mechanical Engineer Researcher Alexander Moreau Astrophysicist And Researcher Thomas Sewell Extra-solar Containment Specialist Flight Details Mission will take place from November 29, 2010 to November 29, 2016. Flight time using temporal sinks will occupy roughly four years of total mission time, during which crew members will be cryogenically frozen. On February 28, 2016, the Foundation recovered a capsule launched by Peregrine-9, consisting of modified segments of the original Peregrine-9 shuttle. The following is a collection of relevant logs and transcripts found inside the capsule. Full reports may be retrieved pending approval from the project director. Recorded date February 1, 2013. Camera feed begins. Kuznetsov is seen adjusting the camera, as the rest of the crew seems to have only just awoken from cryo-sleep. And just like that, we're 700 million light years from home, didn't feel like anything to me. It's a little scary, and a little amazing, so this means that we're firmly inside the anomaly then. Correct, I don't feel anything different though. Take a look outside. Perotics the camera and shows the view outside the spacecraft, and it's pitch black, with no signs of any stars or galaxies visible. Now that's disturbing, pure blackness. All three men are silent. What do you suppose is out there? Who knows, it's our drive to figure it out. Camera feed ends. Recorded date, February 2, 2013. Camera feed begins.  This is Captain Mik... This is Captain Mikhail Kuznetsov of the Peregrine 9 mission, reporting in on day 1 of the mission, which has already hit a snag. The first thing we tried to do was to verify the anomalous Hume levels that our more earthbound satellites were able to pick up, but our can't counters don't seem to be functioning properly here. The Hume levels we're reading are fluctuating rapidly, anywhere from almost zero to have surged numbers in the hundreds. If we came all the way here only to have balty can't counters, what a tragedy that'd be. Kuznetsov is seen pausing, and then looking out the viewport. Still, there seems to be something off about this place. We'll have to do more research later. That's all for today, I suppose. Camera feed ends. Recorded date, March 13th, 2013. Camera feed begins. All three crew members are seen surrounding what appears to be a box of some kind. Kuznetsov is seen directly facing the camera. So, today we woke up and saw a box outside. Floating around in the middle of space nowhere, just sitting pretty. We just recovered the object and are about to open it. They panic, alright? Nervous chuckles from the group. Kuznetsov stands out to the side by the ejection port. Moro lifts the hatch on the box carefully and looks inside. It's, uh, CD. Should we run it? Go ahead. Use the isolated computer. It's not connected to anything. Moro runs the CD, which opens up a film on the computer. Following a nod from Kuznetsov, he plays it. The film shows a view of Captain Kuznetsov sitting in front of a camera.  This is Captain Mikhail Kuznetsov of the Peregrine 9 mission, reporting in on Day 35. Still no signs of slowing down the anomaly's growth. We can't get any good data on it either, because we still can't get anywhere countersworking. Still, we will see what we can do, we're the good of us all, signing off. The film ends by this point. Camera feed ends. Recorded date, March 21, 2013. Camera feed begins. Kuznetsov is seen in front of the camera again. This is Captain Mikhail Kuznetsov of the Peregrine 9 mission, reporting in on Day 47 of the mission. Over the past week or so, we've picked up about 12 more recordings of me speaking about the anomaly in question. Kuznetsov sighs, and is seen rubbing his neck. We're still not any closer to answers, though. All of these other versions of myself seem to know more about what's going on than I do, since they all reference stopping SCP-3200. I wish this version of me could know half as much as they seem to. Which reminds me, no, they can't counter still don't work, still not sure why. Kuznetsov leans back and rubs his face. Moro thinks that we're seeing something from other universes, which would explain where these things are coming from. Thomas believes that something is off about the reality surrounding this anomaly, which would explain the malfunctioning can't counters. But we have no idea why that is either. In summary, we have a whole lot of nothing and a lot of questions. That's all for today. Camera feed ends. Recorded date, August 6, 2013. Camera feed begins.  He looks up at the camera. Today marked the 38th tape we've recovered of myself. We've gotten 38 different capsules containing tapes of myself speaking to a camera, just like I'm doing now. And none of them are exactly the same. In each video, I'm wearing different clothes. The date is off, I have different hair, all kinds of things. And I've got no damn idea why. Kuznetsov leans into the camera. What worries me the most is that we still haven't found out any details about what exactly SCP-3200 is doing. We're pretty sure that this is the region of some weird space-time stuff. Moro is adamant that this is a region where space-time is pretty thin, allowing for contact between universes. But beyond that, we just don't know exactly what's happening. Worse, we started finding more than capsules, things like bodies, mine, souls, moroes, and some of people that I'd never seen, parts of shuttles using technology that I haven't seen before, and other scraps of things that I don't understand at all. Kuznetsov shutters. There is something deeply wrong about this place. It feels fundamentally misplaced, that it doesn't belong. I don't know what else we can find here. Signing off for today. Camera feed ends. The following was written in Captain Kuznetsov's personal notes regarding the mission on August 21st, 2013. How many times? How many times have we been here? This is the question that keeps me up at night. The question that has brought me no rest. We are certainly not the first, and every other Kuznetsov out there seems to have been brought low by the same question. We've recovered a log today, the man that I saw on the tape was old, very old. He had been recording the anomaly for a long time, years, perhaps even decades. Thousands of tapes recovered, no answers. He had studied it for years and years, and know where did he find an answer to why this was happening. They say it's a definition of madness is doing the same thing over and over again, but expecting different results. If so, then just how mad are we? On September 7th, 2013, Captain Kuznetsov apparently vanished while attempting to retrieve another tape. He reappeared two days later, on September 9th, 2013, extremely dehydrated and weak. The other crew members report that Kuznetsov recorded this message shortly before lapsing into a coma. We were fools. The void isn't a region where space-time is ruined, it's the source of the tear itself. Space-time itself is rending itself apart, and we're seeing echoes of every timeline in the past and future. Time is an oroboros, devouring itself again and again, only to be reborn. I saw all of it, all of the times we tried to stop it in the past, all of the times that I tried to stop it in the past, and the future. This happens again and again, until we get it right. Over and over again, we try and try to fix it. All times blend together until we reach singularity, and all is lost. The tear opens more holes everywhere in reality, and the anomalies appear faster and faster, but containment is only delaying the inevitable, the inevitable cleansing of the slate. I saw all of the timelines, and we haven't stopped it in any of them. Matibusia, we have seen into the abyss, and by God, it hates us. This was the last recorded event that was stored in the recovered capsule. Given the passing of Peregrine 9's original end date, the expedition is considered to be lost.


Hi, I'm Josh and I have a question That I can't answer because I'm hitting the laser. Are you being the right person for DevOps? Are you sure? How do you know? Fortunately, we have this talk to find out this talk started out because my wife bought this sign and put it in our kitchen And I love it marriage is more than finding the right person. It's being the right person And I think this is an important reminder for all of us The Phoenix project I assume most of you have at least heard of it Hopefully most of you have read it highlights the relationship between the CEO and the CEO and it's described by one of the main characters Is this dysfunctional marriage where they both feel powerless and that held hostage by the other is this the same between ops and dev From the dev perspective, which I know there are many here. Why does it take so long? Why can't you give me what I asked for that wait for all your processes? I'll never be able to get anything done on the ops side. We say, well, why can't you be more patient? Why can't you use what I've provided? What's why is it not good enough without these processes? We risk problems with availability and manageability issues all are perfectly reasonable so being the right person for DevOps is Actually being more than just your role whether you're ops or dev You have to be more about the relationship between the two Ways you can fix this communicate and learn about your partner Identify what's important to them? How do they like to be communicated to what is their communication styles great talk? We had yesterday about differences in communication learn about your your peers and your co-workers Talk less listen more. I mean we've heard this when we were in elementary school You got two ears one mouth use them accordingly. We love talking about ourselves Take advantage of that and let other people talk Hearing is not listening.  That's okay Active listening means that you are hearing what is being said you've internalized and you could repeat that back Right, just remember just because you hear something doesn't mean you were listening Increase your empathy when you're listening and you're communicating so listen actively right be engaged and when you respond Don't respond defensively Respond selflessly think about the other person and be an empathetic or sympathetic if you can't be empathetic to what they're talking To you about which leads to thinking of others. It's not always about you You are just a contributor in the work now This is to diminish your value But what you do impacts other people and you should be mindful of that and think of others While think of not thinking of others consider doing for others be sensitive when others actually need help and Then engage in that help and it's easier when you've actually dedicated time to do that Right apply time in your day or in your week to help other people Also teach other people you have a great deal of knowledge that you can share Experiences that they maybe haven't experienced yet even if they're a senior developer ops person or a junior person Go under the premise that there are no stupid questions.  This one's very very difficult because you have to be selfless sometimes to be trustworthy You have to be honest with people right take yourself out of the equation to agree and be Transparent and let people know that they're getting honest feedback and honest information from you consistently Now we move on to taking care of yourself You have to keep your interest as you work and apply into the work and organizations you do be more than just the work You do all the talk about burnout a big part of that is maintaining focus on yourself and applying those interests Take some me time. Enjoy a vacation. I used to hate vacations now. I love them. I've doubled down I've tripled down on vacations. They're so important and there's nothing better than mental health days Right.  Take the time Invest in yourself expand your knowledge Right understand that you can go more than just being deeper in your subject matter Understand how your subject matter affects other people and affects other systems Celebrate together.  Don't go right to the next sprint or go right to the next project But do we sink right after the celebration and everybody's you know ready to go Because the key here is in order to be the right person for DevOps You have to be improving yourself and you have to be working to improve for other people So the question is is when you leave here, are you going to be the right person for DevOps? Thank you


It's time for the MechEatGab and listener Dan brings us our quick tip of the week with When in the all photos section of the photos app even after you hit select at the top It's tedious to hit each photo individually But I accidentally discovered a much better way to select many photos at once After you're in selection mode by hitting select at the top Swipe from left to right beginning with the first photo you want and without lifting your finger Scroll downwards through the photos. This will let you select all the photos and subsequent rows As you scroll through until you lift your finger This allowed me to insert all those photos that I wanted into a shared album rather quickly More quick tips like this plus your questions answered today on the MechEatGab number 982 for Monday May 22nd 2023


With members of the all-progressive party APC in Benio State continue to challenge the party's primaries, some stakeholders have called on party fateful to come together and advance the course of the party. The stakeholders speak with PLOS TV News shortly after the macro-division of the Federal High Court struck out five cases in favour of the party. Comments like these are in full length a total expression of a democracy. I feel they should understand, not just by perception but by position, that democracy is unifying, democracy is carrying everybody along, democracy is letting everybody understand not the subjective interest but the objective interest. Benway and the people of Benway are and must amend the objective interests. Opportunity now to sit down on the table of brotherhood and do a reflection of the issues that have brought us this far. It is usually said that when brothers fight together it does not stop them from staying united and advancing the course of their family. So we call on well-meaning people like various members of this family, the APC, whoever and wherever they are, that this judgment is a reflection of the fact that there is a need for us to sit together and advance the course of our party. I was also studying a message to all that have lost their cases in court to please sit there as walls and come back. The parties willing to accept them back as members of this party so that all of us will work together for the victory of our party in 2020 trajan elections. So this is a plea from the party that they should please and please come back. We will never abandon them to our lawyer party members if part of all this they still remain our members. So we call on them to please come back to us, sit on the round table and let us continue the journey. So you get notified about fresh news updates.


Michael Walker. Rebecca Long-Bailey is very much going for this as the Corbynite candidate. She's somebody who's taken on a lot of his ideals. Didn't the party show very clearly, didn't the public show very clearly at the last election that that isn't what the general public want from the Labour Party? Well the public showed at the last general election that whatever Labour offered it wasn't good enough but I don't think that is the reason to throw the baby out of the bar for when it comes to the policies and also the positioning when it comes to politics in this country. So for me I'd agree with Tom that it's unfair to characterize Keir Starmer as a Blairite. Who he potentially reminds me of more and I hope this isn't the case as it seems like he's quite likely to win is Ed Miliband. So someone who wasn't quite confident enough to rally against the establishment but also wasn't as right-wing in terms of the Labour Party as Tony Blair. And so what I want to see from Keir Starmer is an ability to talk in terms of economic populism, to talk about how there is still whether or not Labour lost an election in 2019. That doesn't change the fact that CEOs in this country still earn 145 times the amount of the average worker that companies like Amazon won't recognise trade unions in their workplace, work people until they're near collapse and pay pitiful amounts of tax. So I do think the next general election will still be fought on these issues. But those are the issues that this election was fought on and Labour didn't win. The public don't care about them as much as the left in the Labour Party. Well, I'm not sure that's true. So if we look at 2015 when Ed Miliband was standing and when it was a more centrist platform, yes he was to the left of Tony Blair, but it wasn't exactly calling for the mass redistribution of wealth. Labour got 30%. In 2017 when they had a much more ambitious platform, abolishing tuition fees, building loads of council houses and raising tax on the top 5%, they went up to 40%. Now something went wrong between 2017 and 2019. Some people are blaming Brexit, other people are saying Jeremy Corbyn made a few mistakes as leader. Of course he did. But I don't think that is a reason to throw the baby out with the bath water. Interestingly, Keir Starmer at this point isn't saying he will. Keir Starmer isn't saying he should abolish and get rid of all the policy positions that Jeremy Corbyn introduced into the party or returned the party to supporting. I'm just yet to be convinced that he is confident enough to make that case when there's intense pressure for him to drop some of those policies and to become a bit more accommodating to this country's establishment. Tom, if Keir does manage to win, is that concern well-founded that actually he won't have enough support within the party if he does get rid of a lot of the very, very popular policies within the party to take it through to the next election? If he takes the party in a more right-wing direction, you may well lose a huge swathe of membership. Well, I think there's a general consensus that the last manifesto, whether people liked the policies or not, but the last manifesto was a lot too broad. It had too much in it. It had things in it that simply could not have been enacted without a two-term majority Labour government. It was too ambitious, not because the policies were necessarily wrong, although I think people will have disagreements about individual policies, but because it physically could not have been achieved by any Labour government with any majority over the period that it gave itself. I think one of the difficulties with looking at the vote show that the Labour Party achieved over various elections is that that's true as far as it goes, but in the same period the Tories were putting on vote share election after election after election. It went up in the Theresa May, it went up again under Boris Johnson, and the next Labour Party has to start making that vote share of the Tories go down. And that is partly about what policies that leader has, but it's also about being able to demonstrate that the questions that they are trying to answer as a leader of the Labour Party are the questions that the electorate thinks need answering in that election. And whatever you think of Labour's policies to the last election, it's pretty clear that the country did not broadly see it as an election about whether those ideas were the right ones or not. It's an election about whether we should get brexit on, which was the Tories' big slogan. Michael. The job of the next leader is to define the terms of the next election as well as to have the policies that will win it. Michael, in his first answer, Tom talked about Keir Starmer's leadership qualities. Do you think Rebecca Long Bailey, do you think Lisa Nandi have those leadership qualities? Do you think that the people looking at the Labour Party could see any of those three candidates in number 10? In a way, I think it's a bit too early to say. I don't look at any of those candidates and think they're the full article ready for a general election tomorrow. There will be five years until the next general election. I mean, the attraction of Keir Starmer is that he's got incredibly impressive CV. He rose to the top of his field and became director of public prosecutions. One concern, though, is a good lawyer doesn't necessarily make a good politician. So many of the things written about Keir Starmer when he was in the DPP is that he was very good at detail but struggled a bit more with vision. It's when you're leaving a party that you need the vision side. I think Rebecca Long Bailey has demonstrated she can very competently put across the argument that we need radical economic change in this country so that we have a more equal society. Climate change will be a much bigger issue in 2024 than it was in 2019. And she is perfectly positioned to take that argument to the country to say that it's only the Labour Party who are willing to take on the establishment and vested interests who are capable of tackling the climate crisis in a meaningful way. Okay, we're going to have to leave it there. Michael Walker from the Vara Media.


Hello everyone, welcome to another video. So it's going to be a little while before I'll be allowed to go back out into the streets because of the quarantine thing, but we're going to do some reaction videos in the meantime. So what I want you to do is, if you have anything for me to react to, leave it down below. But I wanted to react to a video that I saw recently on Instagram which was incredibly sad, but it's sort of like about how animals mourn each other's deaths, and people think, oh, well, animals, they are just machines. A lot of people think animals are just machines and they instinctually go throughout life without experiencing their life consciously and subjectively. That is the thing that is, you know, automated sort of biological robots or something. But we've seen in the animal kingdom, you know, I don't think I don't know if you've seen like elephants mourning the death of other elephants and, you know, monkeys and, you know, the higher animals like this. But, you know, there's obviously footage of dogs mourning their owner's death. So here in this clip, you can see, see this dog here laying at the gravestone of their owner crying.  Super sad. But, you know, I don't have to convince people that dogs feel these emotions. Everyone spends a lot of time with dogs and, you know, monkeys and elephants. People like, you know, who sort of collectively agree these are sort of intelligent, emotionally complex beings. But a lot of people actually go out shooting deer and this video here is the one I'm going to talk about. So in this clip here, you can see this deer here is mourning the death of another deer. And there's a couple of hunters there who have, it looks quite obviously have shot this deer here. So let's just have a look at what happens here. So look, what does this hunter say here? So it's something that you have to hunt though. Now, as you can see here, this, I guess this is, I don't know much about deer, so don't quote me on this. This looks like a buck, maybe a male deer. Correct me if I'm wrong. This looks like a female deer, a doe, like the hunter's saying that must be trying to cull them off.  This other deer has risked their life to come up and try to help their friend. Now, deer are so often hunted that it's just the most speciesist thing you could ever think of. Nowhere in society usually would you think it's morally acceptable to just shoot animals because of population control. I mean, I showed you dogs in the clip earlier, people wouldn't think it's okay. A lot of those dogs, a lot of them might be stray dogs in Thailand. If I went out with my 22 rifle and just started shooting stray dogs, because they're quote unquote overpopulating in Bali in Thailand, you know, you just think I was insane. But with deer, it's like this mentality towards deer. It's fine. It's totally fine.  But look, as you can see, this deer here risking their life to help their friend. I mean, that shows courage. It shows emotional connection to their friend. It just shows character. This particular deer has character. And you know, these hunters could have just shot and killed this deer because of it. But, you know, just anyone hunting out there, come on, dude, what are you doing? Like, it's just murder. This is just a deer has been murdered. And another deer's mourning the death here. Like, doesn't that doesn't that make you feel something in your heart? Like that hunting is wrong. A lot of people use this hunting justification. Oh, no hunting for, you know, conservation and overpopulation. And it's just an insane justification. It's not even true to begin with. And even if it was, it wouldn't justify culling the animals. We are overpopulating, we are destroying the ecosystem more than any other animal on earth.  There are other ways of solving the issue that we should entertain. Now, what I want to say, it's not just dogs. It's not just deer who do this. Pigs also do this as well. And I don't know if you guys have seen this. See this pig, his or her friend was about to be murdered by these people. Boom. Pig runs up to try to help them. Boom, get away from my friend. Trying to save their friend. And I've seen if they're okay. See, terrified animal is about to be murdered. And they're laughing. They're laughing.  Like chickens, obviously, there's so many more chickens that are being slaughtered.   But look at this, the way this pig just runs up to protect their friend here, runs up, get out of my way, get out of my way. What a beautiful thing here. And incredibly sad that these, both these animals would have been executed without mercy. And this would not have stopped these murderers, these, you know, look, these people here from cutting these, both these pigs heads off. And that's just a reality of society. It's a, where's the compassion?   And no, but they both ended up getting their heads cut off anyway, like, no mercy, no mercy.  And one of them has passed away.   These animals are treated like meat machines, objects executed en masse in terrifying gas chambers, which are filled with feces and urine. And just because they are defecating and urinating all over themselves in these gas chambers and extremely horrible place, the gas is terrifying to inhale for these animals and it burns their eyes and insides when they inhale it, load it into a dungeon with all their friends they can't escape.  And look at them, look at them, right here, mourning the death of their friends. Now I want to leave you with one of the most chilling scenes on this topic that I've actually seen and I did respond and I did react to this in 2017, but I'm going to react to it again because it is one of the most chilling, saddening scenes I've ever seen. It's really a damning indictment on human beings that we do this to these non-human people, treat them with so much contempt and disregard. Look at this. So what's happening here, I don't know what country this is in, but a cow has been executed, chopped up into pieces, their skin is laying across this staircase and bits of their body are scattered out like on the floor here to be sold and their friend, another cow, has come up and realized that this is their friend and is in shock at his bellowing out, you know, in sadness that their friend is cut up on the floor here. The cow knows this smelling the hair, knows it's his friend. Listen to the pain. Listen to the pain in this cow's voice. How terrible. People are standing around filming. Like, can you, like, where is this humanity? There's a guy here in the background filming as well. Like, are they laughing? I don't know. Like, he's smelling the body of his friend. Incredibly sad scenes here. Like, I don't understand how human beings can do this to these animals. Like, come on. It smells like blood. Are you telling me, right?  They're not filled with fear in those moments. Like, I do not care. You get me the most, you know, humane, temple grand and approved slaughterhouse, RSPCA approved slaughterhouse and you show me images from inside there. You tell me that those cattle do not know that they're about to be slaughtered and even if they didn't know they're about to be slaughtered, that does not justify exploiting and executing animals. These animals deserve the right to live. They deserve the right to their own bodies and they are born into this existence and experience the world around them. They are not objects. They need the right to exist. I believe that animals are born with that right to exist in freedom already and humans come along and breach that right to exist. Human beings have universal rights protecting them. They are still breached in some parts of the world and, you know, people still murder people but they at least have laws protecting them. These animals need laws protecting their rights. As you can see, they're born for their friends. They are in the world and they're aware of it. Even if you find certain animals that don't display this trait of mourning for their friends, the fact that they are experiencing reality around them is enough for them to deserve the fundamental right to exist in freedom. The only interfering we should be doing with animals is when we are helping them, protecting them, etc. So, I hope this video has opened up your eyes for anyone who's still eating animals, for anyone who's hunting animals. Please stop.  Incredibly sad. Now, put yourself in the animals position, try it. Put yourself in the animals position, how would you feel if someone was filming you, you know, laughing that you just lost your friend and they got shot in the head and they're filming you laughing and like, come on, we need to do better. And for those of you who are already vegan, thank you so much. Keep speaking up, keep sharing videos like this, helping people to connect the dots. So, that was those videos. Incredibly sad. If you have any other videos you would like me to respond to, it could be someone saying something about, you know, animals or, you know, just someone saying something ridiculous or something interesting that you've seen, leave it down below or send us an email at joeycarvedrungatgmail.com and we'll see if we can respond to them before we get back out in the streets and talk to some people and do some other forms of activism. Thank you all and I'll speak to you all soon. Hello everyone. This is an announcement that I'm going to be speaking at the vegan camp out in August. So, vegan camp out is the UK's biggest vegan festival, three days of camping, amazing talks, activism workshops, live music, after parties and of course, amazing vegan food. So, some of the other people on the lineup are Russell Brand, Bosch, Chris Packham, Fiona Oaks, Patrick Bobomian, I hope I pronounced his name properly then, Genesis Butler and my mate, Cosmic Skeptic. So, it is currently scheduled to go ahead following a government update that large events can go ahead from June 21st onwards. So, over 80% of the tickets have already been sold, so if you want one, head to vegancampout.co.uk and get yours and I'll see you there in August.


The Mises Institute has a new free book for minor issues fans, Dr. Guido Hulsman's How Inflation Destroys Civilization. Learn how inflation isn't only making us poor, it's harming our culture, meant a well-being, and the moral foundations of civilization itself. Get your free copy today at Mises.org slash Issues Free. Hello and welcome to another episode of the Minor Issues Podcast. I'm Mark Thornton at the Mises Institute. Everybody on Wall Street is begging for the Federal Reserve to cut interest rates. They say money is too tight. Mortgage rates are too high, they complain. Refinancing isn't available for commercial real estate loans. Many mumble. Politicians are now starting to chime in thusly. Senators Brown and Warren, for example, were calling for rate cuts by the Federal Reserve. But despite all these pleas, the Federal Reserve stayed pat today. That doesn't sound like the Fed. They are in the business of printing money in various ways. That's pretty much all they do. Sure, they raise and lower interest rates, but it's money printing that makes that happen, too. Is the Fed just a bunch of tight wads lately? Only recently has the Fed actually shrunk the money supply for the first time in a generation. The reason they are doing that is because they ignited too much price inflation from printing too much money during COVID. The one rule of the Fed's game is that most people lose no matter what the Fed is doing. For a few people, COVID was like a manic wealth creation party where every investment skyrocketed, doubling on average. While the rest of us were being locked down and being forced to be jabbed. Now, after inflation is not transitory after all, the Fed is being, quote, higher for longer. And yet, the S&P 500 stock index is a little higher than its COVID peak. So what gives? Well, the Fed is running tighter monetary policy in two respects. They did increase their policy interest rate, which means mortgages, business loans, credit card interest rates are higher. The same thing for certificates of deposit and money market mutual fund. This caused the regional bank failures and it's turned the balance sheets of banks, companies, and even the Fed itself upside down. Their assets, all their bonds have actually lost money. The Fed has also reduced their balance sheet a little bit. This means that they are selling bonds such as government bonds, mortgage, back securities, agency bonds, etc. that they have lost money on. But don't worry, the taxpayer will pick up that tab as well. Whoever buys the bonds gives up cash and reserves that otherwise would be used for private investment, draining credit from private markets. The amount of tightening, however, has been relatively small and they are already talking about curtailing quantitative tightening. Among the many things the Fed is silent on and Wall Street is also mute is the acts of the Fed behind the curtain in activities or policies using non-traditional policy levers. The big one is what's called reverse repo purchases or agreements. This is very complicated accounting operation that makes the old shell game scam where you have to guess which shell the marble is under, look like child's play. The Fed started the game in 2021 selling these repo agreements to banks withdrawing liquidity from banks with a promise to return the liquidity plus an interest return to the banks in the future. By mid 2022, they had taken almost $2.5 trillion out of the market. That amount stayed about the same for one year until about mid 2023 when stock and bond markets started to crater. That's when they started returning the liquidity to the market, unwinding these reverse repo agreements. There's only about $600 billion in reverse repos left of the $2.5 trillion that the Fed had at its peak. Although rarely mentioned, reverse repos were a major aspect of the Fed's tightening and since mid 2023 have been a powerful tool for easing monetary policy. Jay Powell's tighter for longer stance was not quite true, as this has been a nearly $2 trillion monetary injection. That figure completely swamps the Fed's quantitative tightening program that is supposed to sell off much of its holdings of treasury securities and agencies bonds. But it's actually done very little to reduce the overall Fed's balance sheet. If you compare their reverse repo agreements with the quantitative tightening program, it would seem that they first cooled off the stock and bond market and the unwind of these reverse repos since the beginning of 2023 has helped stimulate the stock market to new highs and save the bond market. So behind the scenes, the Fed has really not been a tightwad after all, but has actually been engaged in monetary easing for quite some time.


Actor Johnny Depp has concluded his testimony in the defamation case he filed against ex-wife Amber Heard, saying he is the victim of domestic violence in the relationship and is broken by the time their marriage fell apart. Depp's fourth day on the witness stand in the Virginia court ended with his attorneys playing audio from a conversation that took place after Heard had secured a restraining order against him in 2016. In the recording, Depp proposed that the couple issue a joint letter saying they loved each other and the media had created a storm around them. The suggestion was an attempt to find a peaceful settlement according to Depp.


We're here to finish the debate. Is overhead press good, bad, cool, or not? Dr. Mike Isretel says it's not great for building delts. My boy Omar Esoff says it's the coolest lift for a lifting enthusiast, and I'm gonna tell you the truth, how to build your shoulders, and what the overhead press is good or not good for. We'll go through the checklist.  That's not who I am, I'm the honest man. If you wanna increase your bench press, give it a little check mark, we should build shoulders straight, but we probably shouldn't build the OHP per se. If you want to build your shoulders, we should train an overhead position, but probably not the standing OHP. Now, if you're a weightlifter, a strong man, or an overall gym enthusiast, I think OHP is probably at the top of the list. It's very difficult, it's hard to pursue, it builds your entire body's connection and stability to press something heavy overhead, which is like the most difficult thing to do. There's lack of stability everywhere, and you gotta get rigid in your core, tight glues, tight quads, and it builds your pressing strength. But again, that doesn't really transfer or is the best to build the delt itself to look good or to build your bench press. Let me show you some of my favorite movements to actually help build the biggest shoulders you got. OHP for bodybuilding, I'd probably just ignore. If you're doing standing barbell overhead or standing dumbbell overhead, I think you're probably wasting your time on building your delt. Side lateral from a cable, even like a Y-Race, which I'll show you, or a heavy press is best done with stability. So, a machine, a regular chair dumbbell press can work, so you have a back to keep you stable, and then we can really focus on building the shoulders themselves, and that's kinda it when I'm talking about building the muscle. We're talking about weightlifting and strong man, especially strong man, you have to get used to throwing a bunch of things overhead, so getting generally strong at doing overhead, using your kinetic chain stability rigidity with a barbell overhead will translate to the axle, to the circus press, and all the different overheads you have to do, which I think is great. Same idea when we're talking about weightlifting. They obviously have to catch with locked out, stacked arms in the snatch and the cleaning jerk, but the stronger you can make those muscles surrounding the joints, the more comfortable you're gonna be doing that. Although they won't be able to strict press what they clean and jerk, it's gonna be heavier, it'll still allow for the stability and the comfort overhead positioning, so standing dumbbell, standing OHP, I think are great for weightlifters, strong man, maybe even a core piece that should be a pillar in their training. Talking powerlifting, law specificity always applies, if you wanna be a good bench presser, you got to bench press. Focusing too much on the overhead or other movements is probably a waste of time. We do wanna build our shoulders, and there's some people that have success with the overhead press translating to their bench, but generally speaking, the kinetic change too long, there's too much instability to really focus on your pressing, and again, the technique of overhead versus an actual bench are completely different movements. So I'd focus on more building your joint and your muscles like a bodybuilder and then focusing on the bench press itself like the skill and athlete. Last piece is general athletics, and I love the standing overhead for a lot of people. We'll do standing push presses with a medicine ball for kind of our plows and our power. We might do something like a push press, a slight momentum dumbbell press standing or overhead, and then we'll build the muscle itself through lateral raises. So when I'm talking about athleticism, we kind of have those three tiers that we focus on, building the muscle, translating into strength, and then strength and muscle translating into power and moving medium weights fast. Those are kind of the categories I look like. When we're talking the OHP, it doesn't make it good, doesn't make it bad, but it probably makes it suit for your goal, for your task better or worse, depending on your overall goal.  I train my barbells a little bit heavier. I like to do singles, double shriples, and the squat bench dead. Overhead press has just never been my favorite movement, although I love pressing heavy overhead. I just don't do the OHP in specific. So I'll do my barbell movements, if it sets a one to three, then everything else sets a six to 10. Close to failure, more bodybuilding, hypertrophy driven. I am currently cutting, so all that just works great. And for your training, you can build muscle, you can build strength a million ways. It's just really what you enjoy, what you want to compete in, and then how long term you can stick to it. And if you're having fun, you're gonna be way more likely to stick to a long term. So for me, it works. Heavy bench press, little bit of machines to catch some hypertrophy. I'll do some accessories afterwards, my delts and my tris, catch a nice pump. But for you, don't let anyone judge you what you do or don't want to do. It doesn't really matter at the end of the day, but if you are trying to be elite or competitive in certain sports, in certain positions, there's different exercises that you can implement that are probably more optimal for what you're looking like. Man, 3sme.co, one of our biggest drops coming very, very soon. We've got hoodies, sweats, everything available on the website. I appreciate you, goodcompanydiscord.com. Be a part of something big in yourself, be all man. We over me, son of Mike, I'm out.


Now there is portfolio assessment. It's another way for alternative assessment or a big comprehensive assessment. The process of observing, recording and documenting the work that children do and how they do it as a basis for a variety of educational decisions that affect the child. Portfolio is a collective showcase of all the activities of the child. For example, if he made a card today, then he tried to make a small doll tomorrow. And the next day he took a small recipe and made something with the help of that recipe or cooked it and then took a picture of it. So the thing is that all the activities including academic activities, play activities, group activities, whatever he has been doing, his record is gathered in the form of a portfolio. And the teacher guides him. For example, if there is a good book or diary in which all the activities or accomplishments that he had done, they are all in it. This tells us about his constant progress. For example, if a child is confused in the beginning, then he makes such pictures or shapes that are not perfect yet, they are not perfect. So slowly he comes towards perfection, towards mastery. So we get to know how his progress is. So Portfolio is an effective tool to motivate, encourage and instruct children. When you tell the children, first of all, we did this kind of work. And now we have done a much better job. And this project or this activity is much better than before, then the children are motivated. You tell them that you are improving. You are also happy with him, you are giving feedback to the children. It is a great success for him too. Portfolio is a mechanism to monitor and improve the instructional skills and curriculum modification. Now this portfolio is not for a single day. Portfolio is made for all the children's section. First of all, it is in class 1. So from the first day to the last day, where important activities will come, all the activities, his good tests, his good projects, his hand-made pictures, and where he made a small speech, his pictures.   From what direction he did it, how creative it was, from where he achieved it, then we have a long-term progress. Assessing children's behaviour in programs where the goals are very concrete and are uniform for all children who participate in the program. So what are we doing? We have set many goals. Whenever we work in a curriculum, we set up learning outcomes for the children. We have to modify their flan-flan behaviour, we have to teach them the flan things, we have to complete the flan concept. So all those things tell us in the portfolios whether we succeeded or not. And if there is some deficiency or deficiency, then what do we do? We go to our curriculum and modify it, revise it, that we didn't have to tell or not teach like this, but we had to adopt a new method so that the learning outcome we wanted would be completed. Assessing children where the purpose is to rank them quantitatively or in a standard manner. So because this is a written record, a long-term record, and all these things are included in it, therefore, if you want to take a final decision based on this, if you want to judge a child, if you want to grade them, then this will be an authentic assessment. Do you remember when we were talking about alternative assessment? So we said that alternative assessment is authentic. The one-time paper-pencil test cannot be authentic because we judged it at one time. Assessing children for the purpose of comparing them to one another using standardized norms. So now because we have made some learning outcomes, we are seeing how far our child has reached the learning outcomes, so a standard that we had already thought of, we can compare the children against it because we have norms that if the child comes to this level, it means that there is such a scale or capability in it. After this, the average child has become, now this has become above average, so we can do a complete process with the help of this. Because we have a long-term progress in front of us that tells us better about the child's progress.