This is sharp storefront conjure has created fully automated stores on wheels. Using the conjure app, you can hail a store in a matter of minutes. The autonomous vehicles show up. The doors automatically slide open and you can choose the products you want. Using the RFID tags, your account is then automatically built only for the items you selected. You don't have to talk to the driver and all the options are truly at your fingertips. In this episode, we talked with Ali Ahmed, the co-founder of conjure, about how they broke the internet at CES in 2018, why they decided to launch specifically with ice cream, and the implications of store-hailing for industries outside of ice cream, including grocery stores, markets, and alcohol. All right, welcome to the podcast on today's show. We're talking to Ali from conjure. Thanks for coming on. For people who don't know, what does your company do? Thanks Diego. It's great to be here. conjure is an app where you can tap one button and hail a shop on wheels to come to you. So you don't have to create a basket. You don't have to wait for a delivery person to go pick up the order. The shop comes to you, so you can shop for ice cream, snacks, and food on the go right at your doorstep in as little as two minutes. So what I love about the idea is that it makes a lot of sense in my head. So instead of the whole Uber Eats model where it's like you just order a very specific item, you're giving the person, the consumer an ability to order from their favorite shop. So whether I love, let's say Pink Dot in LA or some ice cream shop, I know you guys are launching with ice cream. They can go ahead and basically pick their flavor from the cart, right? Absolutely. For you, when you first thought of the idea, what was the problem that you saw? What was the thing? And I say this in a way of like, maybe you personally were like, okay, I want this flavor, but this shop doesn't have it. And now I have to accept it. What was the problem you saw that you wanted to fix? So the problem actually stemmed from my experience in on-demand delivery. And I'll go a little bit further back. So my co-founder, Imad, we're three co-founders, Imad, Tigran and myself, Imad and I used to work in about 12 years ago in the ice cream and food business. And he had this idea back then. So 12, 13 years ago, he came up with a concept of being able to hail a shop on demand. And this is before smartphones. So his idea was to pick up a rotary dial phone and say, bring the shop to me and then hang up. Like an ice cream truck. Ice cream truck, but on-demand. Got it. And then his vision expanded to all sorts of retail categories, grocery and others. And it was just too early, right? So we parked that idea. This is before Uber? Do you mean like when you say too early? I'm talking about 2005. Okay. So way before. Way before. This is just, I think before the App Store even came about. Yeah, the App to trade. App Store was like 2008, 2007, 2008. And so what we did is we parked that idea. And I worked a group on for a while, the tech startup. And then I started a number of businesses. So I then started an on-demand delivery company in London. And at the time, this is 2015. So you moved to London? I was actually in London. I graduated. I had an MBA and then I did another master's from Lancaster. And then I started my first company in Lancaster, moved to London and then worked a group on in London and then decided to start, you know, my own business. So this is like 2008 group on? 2010, 2011, correct. And it was my city deal and it just got acquired by Groupon. And it was exciting to see, you know, the pace of activity at that time with Groupon. You know, it hasn't fared too well now, but at the time it was one of the fastest growing businesses. Well, they got lucky because they had the recession. The recession hit at the right time and every one was looking for a deal and everyone had a Groupon type company. I remember Brad Feld had like Feld's deals. I think he also invested in Groupon, oddly enough. But anyway. Okay. So you're there. It's 2010, 2011. And then I started a startup doing, you know, video messaging and we worked with Sony Music. But then in 2015 I started Dispatch, which at the time became the fastest growing on-demand delivery startup in the UK. And the idea was unique. It was different to your typical Uber Eats and DoorDash and Deliveroo in the UK in that you could request anything by sending a text message and we would find it, buy it and deliver within the hour. Anything. Anything. More than a million pounds worth of requests in the first 20 days of Dispatch. Wow. What was the thing that we're mostly requested? I'm just curious. So Furniture was one of the biggest categories and we kind of dug deep and found out Ikea would take a week and charge 40 pounds delivery fee. So we decided that we can charge the same and have it to you in two hours.  And we would have a network of drivers. We had about a thousand in our network. But Furniture was one big category, but then a lot of it. We did everything but food. And so at times we were getting orders for 10 HTC vibes for an event. We would get orders for Argos as a big retailer in the UK and so we would get typical Argos orders where people just didn't want to book it and then have to go pick it up. That's their model. So they would just use us to do it. Okay. So you're familiar with the space. Very familiar. Very familiar. I spent a lot of time trying to make on-demand delivery work. What happened with Dispatch? Costs were too high. The labor? The labor costs are too high. You have a driver and in our case you also had what we call an operator that would have to find the product. They would have to check availability at the stores, check multiple stores and then make sure that they route the driver to that location to pick up. And we were ending up charging 11, 12 pounds on average, which is about $16, $17 I guess. Delivery fee. People were paying it but at the same time it just couldn't scale. So I moved to the US in 2017. Did the company shut down or did you sell it? Yeah. I mean, I guess it's still active so I had a little bit of exit with my investors and I moved to the US. And it wasn't a huge success to be completely honest. It didn't really, that model didn't work. But as soon as I got to the US I got back in touch with the Mod, my co-founder and told them about my experiences and on-demand delivery, the challenges I faced and he harkened back to that idea that he had about 13 years ago. And he said that by delivering the store instead of goods, we can create a model that will always be faster, cheaper and more convenient and more profitable than delivery. Is the idea there, if you bring them the store, the sort of the price per ticket, the average ticket goes up higher? Is that the idea? That is one of the ideas. Absolutely. That people will spend a little bit more in theory. But more critical is the reason why on-demand delivery doesn't work is because of the order pickup. So if you think about it, with certain services like Amazon and others, you have batching, which is an important concept in delivery to reduce your costs of labor. But with on-demand delivery, there's no batching. You have to go pick up every single order and then deliver it. Or you batch once, essentially. Basically, you're batching once. But by getting rid of the order process and not just the order process of creating the basket, but also the order pickup, our model has all the inventory inside roving vans. But if there's a roving van outside you right now, you tap a button, 30 seconds will be there. Just like an Uber. Might take five, six minutes. Like an Uber as well sometimes. But that's the idea. It's more akin to ride-hailing than to delivery. And it sounds like you started with Ice Cream just because you had sort of a product expert in that world and Ice Cream seemed to make the most sense. Absolutely. With my background, on-demand delivery, Imad's in Ice Cream. And Tigran, who's our third co-founder, and he found out about us, his background is in robotics and automation. We're the ideal team for Conjure. And then who did you launch with? So you're in LA, of all the Ice Cream shops, you pitched them. Which one was like, oh, I get it, I want a partner. So it'd be helpful to tell you a little bit about the history, right? So Imad and I decided to go all-in. Early 2018 we went to CES. We worked with this expert in the motorcycle industry. And he created a prototype, a three-foot-long prototype of a self-driving grocery store. And we christened at Fuji and we took it to CES. And we painted this future vision of stores that you can hail to come to on-demand that are fully automated. And it kind of blew up when we went viral. The concept of self-driving store was unheard of. And Tigran found out about us from some of the coverage after the show. And his background, he's been working for seven years. He built autonomous forklifts and warehouses and self-driving vehicles. And so it was opportune time to bring him on board. Neither Imad or I are very technical. And so Tigran joined at the right time. And so the long play of this is these are autonomous vehicles, autonomous stores. Absolutely. That is still our vision. But what we've done is we were called Robomart. And we actually built a full-sized, fully autonomous store on wheels. There's no driver. There's no place for a human to be in. There's no steering wheel. It's a fully autonomous vehicle. But we built that to showcase the vision, right? And what we've actually done is put drivers behind the wheel, but tinted the windows and the windshield. So you never see the driver. You never get in touch with the driver. It's a fully automated experience for the shopper. And that's going to be the same exact experience when we have fully self-driving vehicles in the fleet. And is it hard from a scanning perspective to know what people take? No. We actually have built our own proprietary system. We use off-the-shelf RFID parts. But the software is what we've built. And we track every product. So for example, if you want to grab this water bottle, as soon as you take it out, we know it's no longer the store. You put it right back. We know that as well. But from the time the door opens to the time the door closes is your shopping engagement when the door closes and the shop leaves. So you say it's an RFID tag? Correct. Okay, got it. We know then that it's no longer in. And that's your basket. So whatever you've taken out is what you get charged for. CVS does that a little bit now. They do RFID tags on like deodorants because I guess those get stolen a lot. It's kind of weird to see what products they put it on. They do it at clothing stores as well. Yeah, yeah, yeah. Which makes more sense. It was just weird when I literally bought deodorant the other day and I was like, what the fuck? There's an RFID tag on this. This is the weirdest thing. That's interesting. And so the big vision here is autonomous sort of markets. And then why the decision, again, to just to go back to the ice cream. Why the ice cream first? Ice cream is the ideal category for what we're doing, right? Unpack that. Unpack that first. A lot of people don't realize the average American eats 20 pounds of ice cream a year. And three out of four have it more than once a week. It is one of the most consumed, it is probably the most consumed dessert in the U.S. and probably globally. That's my wife would agree with you. It's crazy. And the biggest challenge with ice cream is that it melts. If you go to the store and pick it up, it's probably a 15, 20 minute round trip. The moment it hits your basket, the shot clock starts. It's getting softer as it goes. Getting softer sometimes. Okay. So the way you guys look at it is what's the problem? The problem or the food with the highest problem is something that is melt ultimately. Absolutely. And then something that gets consumed at a rather high rate. At a very high rate. And then the intersection of that is ice cream. The intersection is ice cream. The critical problem is time, right? We're saving people time by bringing the store to them. But with ice cream, there's that additional problem of the fact that it melts. You won't believe how many times we've not only heard from people but experienced ourselves that if you order ice cream for delivery, they will sometimes leave it at your doorstep. Yeah. Not even ring the doorbell. Yeah, yeah, yeah. I'm just curious as to what about hot products? Is that harder to do than refrigeration in one of the vehicles or is that just something where you guys were like, look, we know ice cream. I'm going to start with ice cream and then hot products. Obviously, I have a similar friction point, but we'll just do that later. Exactly. Yes. We absolutely see ourselves getting into hot food as well. The way that we want to ramp up, we did our beta with snacks. And during the beta, we averaged nine minutes across all orders for almost 10 months. And so we really proved out the model works. We were doing on nine minutes that equates to about five orders per hour, which is more than twice as what delivery can ever average. And then in terms of like the revenue model, how do you guys, is just like a service fee that you're taking, a delivery fee? So we work directly with the CPG brand. So we get preferential pricing from them.  Exactly. So you get the wholesale pricing. Absolutely. And, uh, and so we do have a markup on the goods, but even with our markups, it's still 20 to 30% cheaper than your regular 7-11 or convenient store. So it's almost a parody with, with supermarkets. And so how has it gone with the ice cream, the beta testing? So we did the beta with snacks and now we're about to launch ice cream. So we have not launched ice cream, but the response from the beta for snacks itself, we had 90% repeat usage. So somebody who used it once, they came back again and again. My brain, it just goes nuts when, when it's, that's why I enjoy talking to entrepreneurs. So I get ice cream because you guys know ice cream. But when you think about like, like, is there an Instacart play here where there's got to be so much data for all these grocery stores as to like what people are ordering, right? For delivery. And so then it's almost like, or even on the food side where a certain restaurant will have three bangers, those bangers are always available. And so is there a play here for you guys to sort of go, we can become the grocery store on wheels because we have the data maybe via a partnership or something like that. And then it sort of solves the last mile problem for the Instacarts of the world. Is there something there? There is, yeah. When you think about data, right? So the type of data we get, the granular data is unlike what retailers can get from anywhere else or brands can get from anywhere else, right? This is at point of consumption when someone's already decided to buy. So in the CPG world, this is called first moment of truth and second moment of truth and I think the third moment of truth as well.  There's three separate occasions that you have to go through. We boil them down into one. And similarly when you think about every neighborhood that we serve, the kind of data that we get, we can help CPG brands and retailers tweak selection to understand what sells what in the best way. And really offer consumers the best assortment possible. I also think about it from a real estate perspective, right? And so if there's a certain zip code always ordering the same ice cream truck, then that gives me data to say I should be there as a brand, right? I should open up an ice cream shop or on the contrary of that to say, we're gonna test this market. Let me call conjure up. Let's do a test in a zip code I might not know anything about. And then just see, do some promotion, some marketing. And let's see if I have any attraction to that market, right? And so then it's almost like you're creating a retail shop on wheels, but without the upfront cost permitting. Absolutely, exactly. So I think, I actually think that, that's really interesting without the rent. But I mean, it's like, it's far cheaper. Exactly. Percentage is, you know, yeah. And so I think that's where my brain goes. It's interesting where you can almost do this like free beta testing. I'm just curious though too, when it came to the autonomous vehicle portion, obviously San Francisco has been testing this stuff forever. Did you guys try to do anything in San Francisco with the little model you made or? So yes, with our fully built prototypes. We actually, at the time, we did a partnership with Stop and Shop. They're one of the biggest supermarket chains on the East Coast. And we tried to run a pilot. Permissions are tough and getting regulatory approval is gonna take time. But what we realized is that we can put drivers in our vehicles, but still have that fully automated experience for consumers. And because of our model doing so many orders per hour, even with drivers, we're extremely profitable. So eventually the plan is to move to a fully automated model with self-driving vehicles. But we can afford to let that happen naturally as the market, as the technology matures, as the market and regulators approve it. Yeah. You know, we can afford to take that time. What about cannabis? So we've been approached by a lot of players for cannabis. It's one of the most popular categories. I guess it's tough because it's a cash business though, right? And so the transaction maybe gets a little difficult. There's a lot of other regulatory hurdles around cannabis and alcohol. Especially in California, there's a lot of rules. Might be something we look at down the line, or it might be something that we work with partners to offer them a platform for them to do it themselves. Yeah. All right, so people listening probably getting excited. They want to order ice cream, blah, blah, blah. How in relation to where you see your growth going? So here we are Q1 2023. What's on the roadmap for you? And so you're about to go ice cream. What can people expect in like Q3, Q4 of this year from you and your team? So we're going live. Our first pilot is going to be with Unilever, our partner. They're the biggest ice cream company in the world. They own Ben and Jerry's, TALENTI, Magnum, Good Humor. And so it'll stock their products at the start. Brand agnostic, or all the brands? So we will. So at the start, we're going to partner with them and have their brands, but they have a very full selection. I've got a lot. 35 SKUs across TALENTI is one of the most popular. And then our pilot with Mars will kick into effect. So we'll introduce Mars brands, Snickers, Twix, Dove Ice Cream. Candy truck. M&M sandwiches, absolutely. No, no, ice cream, within ice cream. Okay, okay, I got it, still ice cream. The M&M sandwiches, the Twix pints, and the Snickers bars. A lot of the impulse buys for ice cream. And then we also have a partnership with Cool House, the urgent company. So their products will then feature into our ice cream shops. And by Q3, Q4, we've already signed up a number of restaurant partners. So it's still early days. That's what I want on your list. Absolutely, absolutely. David Coe is a partner of ours. Q3, Q4. Little Fatty is going to be having their product inside our shops on wheels. I just thought of this idea. So imagine I'm throwing a party, right? And then it's maybe midnight, we all want some ice cream. I conjure, do I conjure? Just like a big ice cream truck.  See, that's cool. In minutes. You could even do that for like weddings. You know what I mean? You know, like the late night crowd, they're always wanting something at the end of the night. That could be a massive opportunity. I just think about that because it's also cool. It's like, let me get my conjurer. In terms of fundraising for this, I'm assuming you've fundraised probably. When you speak to investors, do they get it? Is there something like, does it feel too soon? Because the autonomous portion, what is some of the feedback you've got just from people looking at your deck? We've been fortunate. We've raised from some really great investors. Hustle fund. The CES, I imagine, helped you tremendously. It did. We actually closed investors at that show in 2018. And so we've had a number of great, mostly pre-seed investors like Hustle Fund, Wasabi Ventures, Automation Fund here in LA, Julie and Sarkin. And recently on the East Coast in Baltimore, we have W Ventures that have invested. So we've been able to have some great pre-seed investors on board. And we're now kind of really focusing on launching. And we'll then start looking at raising additional funding when the time's right. Have you had any discussions with the Postmates, Uber Eats, Instacarts of the World just to gather interest to see? Because in some way you're kind of providing the future in some way. Or just a different experience, right? We have, yeah. It's tangential, but it's related. It is, yeah. And so some of them have approached us, right? So we've been very fortunate, I guess, with the uniqueness of the concept. We've been fortunate that a lot of partners and players have approached us. And so some of the players you mentioned have also approached us to kind of learn more about store hailing is what we call this concept. And how store hailing can fit in with their plans. Whether we would white label or platform or be, you know. And it might be something we explored down the line. But right now we want to give consumers the best possible experience. That means that we control the assortment, we work with brands directly. And eventually the plan is to then work with chefs, work with restaurant directors and be able to offer the best food, ice cream, snacks that you can get. Yeah. I wonder, again, there's so many ideas. So we had Let Us Grow on the podcast, Let Us Grow, you know, they make like. I know them, yeah, yeah, yeah, absolutely.  I don't know, kind of interesting, maybe like a marketing play for them. We've been approached by companies like that at that space. So there's companies like farming, right? Exactly, indoor farming companies that have explored, putting on their units inside vehicles, inside our vans. Again, we're just scratching the surface of what's possible with store healing, but we want to be hyper focused, right? We don't want to get distracted in different directions. Eventually, by creating the platform for store healing, we can enable a lot of different use cases for being able to get anything in minutes. Yeah, I love it. I love it. Tell people where they can find you, where they can download your app and when, when they can get some ice cream. For sure. So, you can go to www.conjureinc.com, that's the website, and the app is live on the app store, but right now it's in limited testing. So hours are not, you know, we're really not live yet. What hours do you guys test? We do on the weekends. We do just a few hours on the weekends, but again, it's just testing right now, but very, very soon we'll be making an announcement that we're live. Oh, making an announcement. We would love for people in Hollywood and WeHo to try the service. Okay. I'll tell you, it's one thing. There's a bar next door and they're always asking me to open up the coffee shop to give them ice cream. Really? Yeah. And so it's an, but that, that's like a 8 p.m. to 2 a.m. So I don't know what, what are the hours people are getting ice cream? Once we go live, it'll be 4 p.m. to midnight. Okay. So that's the after dinner. And we'll tweak the hours. Again, every store might, every neighborhood might have their own hours and we can work with different partners to set their own hours as well. I really, really am excited about restaurants. I think restaurants on wheels, it goes back to the concept. If you've ever watched Fifth Element, the flying restaurant that docks at his, at his apartment and there's a chef cooking up, you know, obviously it'll be more automated than that. But, you know, that idea, do you think that's the future? That's even more interesting. Like the chef actually cooking it up. Again, we'll see how it kind of plays out, but the idea of stores coming to you is something that has been, you know, I'd say in science fiction and also in reality, you've seen the concept play out. And now it's just a matter of time. We're making a reality and we're not the only ones. There are other players that are focused on this roving shop model. So there's like Mancho on the East Coast that are doing pizzas. They're finishing them off. There's Stellar Pizza, which is sort of this robot that makes pizzas here in LA. There's Stellar Pizza and their model is not so much on demand. It just goes in parks at different locations. Yeah. But the concept of roving shops is now gaining traction. Sure. And we're sort of leading that, that industry wave. All right. Thanks for coming on the podcast, brother. Diego, thank you so much for having me. It's a pleasure. Thank you. Thank you. If you made it this far, I bet you loved the episode. So you should join our YouTube channel membership for only $2.99 a month. This gets you access to one, the whole on a bridge conversation. Two, you get the episodes on Monday, one day earlier. Three, you get two additional entries to our giveaways. Check out our Instagram to see what we've given away. And four, you get access to seasons one through three. That's over 100 episodes of wisdom and life changing advice. What are you waiting for? Join.


Here it goes. So hello, hello. Let me, first of all, quickly introduce myself. So my name is Sergi, and I'm a patent developer. I like to say that I'm a patent developer from Siberia, though now I live in Berlin in Germany, but originally at least I am from Siberia. And I have something like 20 years depends on what to count and how to count of software engineering, of which I have, I guess now it's 11 years in Python, and I love Python for all this time very much. And currently I work in in Zalando, which is a well-known European e-commerce for cloths and for fashion as a software backend engineer in the precedent forecasting where we run machine learning infrastructure on Kubernetes. And this is what I'm going to present you now, is how to use Kubernetes to basically extend your applications and to make it a part of your applications, not only from the operations point of view, but also from the development point of view. But before we go there, I would like to remind you briefly in what Kubernetes is just in general, which would be needed later. So at least it is advertised as a container orchestrator, which is true, of course. And it was until some time, it was only the container orchestrator. So basically you could run a container, you could drop them into pods, or multiple containers into a pod. And on top of that, you could build a lot of abstraction layers like deployments, which just keep some amount of pods running and services for the pod discovery and container discovery, and ingresses to connect the internet to your application and so on and so on. And all of these all together basically represents the operations part of the Kubernetes. So where you run your applications, where you operate your applications. However, to take a deeper look at that, we need to understand what Kubernetes is under the hood. So how does it work? And when you take a look at it as a software engineer, you see two main components. First of all, it's an API, which is a REST for API. What's important sounds standardized REST for API. And second part here is that there's a database. So it's basically a state for REST for application, which does some magic on running the containers and distributing them to the workers. And if needed to easy to instances or bare metal machines and et cetera, et cetera. And also it's a common line tool, which is Kube control and numerous amounts of other applications, which integrate with Kubernetes like UIs, like dashboards, like monitoring systems and et cetera, and et cetera. And what we can do here is to extend Kubernetes with our customer sources. And so not only using the built-in resources, but also extending it, sorry, with customer sources, which do whatever we want them to do. And for that, we only need to create one single YAML file, which looks like this on the right. So on the right is a resource definition or customer source definition of which the most important part are the names, like single, plural, kind name and group version and version name. You can also optionally add, for example, aliases like short names here. You can add schemas, open API schemas for validation of the objects and many other things. But these are the important ones because they're used later to create the custom resources, not the resource definitions, but the resources themselves which you can see on the left. And those resources can contain any information that you like in the specification or spec field. So for example, here you can see that we have some durations, some fields, some items defined in our customer source and just for convenience, we have labels and annotations. But that would make Kubernetes only a stateful database for YAML documents, which just makes no sense. Or worse, it would be a database over HTTP, which totally doesn't make any sense. The magic begins when you add some logic behind those documents, YAML documents or behind those objects, which is called an operator. So what kind of logic that is, it doesn't matter. It does something whenever you create a resource, whenever you delete a resource or when you change any field of that resource. And what's convenient for us, the software developers is that when you apply this YAML with a customer source definition, Kubernetes automatically creates all the endpoints for the APIs. It is automatically supported in the command line tools and all other applications without any additional configuration. So you can just use this command line, Q-Control get, for example, as a customer source and it would just work. You can use the API clients and it would just work. And here, when you want to write an application which implements that logic, you quickly find yourself in a situation where you have to do a lot of infrastructure hassle. So first of all, you have to talk with the API properly. You have to authenticate with that API. You have to throttle your requests in case of errors. Otherwise, you would overload Kubernetes, for example, with some bugs and it would just die, which happened to us once. You have to make some parallel processing of your objects. If you have, for example, thousands or hundreds, you have to perceive the state of those objects. You have to handle exceptions in your own code, for example, or worse in the external environments and retry things. And you have to connect this API notation with JSON to your functions and so on and so on. Also, logging is needed. So a lot of infrastructure hassle, which needs to be done or whenever you see something reusable appears on the scene, what do you do usually? Well, you make a framework, I guess. And welcome, KOPF, which is a framework for these Kubernetes operators. So I will first quickly run through the features which are available in this framework and then how it can be used and which patterns in the software development it opens for us. So what's your best guess? What would be the most simple Kubernetes operator ever? How many lines would it contain? And the answer is three lines. Import the library, declare the occasion when we want to trigger something and accept the information. The fourth line here is basically your code already. So it's something useful in theory, at least. Here, it's not very useful, but it can be your domain logic, you can do whatever you want to. Or you can just pass and do nothing. But how to run this operator? At least when you start, the easiest way would be to run it locally in your local machine or notebook or workstation or whatever you have. Not necessarily deploying it to Kubernetes and making all those deployments files and giving it the permissions and so on. So you can just use your own permissions which you personally have for that specific cluster. And to run an operator, you just do cop run and your Python file. And optionally, you enable the verbose mode. And then you create your objects and see how it behaves. And if we will have time in the end, I will show you a quick live demo. Hopefully I will be fast with the presentation here. And once the operator runs, you will see some log output there, something is happening and the object is processed and the events are stored and so on. So the magic just works with these four lines of the source code and one common line for the object creation. So regarding the features, so let's quickly run for the features available. When some people come from the goal language environment and they ask how to make informers, for example, with the operators, they start with a very low level and the very low level of this operator, of this source processing in the operator is basically receiving the events as they happen in Kubernetes, directly as is. And for that there is a handler or a decorator just cop on event. Which does that? It receives the event and you can do something but if you have failed or if there was an error or you just didn't notice this event because the operator was down for some time, well, there will be no entries. There will be no second chance for that because the event has happened already. You can use this for some features but not for all of them. Most likely you would like to use the change detecting hunders, which basically understand when the object was actually created, updated or deleted or the specific field was updated or changed. And they notice these changes even if the operator was down for some time when this change has happened because they store the last handle configuration directly on the resource or in other databases. And therefore they ensure that your processing will definitely happen. It will not be missed. So a kind of eventual consistency here. So eventual execution of the hunders. And this is another reason why you see two creation hunders here. So for example, we have two creation hunders because every handler, every function is considered as a single unit of work. What's more important, a single atomic unit of work. It is either done or failed and if it's failed, it will be retried multiple times until it succeeds or until it fails permanently and explicitly. Which is very convenient, for example, if you create some sub-resources like persistent volume claims and a deployment and a job you would like this creation to happen only once. So you put every single object into its own handler or sub-handler. And once the creation happens it will not be re-executed again even if other objects are still in process of the creation, maybe multiple times. The framework also takes care of the error handling. So as I mentioned, if you fail to create something it will be retried multiple times until you reach the limits either by time or by the number of queries or for some other limitations. So in this picture it just shows four create hunders, creation hunders, of which only one, the second one will succeed eventually after three attempts. The other three will fail. Well, this is fine for this demo operator but probably in your real operator you wouldn't like to fail. You would like to bring all the handlers for the final success. Another feature, which is also a high level feature are the timers so you can execute a function every few seconds, let's say two in this example or in some cases every few seconds if the object wasn't changed for some other amount of seconds. So for example the second hunder here will be triggered every two seconds after 10 seconds after the last change. This is very convenient if you want to monitor some systems outside of Kubernetes or even inside of Kubernetes which are not part of your operator. So if you for example want to query some deployments and their amount of replica for example or if you have an external or internal application which you want to talk to with its own API and get the CPU load. This is exactly an example when the timers are handy. And yet another thing just to mention it but it's very handy also in some cases it's close to what timers do but it runs permanently. So the point here is the timer is executed from time to time and it is expected to exit after let's say a fraction of a second or a few seconds in the worst case. The demons can run permanently for hours, days, well, months maybe if you are lucky and doing something, some calculations for example or some querying of the data or whatever else. And you don't need to manage the feeds or I think your tasks or whatever for that. You just use the decorator and it runs magically automatically. So this is exactly the point where the point where Koff makes everything in Kubernetes easy.  I mean business domain code without any infrastructure. And as I mentioned, since Koff is intended to be friendly to humans, the breakpoints it's the very important feature of the modern IDs. You would like to put the breakpoints and investigate what's happening in your operator. And since you can run the operator locally on your machine you can do this not only in the terminal you can do this also in the IDE and you can put the breakpoints and whatever something happens you can just put the breakpoint and see the variables available and their values. So these on the right are the keyboard arguments available to every single handler. So it's some information about the object itself but also some helpers from the framework let's say memo to store some temporary in-memory data of any kind or a patch object which allows you to patch the object and so on and so on. So there's a documentation page on every of them so please go read for more details. And there are many more features implemented over the past year since actually year and a half since Koff was released for the first time. So like login, like custom authentication, configuration the framework or the operator can be embedded into other applications. If for example we have a UI application and you want this UI application to monitor what's happening inside of the cluster you can just embed it as an operator component running in its own feed and so on. So these are the features but what can we do with these features of the framework? And there are a few typical patterns how the operators are developed. It doesn't matter in which language actually it can be in Go, it can be in Python, it can be in let's say JavaScript if there was a framework but the patterns are like this. The first and the most obvious pattern is that when you create a parent resource here on the left, the operator automatically creates the children resources like persistent volume claim and a job which maybe optionally creates some sub children subresources and the operator can monitor their status from time to time pulling the status of the posts what was the job actually finished was it successful or failed execution and report something on the original object that initiated this job in the status field. To write such an operator you have to write only these lines of code. So you basically react to the custom resource creation you create a children resource like only one child here it's a job and on the other side you monitor the ports please notice not the jobs but the ports which are indirect children which belong to this application and you make some decisions on what's happening inside of those ports and how to report back to the cluster. So please notice only 40 lines of the source code of which maybe 20 lines is the big, I'm sorry, is a big text with the YAML file here which has just collapsed. Another pattern is that if you can orchestrate everything inside of Kubernetes why can't you orchestrate things outside of Kubernetes? Let's say SageMaker, let's say Spark let's say MySQL Postgres somewhere out there or whatever else. And it's basically very close to that except that you have to query the status of those applications and also report back the status which you can do with timers. So in this example, for example, oh sorry in this example every 10 seconds we check for something running outside or simulate that we do this with random and report the status of the object locally. When we combine these two patterns we get another very common pattern is the application-specific operators. So let's say Postgres operator or in this case Elasticsearch operator done by Zalando which is not code-based, sorry but just to get the idea. You run the same operator to create the children objects children deployment, deployments children pods but in addition to that you talk not to Kubernetes but to the application itself here through the applications API and you check if it's alive or what's the CPU load there internally and if not, if something is going wrong you can just upscale or downscale the application. And for that a code snippet, oh sorry a code snippet how this can look like. In the background it's the same application as in the first pattern when you just created children but in the foreground you can see that we first collect or simulate the CPU load here then we make a decision on what to do with the pods should we upscale or should we downscale based on the CPU load and we change the child here child deployment to upscale or downscale. This is the whole operator need for that so the complexity is very low as I said. And yet another pattern just to quickly mention it so it was the cross cluster communication. In that case we, this is an interesting example actually on the left the user can have access to the cluster A only and they can create the custom resources there but there's no operator for them. The point here is that the operator runs in a totally different cluster in the cluster B which is on the right and they communicate with each other with a little proxy with your authentication system so it can be all two or whatever else you have for authentication. And the execution and the workload of that intention on the left which is expressed by the user via a customer source can be shifted to a different cluster where the operator actually performs all the job. And this is a quite a complex and complicated solution and what do you think how many lines would be needed for that? And the answer is only these many lines so how many is this like below then less than 10. Because you can just inject your custom authentication as long you have a token you can just talk to a separate cluster instead of a local cluster. And this brings us all these patterns all together bring us to a totally different way of looking at Kubernetes and looking at our applications. So we can extend the domain-driven design to Kubernetes and basically bring the state-driven design or sometimes I call it desired-driven design just for fun. When the users express their intentions or the desired state of the system with the YAML documents applied to this Kubernetes cluster and the operator does the magic of reconciling with this reconciliation loop of bringing the actual state to the desired state. And this actual and desired states can be the states not necessarily of Kubernetes itself but of any application. So in this example, a user data scientist asks for a forecast to exist. Initially it doesn't exist but the operator does whatever it needs to and this is totally not of the user's concern what is happening there. So the operator can run a local job, can run a SageMaker job, can run, can do the calculations terrifically inside of the operator but eventually it brings the desired, the actual state to the desired state by uploading a file to an S3 bucket. When the user just notices that and say, who thinks my intention was satisfied and they get this forecast there. These are only a few patterns which I see, which can be used or can be applied in the operators but I hope this is not all and you can bring some new ideas how the operators can be used and which patterns can be implemented. And this is not the end of the presentation. So one or two minutes more. Do we have time? We have time. So just to quickly mention, there are three major tracks in the current roadmap. So one is the technical track where the new features will be implemented. I basically mentioned the same features a year ago and at another conference but this year didn't go well from the beginning and some of the features were not implemented but this is still the plan. And now since the framework is forked recently since this August, I plan to build a community around it or maybe join some other community and community of first contributors and also first of users. So some support for the developers who make code-based operators. And the third track is making all those YAML files easier because the YAML development, YAML driven development is sometimes really annoying. You have more YAML code than of Python code sometimes. So to summarize, the operators can be easy. They can be so easy that you can write just ad hoc operators for here and now without any reuse and it wouldn't be a waste of investment and you can do this in Python and you can orchestrate everything, whatever you need for your business domain without the infrastructure. So please use COP, please spread the word, please share your operators or at least some articles how you make the operators if you can share them directly. Here are the links. I have uploaded the slides already to this link so you can just, I'm not sure if you can Google or click here but feel free to download and to ask any questions in Twitter or in the issues. And before we go for the questions, do we have maybe three, five more minutes for a quick live demo? Yes, so there doesn't seem to be any ask any questions. It was a little bit about some URLs that seems to be resolved. So you do have, let's say about exactly three to four minutes for a live demo. Okay, so this is the operator which I mentioned in the very beginning that the most simple operator ever with one additional line which we can comment out right now. And we want to have a cluster and I highly recommend to use, key 3D for any experimentation. It's a very lightweight Kubernetes cluster which starts in something like 20 seconds, totally clean and from scratch and I will show you how to configure it cluster and how to get to the running operator. This operator on the left, it's basically part of the repository. It's the examples folder and the first one, the minimum example. There are more advanced examples like creating the children resources. Okay, let's take this one instead. This is more fun. Here we have a port description, a YAML file which runs a duty box and sleeps for whatever we have specified in the duration field of the customer source. And it adopts it, so it makes this port a child of the customer source which it handles at the moment which is the code, for example, customer source and it creates this port with the client. So in this case, it's by QBitGee and it remembers some information. So fine, we have a cluster running. We can see the pulse maybe of some other application of the system itself. And what we need to do is first to create a customer source, a definition, which looks like this long YAML file with the names. And then we can run the operator in PyCharm and most likely it will work. I hope so. At least it did so 30 minutes ago. Yes, so it has configured itself. It has authenticated with the cluster and it's ready to run. What we do here now is applying the custom resource itself with a spec and a duration of one minute. So this is how long the port will be sleeping. In some cases, I can type Z instead of Qt Control but it's basically the same. It's just for my convenience, one letter alias. So here we do the Qt Control Applying and this object file and please notice the operator reacts immediately. It notices that it's a creation of the resource. It calls the createfm handler. It does some communication on the low level which belongs to URL leap three in this case. It's not our log line. And that's done, it puts some status on that resource. So we can see the port now in the current namespace which we have created for the suffix but belonging to these customer source. And we can also see the customer source, the status. What's wrong? Yeah, it keeps, for example, nope. So here on the customer source we can see the YAML representation of that object with a lot of fields injected by Kubernetes itself with Qt Control with our own framework. And the most important here is that the status is updated in this last line where we have remembered the UID of the port that we have created. So in the next hundreds, whenever something happens with these pods or with the customer source, we can just remember the things that we have created and we can talk to Kubernetes just by referring by their name instead of querying like what pods belong to our application please tell us. So instead we can know their names. So that's it. The operator is up and running that easy. The whole code base for that can be hit on the screen with proper zoom. Okay, or maybe just the screen collapsed. That's it from my side. Now the questions, if there are any questions.


Yeah, we on boss talk one-on-one. Yeah, we gonna I hope I got me a little model on my head. I was about to say I was just about to ask cuz I know you did a little bit of modeling Yeah, so she got her first fashion show in December. So we don't know. So you are putting her into it I was like that would you buy that? What agency did you get her with? So she's not with agency. She's a free agent right now Most of my work when I first got started. I was a free agent until I wanted to get into more difficult shows You got to have agency. So shout out to carnail because I was signed with some knowledge model management He put me on one of his biggest shows fashion beyond a limit So kind of gave me the experience of like a really really really big show See, that's what I wanted to know because I'm not what's the benefits of having an agent Compared to you know shows New York Fashion Week, Los Angeles Fashion Week because I mean Most of them they don't most of those designers are impressed if you're with an agency if you not they just look at you as you're Unexperienced, you don't know what you're doing nine times out of ten. You know exactly what you're doing You just don't want to be tied down. You don't want to have those stipulations You don't want to get that five or ten fifteen. Yeah, I'm about to say yeah But once you're getting those big shows and you're getting that experience out there and that exposure Yeah, take that ten percent. I don't care. Somebody else be gonna pick me too. So I'm cool with it. I give it to you. You use the watch that on Yeah, our banks tire banks them they didn't want me they said I was you went on there. Yeah, I was under wait I was like a hundred and twenty three pounds. I didn't know I was 16 when I went This is when they first started just really open it up to the teenager. She ditched you She didn't diss me Multiple Multiple auditions that you have to go through before you even get it to me.  They weren't messing with that They didn't want that Right Because you always thought that you know with models they want you as skinny as you can come now They want you thick So I'm just like well, I mean I eat but it don't stick So I don't know and I had a baby and a baby is still in the way too. So see a lot of people wish that could be you I'm just like, oh, well fine. Don't take me It didn't stop you though. No, it didn't stop you so that's great That's good because you started modeling out of how old because it wasn't in 15. Okay, so you started modeling if oh Tell me the story. So that had nothing to do with my dad. My dad didn't even well He spoke it into existence. I'm gonna say it has something to do with him. Oh, so he knew my dad's sister my aunt Rachel She took me to HCC college for a casting call And I modeled for their show every year and then after that she just got to be more and more show Oh, she was determined. You look thin thing you finna walk these runway.  I was the only black girl and I was dead in the middle I had glue in my eyes. So my eye was all pink and she was squirting red.  Their foot could be the ankle could be wrong singing any day Over modeling. What's the most difficult situation you've ever seen happen in modeling? We had to do a bridal showcase at the Jar Jar convention center downtown and it was basically maybe 10 girls 30 looks and they had us coming back to back I couldn't fit the shoes so I'm a size eight and a half nine my foot was in a size seven and a half shoe The dress that I had on was two sizes too small So I'm in this core set could barely breathe My aunt is looking at me like you got it better not pass out when you get to the stairs You need to basically run to get to the next designer and I fell down the stairs Wow, I ain't he was like I got it Patch it up and get going you good. Your next look is some pants and I had graduation Did you get blood on anything? No when I tell you she was a working art with that tape And I almost miss graduation so afterwards we were running and she was like we got graduation So I'm running she was like your hair make-ups already done I'm going to put my little dress on and stuff. We running down the parking lot. Yeah We own boss talk one-on-one one-on-one. Yeah, we gonna


Good morning, John. Last week I was in Amsterdam, and as usual, when I go someplace that is not my home, I am struck by all of the little differences, like all the bikes and the trains and the trams, where in my town almost everybody gets around by car. It's easy to say that this is a question of circumstance, and of course it is. In Amsterdam it's dense, the roads are old and narrow, and the country is flat and isn't covered in snow half the year like it is here in Montana, but it's also a question of choice, individuals making decisions and establishing and following norms. In Amsterdam, even if it's faster to take a bus, even if it's raining and gross, people still bike because that's what you do. And since so many people do, everything is built for bikes and trams and trains, while I imagine trying to find parking would be a miserable, terrible disaster. I don't actually know though how these norms get established. I imagine that they are things that just fit, things that simply make sense to the people who have come together to make a place, norms that make them feel good and valued and healthy and satisfied. The blending of story into place, into groups. That's the thing that I thought a lot about this year at VidCon EU because it's also the story of online communities, which is what VidCon ultimately is about. At VidCon EU this year, we weren't able to have a fan component for a bunch of reasons that I'll put on the screen right now if you're curious, but it was still able to be that kind of cultural exploration. We get a chance to ask where our ideas come from, what stories we are telling to ourselves and to each other and whether they're good stories. Having the community there I think makes that even better, which is why I came away from VidCon EU. So excited for Anaheim and Australia later this year. I'm working on what I think are some pretty good speeches for those VidCons about defining success and some of the strategies that I find really work when trying to figure out what kind of content is going to get attention and be successful, but also not be bad for the people watching it. I'm excited about my panels and also to do an old school acoustic set to close out the whole event in Anaheim. I guess being a founder has its advantages.  A couple of weeks ago on our new podcast, Delete This, Catherine and I were talking about how the messiness of stories can make it hard to love something a hundred percent, but maybe loving something a hundred percent isn't right. Maybe it starts with joy and ends with joy, but joy that also has care and concern and thought mixed in. And if we're not doing it that way, I don't even know if that's right, which is why I love VidCon and also why I love my new podcast, where Catherine reviews my Twitter feed. And if you want to find out more about those things, there's links and maybe even some coupon codes in the description. Any opportunity to examine the stories I tell myself is something I want more of in my life. Taking an hour every week to go through my Twitter feed with someone who cares about me a lot is a great way to do that, and so is traveling to a new place and making a bunch of cool time-lapse videos. And so is getting together to celebrate and contemplate with a bunch of people who care about and love and are excited about and also worried about a lot of the same things as me. John, I'll see you on Tuesday.


I... am so thankful that I checked out this outro before the episode. I wasn't gonna do it, but I was like, you know what? These endings don't really spoil anything unless you know what's gonna happen. Because if I reacted to this song and these visuals after that episode, I wouldn't be able to pay attention. I wouldn't be able to. Oh, yes! Oh my god, that guitar sounds insane! Drumline, the second this just started, man, I'm already red! Oh, I love that! Gym Song! Gym Song for tomorrow! I'm lifting... like this! Yeah! Man, this is going so hard already, I wanna... My fellow rockers, bro, my metalheads, bro. Yeah, recommend this to the metal reaction channels. They gotta hear this already. Already, I'm going insane. Oh, that guitar is squirting on me. I wouldn't be surprised if that's TK singing right now.   Jimeno? Usually I'd bust a nut all over you right now, but TK is already getting all my juice. TK is distracting me, that's how good he is. You know TK is that good.  They'd be playing, but then Jimeno's titties would pop up, or Machima's ass, and I'd forget about it. That's sound he makes right here. Yes, yes, yes. This is what I want, man. This is why I was so hyped for this shit, man. Wow, I'm going to watch the video after this, because I'm way too distracted by the vocals. Way too distracted, bro. Best one, best one, it's the best one. I don't care what anybody says.   It says TK from, I don't know what that means. TK from whatever, but it's called First Death. Oh my god. Holy mother of pearl, Neptune, and Buddha. Wow, let's look at the vocals now, okay? Do I have to wash this on mute? No, no, I can't, I can't. But I'm going to pay attention, I'm going to pay attention. I promise. I love this. The visuals are always good. I don't know what it is about this one, but it's like the animation for this ending was just something of a different nature.  Like, is there any other place you'd rather be than in this location right now? Ugh, the lighter, the flicker, the lighting in the scene with the shadows?  When y'all told me chainsaw, man, this is the music that I imagined in this anime. This is what I imagined.  Like, without a head start, full force of God jumped through the wall and I literally make it through. That's the kind of music I wanted.  That's what I want. Look at this. Look, what a beautiful shot with the hair moving and the lighting. I don't even remember seeing this. That's what TK does to me. Meowie. Yup. This, I can't believe this exists. This part, honestly. Tell me not this is not the most beautiful thing you've seen. Choke your loved ones, okay? Choke them. See what I mean? I didn't even see that when I heard this song for the first time. That's the TK effect. They did this. This is absolutely amazing. Oh my God, could I pay attention to the visuals? TK, please. Why am I looking up as if you died? I'm the one that died. Oh my God. This was amazing. I gotta watch the episode again. Oh my God.  I wanna hear this part again.  What did I tell you in the intro that this was gonna be the best ending? Nick, you can't say that. You didn't hear the song yet. What about the other seven endings?  I'm joking. I actually love most of them. Most of them, not all of them. This one, not only with the visuals amazing, still, I think visually my favorite was the one with maximum the hormone, horniness. Them, that was definitely my favorite when it comes to visuals. But song-wise, put my bias aside, this one was everything for me, man. Honestly, I feel like it's gonna be a tie with Vondie's song, Chainsaw of Blood. But I feel like this is more my style right now. This is more what I want. This is more what I'm listening to. Like, I'm loving my punk music right now. I'm loving the Pierce DeVale. That's all I'm listening to now. I'm revisiting my childhood, Pierce DeVale, and Sleeping with Sirens.  This is that song, bro. This is what I'm gonna listen to.


I want to play a clip featuring Dave Rubin because I think it is perfect at demonstrating precisely why conservatives and Republicans always hyper focus on like the surface level culture war nonsense issues and it's because their policies are incredibly unpopular. Like imagine if they try to sell you their agenda based on the economics of it. They said, hey, how would you like it if we gave tax breaks to the rich and never raised the minimum wage and busted up unions like the American people wouldn't like that. And even when they try to make like an economic appeal to Americans, working Americans, it doesn't land. It's disingenuous. So what they usually do is try to cultivate goodwill by focusing on the issues that are more relatable. So, you know, if you like Dr. Seuss, then they're going to spend an entire week screaming about how Dr. Seuss was canceled. What an actuality the company itself decided to pull six six books. So Dave Rubin is going to attempt to make an actual economic appeal to Americans to get them to be conservative. So he's going to give us some insight. This is the argument that he uses that he thinks might actually persuade people, particularly college students who are more liberal, more leftist oriented. So we're going to watch this. This might work on you, according to him. And then when we come back, we'll determine whether or not this argument is persuasive. But there are a couple of techniques you can use. I would say it's very hard to get them to join you or to listen to you if you're just drubbing them with facts. It's very hard to do. What you can do is you can turn some of this on them. So one thing that I found is at least somewhat effective when I go to colleges before I do anything, I'll say, you know, does anyone in this room have it worse than their grandparents? Good question. And if you live in the West, especially if you live in the United States, but I suspect it's very, very similar here. And in most Western countries, you have it way better than your grandparents. In many cases, your grandparents were immigrants who came with nothing. That's obviously a very consistent thing that's happened in the United States or certain, maybe your great grandparents or whatever.  It's very rare that if you live in the United States, that your grandparents who were alive in, say, the 30s and 40s and 50s had it better than you. And if they did, they were probably oil tycoons or something. And then if they have it better than you, that means that the family lost the money over generations, which the left would love because they don't want to keep accumulated wealth. I love how at the end there, he just pretended as if dynastic wealth isn't a thing when it's quite literally linked to record high income and wealth inequality.  So you've seen the clip. This is the argument that he uses that he thinks might work. Are you persuaded? Are you a conservative now? Did that one question that he thinks is very persuasive actually change your mind? Of course, it didn't because that actually is going to hurt his case.  The answer is an unequivocal no. See, when your grandparents were in college, they weren't burdened with student debt for the rest of their lives. And if they took out student loans, they could pay it off easily over a summer working at McDonald's. And on top of that, they can buy a house, buy a car, support an entire family all on one income. Whereas nowadays, that's not possible. You need two incomes to really get by and actually earn a living. And there are all these other costs associated with two parents working. I mean, daycare.  He's thinking, look, things are better now. I'm doing better economically than the last generation, than the rest of my family. So it must be the case that everybody else is doing better as well, except that shows that you're out of touch, Dave. Not everyone is doing better.  Congratulations.  And you were able to find that to be lucrative. But that's not going to be something that most people, most young people are going to be able to do as a career path. He says here, it's very hard to get them to join you or listen to you if you're just scrubbing them with facts. Yeah, I wonder why you'd say that. It's almost as if you don't know any facts and that the facts of the matter, the objective empirical facts aren't very helpful to conservatives. Now, there is some truth to what he's saying. If we are more charitable in that people oftentimes will respond more with like an emotional argument, if you make an appeal to emotions. But what's the emotional argument that conservatives make? Well, they'll say, look, I mean, the left wants to cancel you. They want to get rid of Dr. Seuss and Mr. Potato Head. Whereas the actual emotional argument that the left makes is that, hey, people are dying every single year because they don't have health care. They can't afford their insulin. They can't afford to see a doctor. This is absolutely egregious. It can happen to anyone. Maybe we should have Medicare for all. So even our emotional appeals are actually founded in reality. Whereas when the right makes emotional appeals, it's hysterical, it's nonsense, completely bombastic and idiotic. He also argues that your grandparents had it worse because they had to live through war and famine, as if that's not something that this current generation is living through. Zoomers who were born at the start of the Iraq war are now quite literally old enough to fight in it themselves. And sure, like worldwide, there's been improvements in the standard of living. But you also have to understand that your grandparents have a privilege that none of us will have. Millennials and Zoomers will not have the privilege of growing old and not being too affected by climate change. I mean, we're already seeing the effects of climate change in certain communities around the world. They're already seeing it.  But when we're old, when we're living out our golden years, we may very literally see wars over water because of climate change. That's also a luxury that our grandparents had have now that we won't have. So for him to say this, like there's so many reasons why our grandparents had it better than us. And the main one, if you're trying to appeal to economic arguments, is the New Deal, something that Dave Rubin is against. Neoliberals in both parties, the Democratic Party and the Republican Party destroyed the New Deal reforms. Unions, their prominence has gone down significantly. And as a result, the working class is struggling. The middle class is disappearing altogether. So if your entire pitch to young people is, hey, think about like whether or not you're doing better than your grandparents. You're not going to persuade anyone. Sure, there are generational differences when it comes to technology. We have computers now. We have smartphones and that is an improvement.  So this is why Republicans have to remain hyper focused on these weird wedge issues and cultural issues. Because without that, they couldn't persuade regular people because nobody wants to see more tax cuts for the rich. When you look at public opinion polls, Americans, by and large, agree with the left on policies. They want to see an increase to the minimum wage. They want to see legalized nationwide. They want to see a single pair of Medicare for all health care system. But when it comes to like the right, your ideas are unpopular. You've got nothing. So you have to either focus on culture war issues or lie about your economic agenda and pretend as if you're for the working class. While every single Republican votes against the $15 an hour minimum wage. And what was it? Like only five Republicans in the house joined with the Democratic Party to pass the pro act, which would help people form unions. It's just it's laughable. But I'm glad that Dave Rubin is sharing his insight into how the right recruits because I don't think we have much to be concerned with when it comes to their economic arguments, because this is not very persuasive to say the very least. I did, I did, I did, I did, I did recovery mode. My brain, I did recovery mode. My brain, I did.


Hello, Psych2Goers. We just want to take the time to thank you for all your kind support. We are a team of dedicated, passionate, and hard-working individuals who come together every day with one goal in mind. We want to make psychology come alive for you. We are self-funded and recently launched our Patreon. If you enjoy the work we do and find it meaningful, please stick around until the end of the video for more information on how to get more involved with us and all the cool rewards you can get from us. We hope you enjoy this video. Sweaty palms, nail biting, and pacing back and forth in your room are all habits you're probably already familiar with when you have anxiety. But our bodies also have a surprising way of doing strange things when we worry. Sometimes, the unconventional route is also an uncomfortable one. There are six weird things anxiety causes you to do. Number one, you have ice cold hands and feet. Anne Marie Albano, an associate professor of medical psychology at Columbia University Medical Center, states, when you're anxious, your blood flow is redirected away from your extremities and towards your larger organs in your torso. This is why it makes it hard for your blood to circulate well that keeps your hands and feet warm. When you feel as though you might be in danger, your body enters the fight or flight mode to prepare yourself to survive. Unfortunately, anxiety isn't rational and causes you to feel this often. Number two, you experience gas problems and frequent urination. Sounds embarrassing, right? But this is unfortunately true. Being anxious causes you to have an overactive gut. Albano states, gas is created when the acid in your stomach is churning while nervousness runs throughout your body. When you're anxious, you may also be prone to eating and drinking too quickly. Frequent urination is commonly experienced too. When you're anxious, your muscles tense up and your body puts pressure on areas such as your bladder and abdomen that makes you want to urinate more. Although these experiences sound uncomfortable, they're nothing to be ashamed of. If you're concerned, you can talk to your doctor about solutions to these symptoms. We hope that by talking about anxiety, people can be more accepting of it. Please be sure to also check out our video, 13 Things People Don't Realize You Do Because of Your Anxiety to Stay Educated on the Matter. Number three, you catch yourself yawning a lot. Albano states, some individuals, especially with generalized anxiety or panic, tend to breathe more rapidly than the average person. As a result, rapid breathing tricks the brain into thinking you need more oxygen, which causes you to take deep inhales. So the next time someone thinks you're yawning because you're bored or tired, inform them that it could be anxiety. Number four, you get rashes on your skin. Anxiety can give you an uncomfortable itch, metaphorically and physically. Albano states that being anxious can frequently cause you to experience skin allergies and problems, such as eczema. That's because when people find themselves highly stressed, extra cortisol, which is the stress hormone, rushes through the bloodstream. As a result, the skin starts to feel irritated and rashes begin to develop. If you experienced this issue often, we advise you to talk to your doctor about ways to alleviate it. Number five, you often space out and have trouble concentrating. Entering a dreamlike state sounds relaxing and even ideal for escaping your troubles. But having severe anxiety can cause you to have out-of-body experiences. When things start to feel too overwhelming, you may find that everything around you feels unreal, including the body that you're in. This is because of the fight-or-flight mode you enter, which prepares you to deal with the current issue by eliminating stimuli nearby that's too much for you to handle. Number six, you hear phantom rings. When you have anxiety, you may constantly be sitting on edge and anticipating something. One of those events may be a phone call or text message from somebody you've been waiting to hear back from. As a result, you may hear your phone ring or buzz, only to check it and find that the sound was all in your head. Others call this phenomenon ringxiety or phantom ringing. For instance, people in a relationship with high anxiety may also develop a strong attachment to their partner. So, if they're worried their partner isn't as committed, they may expect the worst and think that they're talking to someone else. To reduce phantom ringing, it's important to talk about the anxieties you have with your partner. It may also be wise to disconnect for a while and embrace nature instead. Does anxiety cause you to do these strange things? Please share your thoughts with us below. Also, don't forget to subscribe for more content from Psych2Go and check out our Patreon. We started it because we want to grow into a bigger platform that reaches more people who are in need of help. With your contribution, you can receive our PSI pendant, t-shirt, issues of our magazine and many more membership benefits. Our funding will help us produce quality script writing, voiceovers and animation that makes our content both entertaining and educational. We want to make sure our community members get the best and only the best. Thanks for watching. Original article, HTTPS, Psych2Go.net forward slash six weird things anxiety causes you to do. Hey everybody, I just want to give a personal thank you video for you guys for always supporting Psych2Go and making this all possible for us. Our vision is to make psychology as accessible as possible so that it promotes self-awareness and helps you guys grow. However, we want to make more content for you guys and would love your support in buying one of these bracelets from our partner, Introvert Palace. Check out the bracelet. It's pretty cool and it even includes Pluto. The link to purchase will all be in the description below and I hope you guys have an amazing day. Bye.