to Kevin from DDEV now who's going to talk about combining DevOps and emotional intelligence. Yeah and this will be really interesting because I do not have my speaker notes or a timer so I'm just going to kind of wing it as I go but hi we're making the best out of what we have available to us. My name is Kevin Bridges. I'm the CTO and founder of a company called DDEV. We make local development tools and complete lifecycle kind of hosting platform as well. And through the course of putting together this company, I started in Drupal probably 15 years ago. I started around 4.5, 4.6 and was fortunate enough to be involved in a lot of really large early websites. So in Drupal 7 we made Popsci.com which I think was one of the first enterprise level websites eventually moved on to a site called examiner.com where we introduced Mongo into the Drupal core code base and basically most of one of the largest sites in existence at the time it was the top 50 US web property. Through the course of that I basically came to realize that there's this concept of a pendulum that's always swinging and I like to reference this a lot but for me that pendulum was initially you know when the internet was created it was more long lines of well let's just start doing things on the internet. Let's get our message out there. Let's go to Matt's script archive if any of you actually remember what that might be. Download a Perl script and put a bulletin board or a login form on our page. Eventually we got smarter and smarter and figured out that there's different patterns, different ways of doing things and that they're really successful. The ones that were really accelerating in this new world were the ones that were capable of identifying those patterns and gravitating the people that were doing the same type of work. That's what we started looking at CMSs. That's where Drupal came from. At the time it was in Juma and Magento and a couple others that I was evaluating. It ended up in Drupal and like most of you it changed for life but that was 15 years ago and we spent a lot of time working on those components that make up the website. You know the login forms, the bulletin boards, the shopping cards. I got that really well and then finally realized that we can do big sites. Once we started getting into the enterprise the whole new world of conversation started happening and that world revolved around infrastructure and revolved around handing off the work that we were doing to people that were capable of eating it alive, eating it money, having to deal with corporate networks, having to deal with the whole new world of things that most developers are very uncomfortable dealing with. Eventually people got smart and called it DevOps so that pendulum was swinging back in my opinion to being able to manage the other side of the equation. So we've got the front end, that's covered by Drupal, now we go back to the back end, that's what DevOps is and we need to understand how to do that pretty well. One of the things that engineers tend to do is they tend to neglect the human side of that conversation quite a bit. So a lot of times when you hear the word DevOps that comes across as being a very technical skill set, something that you need to be super smart about, something that you need to be super skilled with computers on the server side, things that a lot of people don't really do natively. But what is really important and what is the point of this talk is that humans matter more than the technology and if you can engage properly with both the technology and the humans involved in building that technology you're going to do amazing and wonderful things. So let's dive in. I can figure out how to use a computer. So why are we here? The company that I created has a vision statement of advancing developer communities and for us it's real simple and not so simple at the same time. It's advancing developer communities so we are a thriving part of the developer community working to advance developers and their communities beyond where they are today. Together we can paint a picture of what tomorrow can and should be and for us this is really important and I'll get to some of this in a little bit. We want to create a world where developers are helping each other grow stronger, build faster and achieve solutions in a collaborative way. That's what DDEV is all about. So for us you know when we go and like look at the different communities that we're involved with we're not just involved with Drupal, we're involved with WordPress, we're involved with typo3, we're involved with SU, we're involved with Expression Engine. There's many different CMSs out there. There's many different communities out there and each of these communities from organizing events to you know getting their associations funded to being able to provide the services that they do. There's very common patterns in there. Some of those common patterns are technical like local development environments. If you're working with PHP then you need a quick and easy way to get started. If you're working with the community then you need by a governance model a set of guidelines to be able to make that community effective. And we specialize in taking those patterns just like we did early on in the internet just like we did when we started using Drupal just like we did when we started exploring DevOps and we share those patterns with the different communities to make them more effective. So again focusing on the human part of it and not just the technical part of it I think is really important because if you can do that you have the ability to realize the collective of what open source gives us which is you know a good group capability of solving problems to make us smarter and you can share that with other people. There we go. So basically what we're going to learn in this talk very quickly what DevOps actually is. We're going to talk a little bit about navigating complexity from a human perspective. We're going to talk about what emotional intelligence is and how it works inside of the DevOps paradigm. And then we're going to talk a little bit about what to do when things get difficult and show you a very quick example of increasing velocity with structure and empathy and what that actually means. So a lot of times when people get started you know they see I like to reference mountains a lot. I'm from Colorado so that's kind of where this is coming from. But typically when I have people come out and visit me in Colorado they see something like this and this is for us in Colorado a pretty standard height but a lot of times people see something like this. They think that they're going to be able to just run up the mountain that they're going to be able to just put in their best effort and put one step in front of the other and kind of get to the peak. And what they don't understand is that a lot of times it's a longer journey than it looks like. It takes a lot more work to get where you need to go. And many times people fixate on the size of the task in front of them or the problem in front of them to the point where you know a really good engineer might start coming up with all these elaborate solutions to solve this very difficult problem. And they might stress about it to such a degree that they start to kind of withdraw to get imposter syndrome to not really feel affected with what they're doing. And they tend to forget this simple fact that people need to know that their life is more important than the project that they're working on. And that's a quote that comes from a gentleman by the name of Randy Fay. And if any of you use D-Dev or any of the products you might know who Randy Fay is he's an incredibly passionate supporter of the project of the community. He's been involved in Drupal for a long time. Very active in the governance conversations that happened very early on in Drupal. Some things that some people might not remember. But if you get a chance you can kind of hear the podcast. This was a Drupal Easy podcast where you talk about this. It's bit.ly.com. It's a really interesting quote because I think that a lot of businesses tend to forget they focus so much on delivering value or delivering products on delivering services that they forget that they're climbing a mountain. It's not it's not a small task that's being undertaken and it's not something that's just going to end at a certain point and then give you a new starting point. So let's get a little bit into kind of what DevOps is because it's going to be important in this conversation. DevOps is discovering what needs to be done defining a clear measured path to doing it and executing that path using tools that suit your needs. Decreasing complexity and increasing clarity to add maximum impact and automating where possible. So basically what this means is that DevOps starts off as a checklist. Real simple. You can do it on a piece of paper. You can do it on a stick. It starts off as a methodical way. I have to achieve that goal of reaching the top of the mountain but in order to do that I have to take a left at this turn. I have to take right at that turn. I have to make sure that I pack my water. I have to make sure that I have the supplies necessary that I know I'm going. Knowing where you're going is going to be a critical part of this because if you can isolate things, if you can make a checklist then you have the ability to not only know where you're going but you can automate it at a certain point depending on what it is and how much human touch it has. DevOps is not that one weird tip or magical pill that will solve all your problems. Installing a butt load of tools, boat load, I think is how I was supposed to say that. We're trying to make someone else's methods or strategies work for you. So essentially, you know, you can't go out and sail all of a sudden on the DevOps expert. I'm just going to solve all of my problems because I'm going to make everything work. It doesn't work that way. It's hard. It takes a lot of work. It takes a lot of energy and it takes a lot of effort. And the more people that need to evolve, the more difficult it gets because, you know, computers are very easy to binary. If a computer breaks, it's either because of the hardware field or I told it to do something to break it. If a person is involved in that conversation, it gets a lot more difficult, a lot more complex. You know, people are not computers. They're very, very involved. So DevOps is not easy. Again, I'm missing my speaker notes, so I'm kind of just winging this so bear with me. But it's completely and totally worth it. You know, if you take the time to understand where you're going, if you take the time to map out how to get there and you take the time to work with the people that you have on your teams efficiently and understand them, they're going to reflect that back to you and they're going to be able to give you their best. You know, a lot of times when you have a lot of really smart people in the room, they start working on a problem. And I think we've kind of seen this in some of the light shedding that you might see on Google about work. People tend to get really passionate, really involved and really want to do their best. And as a result, a lot of times there's conflict, which is kind of an interesting and ironic paradigm if you think about it. Because you have a group of people that are trying to solve a problem together, but they suddenly can't communicate. They're bickering. They're arguing. They're not understanding what they need to do. And they all just want to do a really good job. And being on an engineering team where that kind of tension exists is unhealthy. It's not a good place to be because it's not comfortable. People getting anxiety from that type of interaction. They're more focused on the challenges that they're going to have with each other than solving the problem. Eventually they'll get there if the communication is good enough. But if you are proactive and you take the steps to engage with people, help them understand where they're going and empathize with them, then you're going to be able to help direct people in a direction that's going to make them more productive than they were originally. So in order to do that, you basically need a map. You need to define the culture of what you're working on, what the rules of engagement are essentially, and you need to take small steps. So without a map, you really don't know where you're going. And that's the number one rule of being able to communicate is know where you're going. So the example that I tend to get there, which some of you may have heard yesterday, is if you take a dishwasher from a naval ship and you contrast that with a dishwasher that's working after school in the restaurant, you're going to go and ask those people what they do for a living. You're going to get drastically different answers. So if you ask the person that's working in a restaurant after school, why do you wash dishes? I get a paycheck, I go home, I don't even know why you're talking to me like that. Pretty common answer. But if you take the time to ask that naval officer what their job is, same dishwasher, they're going to say, well, I get up at four o'clock in the morning, I clean my kitchen, I wash all the dishes, I make sure that the pots and pans are ready to go. Everything's stacked up for the chefs to come in, so that they can cook the meals that my troops need to go out and win the war. They know what their mission is, they see where the ship's going, they know where their team is going, and they know exactly what their position in that organization is and how it affects people that they come into contact with. There's a subtle difference there, but it's a very important one, because if you're trying to create a technology project and you're incapable of properly articulating where it is that you're going, then people are going to go to their streams. They're either going to become super active, they're going to start thrashing and just creating work because they think they're helping and solving problems. So, well, I can have this filter here, and the user's going to have this particular issue. I made a better code than in here. Oh, I just thought of this really neat thing, and let me refactor some of this code. That's the kind of conversation that happens, and that's not tenable to be able to move something like an able ship forward in a straight line. So, it's important to have a map, it's important to define the culture. So, by that, I mean that you need to give people the opportunity and safety to be able to fail, to make mistakes, to admit that even though you defined a map, you may have been long in specific steps that are necessary to achieve where you're going, and you need to be going to work with the team to kind of modify it in real time. So, that's why culture is very important. Small steps is also super critical. It's kind of the concept of bad job. You need to be able to adjust quickly, and you need to be able to communicate those changes not only downstream but upstream. So, for me, I have to report to the board of directors. In order to report to that board of directors, there are certain things that they need to understand about the company. They need to understand what value their investment is giving them. They need to understand the products that are being built, the services that we're delivering, and the effect of those on the company. So, finding a way to translate both downstream and upstream becomes pretty critical, and I think that we've been able to do some pretty simple processes. So, essentially, everyone's lost without the map. We use a system that's called OKRs, objective key results. There's a book out there that is called Measure What Matters. It's MeasureWhatMatters.com. It's very good. It's a system of management that's used way to gain out of Intel way back in the day, but it's now used in Google and a lot of large organizations. And the premise of it is that you have objectives and key results. Your objectives are going to be three to five items that are identified at different levels on the side of the company. So, at the executive level, we may lay out three to five objectives of the company instead. Realize a recorder. We want to sign up 50% more customers. We want to increase revenue by 25%. We need very binary types of things where you can say for sure we either succeeded or we failed at this particular item. And it's important to keep them limited to three or five items because what's going to happen is you move throughout the organization. People are going to expand on that. So, you go to, for example, in a larger organization, you're engineering leaders and ask your engineering leaders to also come up with three to five objectives that they want to meet from their specific department. Then you sit down in a room and you evaluate all of the objectives from all of the company. You determine what's going to be reasonable during the quarter or whatever time period that you're working on. And then from there, you start to lay out a map that you can communicate to the rest of the company that helps everybody understand where you're going, where you're trying to get from that quarter. And out of that, they look through and they start to fill in those key results to support those objectives. So, again, you're only looking for three to five key results that support a specific objective. Each of those key results need to be binary. Then we succeed or not.  So, for example, if I set an objective to achieve over a course of the quarter and we completely missed the boat, that boat just went off in a different direction and we needed to adjust, that's fine. It's okay to not hit your goals, but it's important not to change them in a course because you need to be able to learn from that experience and you need to be able to communicate that change in direction to the rest of the organization and help people understand it. So, again, creating an environment where it's safe to fail not only at the individual level but at the organizational level is a critical component of being emotionally supportive of the people that you're working with. So, what is emotional intelligence? It's the ability to understand the way people feel and react and to use this skill to make good judgments and to avoid or solve problems. As a manager, the number one thing that you can do is have realistic and healthy one-on-ones with the people that you're working with. You have an, as an engineer or as a developer, it's also imperative that you reach out to people that you're working with that understand how they work to talk to them on a non-critical basis. You know, hi, my name's Kevin. How was your day? That's a very, very good way to engage with each other on the team and when you find yourself in a situation where there's somebody on the team that you may have conflict with or that may not work the way that you want them to, having that conversation on a regular basis and committing to it as if it's the most important thing in the world will go a significant way towards changing that attitude towards changing those interactions with that people and it's a super important thing to do. I personally don't like talking to people. I'm a very almost anti-social kind of person. So, me engaging with people on that level was very uncomfortable and it has been the single most rewarding thing that I've done as we've grown in size as a mother. So, definitely encourage you to talk because as weird as that sounds, just talking to people goes a long way. So, the next thing that you're going to want to pay attention to is handling conflict and pressure by understanding context while providing space. I think that's what that says. So, what that basically means is that you have to put yourself in that person's shoes to be able to communicate with them, to be able to understand what they're going through, to be able to make relevant recommendations to them, to help them understand where you're coming from and be able to move forward. So, a lot of times if there's conflict you have a couple of different options and this is what most of us do right out of the gates. It's too much. I can't deal with all the stress so I'm not going to listen to any of you. I'm going to go ahead and continue to do what I'm doing because we're all crazy or however you want to say that. If you can't put yourself in that person's shoes and accept their reality and then work from there as a neutral space then you're probably going to belong.  You need to go in a very neutral place, put yourself in that person's shoes and then start to understand them. And then once you do that, you have the ability to help them understand where you're trying to go and you can eventually get to a common place that everybody agrees on and it's drastically different. You no longer look like that. You've got a smiling happy person that's like, okay, well, you know, this didn't happen the way that I wanted it to or expected it to but I'm happy with the outcome and that's an important part of communication. We like to use a system and it's pretty simple to kind of keep in mind. I think we actually got this from Jam and Tracy over at Oakland Strategy Partners, but it's the concept of rain, right? And rain's real simple. If you're feeling overwhelmed, if you're feeling kind of down in the dirt or whatever, you need to recognize what's going on first and foremost. And what's going on is seldom what it appears to be. So, I may be focused on the fact that a delivery is not being met or deliverable is not being met, but in fact what I need to be focusing on is the person is having a personal drama. They might be going through some type of stress at home or there might be a virus that's affecting their day. You know, you need to recognize what's going on. You need to allow the experience to be there just as it is. So, what that means is in the world of improv, they kind of do an and then kind of scenario. So, essentially an improv, what you need to do when you go up on the stage and you talk to the person next to you is you immediately have to accept their reality for what it is.  You have to take that reality, you have to put yourself in it completely and then you can improv and you can become a part of what's happening. It's the same thing when you're dealing with people in a work environment. You need to first put yourself in their position to be able to communicate effectively. You need to investigate kindness. You know, I can't go into one of these one-on-one meetings or one of these conversations and expect a good result if I'm not kind in the process. I might be able to dictate that just, well you work here so you're going to do this because we pay you money. That's not going to go very far. That's not going to build any kind of rapport with the people that you're working with and you're basically not going to be considered a very nice person if you do it. However, if I go in there and I say, okay, well, I understand that your child is having problems or I understand they pass growing up on your bed or something like that, you might be able to make more of a connection. You investigate what's going on and you start to ask leading questions and you come across with kindness and it has a dramatically different impact. You want to focus on national awareness which comes from not identifying with the experience. So what that means is that if you find yourself in a difficult conversation, somebody might be going through a lot of personal strife, you don't have to own that strife to be able to communicate effectively with that person. You just have to empathize with them. You have to understand where they're coming from and then you give neutral and good advice in return.  You'll succeed in business. You'll succeed with your clients and the world starts to be a different place. It's pretty interesting. It sounds kind of overly simplified, but it's amazing the effects that this type of communication have in an organization. So basically the other tenant of this is that your team of humans is more important than the velocity that you have. And I think I'm able to go back. There we go. So the mountain biker thing is interesting. Again, from Colorado, I do a lot of mountain biking. I do specifically downhill mountain bike riding which involves a lot of speed, a lot of jumping, a lot of danger. One of the most valuable things that you can learn in mountain biking also translates to other aspects of life. And that includes running the business and being able to get looked at. So that concept is that it's slow basically. You have the ability to approach downhill mountain bike race in two different ways. You need to go very fast and use speedo for compensating things. And when you do that, you basically lock up.  I end up not floating in the moment. However, if I completely relax and I understand the mechanics of what's going on, I learn this system that I'm engaging in and I relax a little bit. I get that flow state where suddenly I'm completely relaxed when I'm going over the jump. I'm using a significant smaller amount of energy than I was previously and it's much safer as a result of it. So I get that flow state. I'm able to achieve more by going slower. That's a very important concept in DevOps and when dealing with large teams of people or dealing with small teams of people, is sometimes you have to slow down to go faster. So what that means is, well, we've got 25 different things that we want to do for this OKR system, this particular quarter. Well, that's not going to work. We don't have the velocity to be able to do that. You need to be able to measure things like velocity to be able to answer these questions, but you need to make a conscious decision. There's only so much that's going to fit into that pipeline that allow you to flow properly. And if you put too much into that pipeline, it's going to clog it up. It's going to cause stress. Nobody's doing anything when they want to do the result of it and it's going to feel almost kind of productive because you have to slow down to keep that pipeline optimized. So measuring velocity, understanding the ability of the team to be able to function on that velocity is critical. We use something called Zen Hub, which is an add-on for GitHub. And basically what that does is it puts us into a scenario where we can work with product. We can kind of outline what the map is going to be.  They say, well, out of those objectives, we have these five features that we want to get in to support this specific objective. In these features, we have 10 use cases. These use cases are defined using a Gherkin testable format. So then I can plug that into an automated system, have those tests reflect what is being built in the products, and then create a reporting system that also goes back up to the executive level, to the board level. This is something, well, this quarter we're working on this feature. It has this number of use cases. I can derive that 0% is passing it to beginning of the quarter. I can create an automated dashboard which facilitates the communication from the engineering team all the way back up to the executives using very simple steps. Again, back to that checklist concept. You want to be very consistent in your vocabulary, very consistent in your messaging, and separate it so that it doesn't overwhelm everybody. When we first started making it, everybody was involved in every meeting. Everybody had an opinion and everybody knew what was best for everybody else. And nobody was wrong. So getting together, talking about it, finding a way to break that apart a little bit. Now we have a system where we have the product owners and the technical people. They have a conversation first that starts to align what they're working on, starts to align those use cases, and sets the rest of the team up for success. So once that first conversation happens, it's smaller. It's more manageable. As a result, we get a lot of the decision points out of the way. Then we expose it to the larger teams. It's, okay, here's the objectives. Here's kind of what we're looking for for the user stories. Here's the features that we need to support. What do you think about this? If necessary, we make something called an architectural decision record. And this is a media file essentially that gets stored in a repository of whatever code base we're working on so that when we do have a product to technology and conversation, and there are decision points that come out of that, we're going to use this technology, we're going to use this tool, we're going to take this approach. Those are recorded inside of the repository where each of the engineers are working on so that every single engineer has the ability to learn and understand why they're doing what they're doing. Again, over-communicating and connecting the dots so that people know what they're working on, why they're doing that is one of the most valuable things we can do.  I'm just going to rewrite it because I need to do this. And being completely disconnected from what the intent of the work that I'm working on actually is. And that's a dangerous question for anybody to be because it leads to frustration. The other thing to recognize explicitly is that having space for culture and lost velocity is a privilege. The type of system that I'm talking about, building is not something that exists natively in every organization. So, while it is a privilege to have this, it's also a right that you need to fight for. So if you find yourself in an organization or a team where you're not having this type of communication, first you need to take steps to try to fix that problem. If those steps are not receivable, you need to go find someplace else to work because that's not a great place to be. You're never going to be happy. You're never going to have a job satisfaction that you need. You're likely to have a lot of anxiety as a result of it. It's just not a healthy place. So go find this healthy place. It's made a privilege a part of your life because everybody deserves that. So just to summarize, because I still have no idea of my time allocations. Four minutes. Okay, so basically define the map. Take the time to understand the situation and the people involved. Help your team adjust and move towards the goals that you're setting. Be very communicative about the way that you're driving that ship. And build a space for innovation and clear thinking about challenges where it's safe to experiment and okay to fail. If you do these things, it doesn't matter what you're working on. It could be the, you know, you're the new rocket science of the world. You're going to change everything. Or it might be you're making a cake. You engage people properly. You treat them with respect. You communicate with them and you have a structured system to be able to do that. Record the results and communicate back and forth with most of the company. You're going to be successful at it. And that's a very important thing that a lot of people don't realize. So one more summary. DevOps is not magical fairy dust. Creative, create a culture of safety is critical. So creating, sorry, that's a little blocked out. And it's working progress. That's okay. So for us, we know that we make mistakes. We know that we make them continuously. We're not perfect. So we have to adjust continuously. I learn every day that I go to work. And I learn from the people that I work with. I learn from the tasks that we're trying to solve. I learn from the communities that we engage with. And all across the board, the entire thing works because of communication. So we cannot stress that enough. And that's all that I have. So any questions? Thank you. I thought that was great. And what you were saying really trying, I guess, like a lot of people have gone from working on quite a lot of things to multi-tiered or headless sites and are now working a team where we have probably four different disciplines, working set of disciplines. And whenever I come to things like this, I'm reminded of how much I miss the shared purpose of working on a single thing. And I wonder if you have anything to say about how you encourage the kind of behaviors that you were talking about, which seem valuable in teams whose shared purpose has become siloed in the way that often happens? We have a couple of approaches. And just to make sure that I understand the question is essentially along the lines of, you know, you're on a larger team, you're involved in a very specific discipline in that team. And how do you get back out so they become a bigger part of the team? Don't feel like you're on the sidelines. Yeah, exactly. So the way that we handle that is through structured sprint planning and retrospectives, essentially. So we did the ability at the end of the sprint for each person to give a demo of what they've been working on. That demo is facilitated by a project manager that goes through this together, a slide deck, and we record it. So every single scan up that we have, we go through the normal scan up process, we have a breakout. That breakout is recorded and put into Google Drive. So if you miss a meeting, you have the ability to catch up with it later.  So, an example, we might use Pyrex, we might use dinosaurs. The last one I think we're going to use, banks and shiny armor. And we just kind of have three or four little sections on the document where people can write in catastrophes for this past sprint, successes for this past sprint, things that you'd like to call out about other people on the team, items like that. So you have to have more structured follow-up to be able to extract the people that might be feeling isolated. So they have the ability to engage with the rest of the team. In addition to that, we found that just the tools that we made really helped with that. So tools like DDEV, back-end engineer, systems engineer, the ability to very quickly spin up something that a front-end engineer is working on. So we encourage collaboration as much as possible. So you may step in and offer to do a test of something that a front-end person is working on just because you can switch contacts fast enough to be able to do that. You don't need to understand all the technology. You just get one command and you can go and suddenly you can help. So it works both ways. You need to make the initiative to reach out to other people on this team. If you're not talking to someone, schedule a regular one-on-one with them. Say, hey, you know, we've got nothing technical or work-related. I just want to talk for a little bit to make sure that I understand how you work so that I can make sure that my work's doing the best that came for you. What that helps. All right, great. Thank you very much, Kevin. Can you hear me? Yes. So I'd like to apologize to SystemSeed for not putting you in the slides. I did it very late last night and I forgot, so I'm really sorry. We'll put the logo up now. But basically, SystemSeed have been amazing. They've been sponsoring the training and without them, the training would not have happened. So can we have a big round of applause for SystemSeed?


Still 1-0 Stevenson Coleman's got a one-timer sneaks through and Brenton Rylott converts 2-0 Stevenson Oh, Brendan Rylott was denied a goal as he was one-on-one with Bidini late in period number one, but thanks to Coleman's early Confirm that and it looks like Also a look out against Gresham as that's Puck is sent in by Alex Rivet And he's got another goal to his name here in the recent goings 3-0 Stevenson now as they convert on the power play Leaping up for that one was Lee. He's back down to it. Vituci was in it and now Ryan Patrick with the interception He'll break the other way and he scores Ryan Patrick Continues his hot streak and The short-handed goal is scored by the Mustangs. It's 4-0 five seconds left pass headed up and that ends it as Stevenson's win streak extends to nine games At the five to one victory over the Kings Monarchs They stay undefeated all time against them as well moving to eight and oh and And certainly playing their role and trying to improve their seeding


Hello. Welcome to get another session of our NPTEL on nonlinear and adaptive control. I am Shri Khan, supermarker of systems and control IIT. So we are in the final week of our course on nonlinear adaptive control. And I really hope that you have learned sufficient material to be able to design algorithms that can drive autonomous systems such as what you see in the background. Now, as always, we're interested in all sorts of applications. Of course, what you see here are mostly aeromechanical systems in the background, which is due to my own interest in these. But of course, adaptive control designs are not restricted to these. And you can use it on power networks and biological networks and so on and so forth. So I'm always open to hearing more about sort of applications that you folks are envisioning the use of adaptive control. So what we are looking at in this week, in this final week is the connections with learning. And we are now specifically looking at sort of a deep learning problem. But of course, we are, we are sort of different in the typical, different from the typical learning sort of results in the sense that we are not doing the learning offline then implementing it later, but we are doing learning and control simultaneously. We can do this because essentially this is connected through parameter learning, which we already know very well. So that's what we sort of apply. The only difference or which is of course a significant difference is that now we have a very nonlinear regressor parameter form, which is not what we were used to until now. We are always assuming linear parameterization and things like that. But you see here that everything is rather nonlinear. And so we still have to see how we can deal with this kind of nonlinearity. In the previous lecture, of course we started to understand some details about how my robotic arm dynamics looks because this is the application that we are going to be looking at for application for the use of these neural nets. And we saw the basic all electrical dynamics, what each term means, what is the joint on the world space coordinates. And we also constructed this error variable with respect to a desired arm trajectory. And we also, you know, defined this back stepping error type variable, which we have seen before. And we wrote the dynamics in terms of this back stepping error variable. And in this dynamics now we have this function F, which is called a nonlinear robot function. And this is the function, as you can imagine, we will approximate using our G layer neural network. So, but this is where we were I'm going to mark our lecture here. So lecture 12.4. Thank you. So, now, if you look at how we want to design our controller, what we do is put in an approximation or estimation of this, and that's called a factor. So, unlike what you've seen in adaptive control before, we are not approximate, we are not just estimating parameters, but we are now estimating functions. And that's why we have the notion notation F hat. Okay. And then of course, we have a KV times R, which is like a gain matrix, symmetric post-doctoral gain matrix times this back stepping error variable R. And so this is the control. Yeah, so it's called tau zero, because we designed the control sort of assuming that there is no disturbance, right? We cannot do anything to sort of really cancel the disturbance here. So we just design a control assuming there is none. And this is, you know, you sort of try to cancel this guy with its estimate, just sort of getting motivated from the certainty equivalence type idea. And then we leave this term as it is saying, because honestly, this term is going to cancel out on its own. So we don't worry about this term. Great. Now, so as, as we mentioned, F hat is an estimate of F by some means, which is not a dispute. So what happens to the closed loop system? Right. So, there is this notation here. So the closed loop system is not KM, but the VM becomes this guy. Minus KV plus VM times R and plus an F tilde and this tau D. And this is where you have sort of this F tilde, which is the function estimation. So this is just a term Zeta naught, which is combining these two. Nothing special about this. All right. So this is essentially like an error system. So I'm going to highlight this. And so this is sort of the error system. And of course it's driven by the function estimation error. So the F tilde of course shows up here. So, so this is sort of like, I mean, although the tau zero seems to have only one term, which is KV, I mean, KVR. I mean, there's two terms, but one of them is to more or less counter the effect of the nonlinear robot function. And the other term is what is the like the stabilizing term that we usually inject. And this term, although it looks like just one term, it's in fact a proportional derivative term because of the nature of R. So I have a V dot term and an E term. Right. So, so this is important to remember that it has both a proportional and a derivative term. So a PD type controller. Very, again, something that is very standard in aeromechanical applications. Even for space stuff, PD type controllers are known and found to be stabilizing. Yeah. So in the remain, of course, in the remainder of the paper, we mean the authors use this equation 14. Yeah. And we, of course, focus on tuning this neural network in a smart way so that you can get R to go to zero because you want R to go to zero. All right. Great. So why is it? I mean, one, one's very quick aside. Why is it sufficient for R to go to zero? I want to quickly point that out. Whatever R is defined. Okay. So sufficient for R to go to zero. Yeah. Why? Because this means that E dot plus lambda E equal to some phi function. This goes to zero, which means E dot is equal to minus lambda E plus five. Right. And what do I know about fun? Suppose if phi is also bounded, we can prove that phi is bounded, which means R is bounded. If, let's see, I have put it properly. If R is bounded, that is L infinity and R, of course, goes to zero implies phi is bounded and phi goes to zero. Right. Which means that, and what do I know? I know that this is a stable system. Right. Because lambda is positive definite symmetric. So this is a stable system with a bounded forcing. So you already prove this kind of a result when we did this or take a construction a long time ago that if this E dot plus lambda E type thing goes to zero, then he has to go to zero. Right. So this immediately implies that E comma E dot both go to zero as T goes. Yeah. So it's enough for us to show that R goes to zero. So that's what we aim to do. This is essentially like an ortega type construction idea. Right. Even in the ortega construction, we did the same thing. Right. Great. So if you don't remember again, I would ask you to go back and refer to the ortega. All right. So that's what it's mentioned here. Yeah. Right. So E exhibits stable behavior. In fact, E is less than R. I mean, even if you don't have, you know, I mean, of course we are talking about R going to zero in this case, that may not happen. But even if our remains bounded net has some nice bound or just by virtue of this equation that I know R is E dot plus lambda E, then it's it can be shown even without talking about things going to zero because honestly speaking in this article we'll not be able to prove that anything goes to zero percent, but we only prove nice bounded performance because after all, you know, whenever we talk about using neural networks for functions, it's eventually an approximation of the function. So there's always some error. So obviously if there is some error, you cannot expect just like in case of the disturbance, you cannot expect to put things to converge to zero. Yeah. So the best you will do is get some kind of bounded performance. So just with the relationship between E and R, you can actually conclude that the two norm of E is bounded by the two norm of R. And similarly, the two norm of E dot is also bounded by the square of norm R square, norm R square. And so this is important to remember. Okay. Then we also have very standard properties of the robot model. So M is basically positive definite symmetric and therefore it's satisfied this kind of an inequality. Right. So you remember that whenever you have positive definite symmetric matrices, you have this kind of an inequality. Yeah. The second property is that VM is bounded. Yeah. And by some, you know, continuous function multiplied by nine. Right. This is again a property of the centripetal Coriolis term. Okay. And the third property, which is a very important property in the Lyapunov analysis is that the matrix M dot minus twice VM is two symmetric. Right. What does it mean? It means that any quadratic form, which is alpha transpose M dot minus two VM alpha is zero. Yeah. So the, so the quadratic form corresponding to any symmetric matrix is always zero. And so that's what we have in property number three. Of course, we assume that the disturbances are bounded. So, not on this, but yeah, we assume that the disturbances are bounded. This property five, we don't use yet. I mean, we don't talk about it. Yeah. Which is why there is a sign on an R. Yeah. That's why you had the sign on here. Sorry, the Zeta naught here. Right. So if you remember the Zeta naught, that was sort of inserted here. Yeah. The purpose was to talk about passivity, but you remember that we said that we not discuss the passivity aspects of this article in these cities. Yeah. So as of now, we skip it. We need to talk about it later. Right. This is a property. Yeah. So this is not an assumption. These are properties. Yeah. So it's not like we are assuming anything. So of course, this property can also be proved. There's a nice reference that's given for this. All right. Excellent. Excellent. So now we know that we need only good behavior of the R. And we have the dynamics of R given by this equation 14 here. Yeah. Which is also something nice. Now if F tilde was zero and tau D was zero, then this is well known to be a stable asymptotically stable system. Yeah. So if both of these are zero, then you are in very good shape. No problem. Yeah. Now the issues happen when this is non-zero. And of course, there is disturbance. So of course that also if it's non-zero, then, you know, this is at least bounded. So you want some bounded performance. So what you need at the least is that you have some nice bound on this F tilde. So this is the least you want. So you want a good function approximator. So that is why you start talking about the neural network control. Yeah. That is where we start discussing the neural network control. Right. So, so that's what we say that this non-linear robot function should remember. 11. So this guy. Yeah. This whole thing assume that it is given by a neural network as in three. And so it's essentially like a the function effects is replaced by this kind of a weights thing. I mean, you had it here. You had it here. Yeah. Suppose this function effects is approximated in this manner where of course, epsilon is small enough. And then you have these weights and offsets and so on and this activation function. So it's like a approximated by a three layer neural network. Now, why can we do this? Because by this nice theorem 2.1, we have that, you know, you can approximate almost any continuous function in this way. And effects is of course continuous. So, of course, we have this fact that this error is bounded by some constant episode on end. So you always need bounds on the other side. If you don't have bounds on the errors, then you can't get bounded performance. Right. So, of course, there is results would say that these ideal weights are not necessarily unique. Yeah. So, so I mean, that's one cannot expect like, you know, when in standard adaptive control problem, the value of the parameter is sort of fixed and known. For example, if you say the mass of your drone is unknown and you use an adaptive controller, so the mass is a fixed quantity, right, you know what the masses. Well, you don't know what the masses, for example, but you know that it is a fixed quantity. But in this case, that's not necessarily the case because these are not masses and properties of the system, but these are more like weights to some kind of sigmoidal function which is used to approximate actual nonlinear function. So therefore, the choices are not necessarily unique. So, we should put this in. So, of course, this according to theorem 2.1, this mild approximation assumption always waits for continuous function. Right. So, but so anyway, so this is of course, this is of course, the important part here. So, then of course, just for we define a new notation, which is this z equal to 0 0 v, this is just to make our lives easy in terms of notation. Right. Now, before doing any actual neural network type of design, what we want to do is to look at a few different bounding assumptions and facts. And some of them are assumptions, of course, and some of them are facts. That is to say that some of them are guaranteed to hold true and others have to be based on some assumptions. Right. So, the first is an assumption. The facts are easy to prove given the assumptions. And therefore, we start with the assumptions. The first assumption is that the weights are bounded. Okay. This is a very fair assumption. I mean, if the weights are not bounded, then possibly your function X is not bound. Okay. So, having bounded weights is a very reasonable assumption. Yeah. Good. The next is that the desired trajectory is also bounded. Yeah. So, desired trajectory is defined by QD. But here we talk not just about QD, but about all the derivatives or at least two derivatives of QD also. Now, this is, again, no different from the assumption which we made in our previous adaptive control programs. We just said it in words. We said that you have a bounded trajectory with bounded derivatives. Yeah. So, here we are making it a little bit more specific. You have taken QD and it's two derivatives. Right. So, it's, again, a very reasonable assumption. If you want your system to be following trajectories which are too sharp or too jerky and so on. So, therefore, you do assume that you have bounded reference with bounded derivatives. This is, again, something very reasonable. The important thing here is, of course, that this is a known constant. So, you know this value. Similarly, here also you know this constant. So, the important thing is that you know these bounds. In case of trajectory, of course, this is not difficult. But in case of weights, knowing a bound is sort of the kind of thing we assume when we talked about projection in an active control program. Right. So, in this case, we are, you know, posteriori assuming that there is a known bound on this, that we are trying to learn. Then we come to the first fact. It says that for each time T, X is bounded in this way. Yeah. So, X is bounded means it's not like a uniform bound or anything. But we know that X contains of, consists of what? X consists of Q, well, actually I should probably point it out here. Yeah. So, if you look at this, I'm sorry, we define X, yeah, right here. So, the X is defined this way. And so, X contains what? It contains QD and its two derivatives. So, these we already know are bounded by the cap QD, by our assumption. And then the error contains E and E dots. So, at least it contains what? It contains again Q and QD dots. Q and QD and QD dots and Q dots. Right. And this is of course bounded by some R along with some QD. Right. So, this is not difficult to see because that you can actually get this sort of a bound on X. Yeah, like a linear bound with respect to a fine bound with respect to R. Yeah. Right. So, now, you know, we sort of want to talk about using some kind of Taylor series approximations so that we can in fact do a deal with these nonlinear regressor parameter. Yeah. Remember, the linearity in the regressor parameter forms is what helped us design most of our adaptive fin solace. Right. Without that, we would be in quite a suit. Yeah. So, this is what I mean. It is E for extending linear NN to nonlinear NNs. Right. And this requires use of Taylor series based results. Right. So, this is what is important. Right. I mean, eventually when we have a nonlinear regressor parameter for the nonlinear terms in the neural network, we still want to look at some linear versions and we do it by taking Taylor series approximations of these nonlinear terms because without the linearity, it would be impossible to deal with the structure that comes about and different kind of nonlinearities that come about and it would be impossible to, you know, get any kind of stabilization results. So, we of course, as always assume that we had and W had our estimates for the ideal weights. Right. And we of course define the tilde versions for V, W and Z. Right. And of course, we also have the sort of error in the activation function values. This is defined using this notation as sigma applied on V transpose X and sigma applied on V hat transpose X. So, this is again a notation. Right. So, what we want to do is to sort of expand this into expand this with some kind of linear terms. Right. And that's the whole idea. Right. We want to use the Taylor series. Right. So Taylor series gives us some linear terms. Right. This is standard when we linearize nonlinear systems also. Okay. Great. So, so what is the Taylor series expansion of say this V transpose X? We know that we can be written as V tilde plus V cap. We take the V cap as the center sort of and so we have sigma V cap transpose X. Yeah.  So, you take the partial or the derivative with respect to X. Right. And then you have this sigma prime notation. Right. And then you have multiply with the error term, which is this V tilde transpose X. Right. And then you have all the second and sorry, the higher order terms here. Okay. I'm sorry. I think right. Right. We have the higher order terms right here. All right. Great. So of course, this is defined. This is defined as a partial with respect to some sigma prime is defined as derivative with respect to some Z evaluated at Z hat and so on. And O Z square, of course, define higher order terms. And this is all well known. Right. So of course, there are some, I mean, the author's point to some other reference where a different Taylor series was used, but that's okay. Right. So now, of course, we, the authors want to simplify notation. So they call this term as simply sigma hat prime. Why sigma hat prime? Because the sigma prime evaluated with this hack term. So that's the rationale for using this kind of notation. And so what do we have? We have sigma tilde as sigma minus sigma cap. And so sigma, we use, you know, this kind of an expansion here. Right. So what do you have? So sigma cap also contains, sigma cap is essentially this thing. Right. So whenever I subtract, if I subtract these two, I just get this term. Right. That is sigma prime. We had transpose. So let me fix this. We had transpose X. Right. And this V tilde transposes. So you get these two terms right here. Okay. And then you have a second order. Okay. So this is of course simplified. We just call it sigma hat prime. And this is V tilde transposes. So this, this, this term is just to, I mean, I'll just mark it. So this term is just this whole thing. And it's just a short hand. It's nothing other than that. So now there is also the requirement to put some kind of bounds on the higher order terms. And so we, I mean, the authors do do that. So this kind of a bound is sort of used. And again, this is I believe transfers. And so this is like this kind of a bound. It is. So let me see. I'm trying to see if this is any different from what we have different bounds are put on the, okay, okay, okay. So this term is bounded with, again, this sigma tilde, this looks like sigma tilde. Yeah. So essentially this, I mean, honestly speaking, this bound is essentially derived from this equation. Because if I take this on one side, I simply have this subtracting this. And this is sigma tilde. It's essentially sigma tilde. And then you have this guy here. Yeah. So this is what you have. So this, if this guy is to be evaluated, then you take this to the other side. So you have sigma tilde, which is this minus this whole thing, this whole thing. Right. Right. So now in order to get some kind of reasonable bound for this term, you use this expression 24. Right. So you have a fact four, which is that for sigmoid RBF and tan hyperbolic, so all the three activation functions that we looked at, you have this to be bounded in this way. And these are, of course, obtained using some kind of bounds on these guys. Right. So this is somehow using that. So because you see that these bounds also contain the Frobenius normal B tilde. Right. So so these bonds are obtained using this expression, right? Okay. So that's the whole idea. Okay. All right. So of course, they also use the, not just the, yeah, they also use the fact that sigma and its derivative are bounded by constants for the RBF sigmoid and tan hyperbolic. So of course, I mean, the authors mentioned that for nets greater than three, this kind of bounding and these kind of ideas and are not too difficult to extend either. And then it can be done. All right. Excellent. Excellent. Great. So what did we look at in this session is that we had already seen the robot dynamics that we saw a little bit more of, you know, sort of how the control structure looks in today's session. We also saw how the nonlinear robot function looks. Right. And we understood why are going to zero sufficient for our purposes. And finally, the, once we understood that this F tilde that is the function approximation error is what we want to drive as close to zero as possible. We understood that this is where the neural network comes in. Right. So this neural network is used to approximate this function using this theorem that we looked at earlier. We know that, you know, we sort of know that this function approximation using neural networks will help us to get close to value of F, therefore F tilde can be made to have like an epsilon n bound. Right. And that's what we looked at at how this neural network approximation will work. How we use the Taylor series to sort of linearize the terms in the neural network and bound the nonlinear terms. And this is what we'll use in the subsequent analysis to define these parameter estimation and parameter learning. And these parameters, of course, the weights of the neural network and we will hopefully be able to show that you have nice stable performance the way you require. Right. So we'll continue with our discussion in the subsequent session. And I hope to see you again soon. Thank you.


Hey Brent, how are you? I am hanging in there. Is still where you are, where you have been forever? Yeah, I mean, stuff keeps shifting around me, but I'm still around. Anybody else coming today, do you know? Oh, no idea. I honestly just want to scrub a non creds one. But I can't. No, we honestly should. I don't know anybody besides, you know, who that's actually using it. Technically, there are some former Everton customers who are still using it. But yeah, I. Like the revocation just doesn't work. And they keep finding more and more holes with it. So. Yeah. I mean, and just in the first place, it's not. Secure. I mean. Like if we wanted to use an RSA based solution that is more secure than we're going to need to up the. The size of everything. Which is a conversation you, me, Dmitri, and Jason lotter had in like. 2016 or 2017 or something like that. Yep. Like, well, okay, we really should up, up. A non creds. I wrote prototypes for that with 4k instead of 2k. Remember. Right. Yeah.  By the time we. You know, we shouldn't disrupt our current customer base and make them redo everything. Okay, should have.  We're not yet. Well, that's why I kind of said, all right, let's move to a non creds 2.0. I've been kind of doing that. So trying to get that going. Yeah.  Yeah, surprising. So, I mean, I'm having a hard time being motivated to work on anything with RSA related because there's so much legacy bloat. Yeah, I mean, we had a good push briefly to, but like, like. The PR was a 224. Well, it's like, it's good. It's a good PR. It updates things, changes a lot of stuff. But there's one line in it. That's currently pointing to like, like Dalek needs to be like Dalek needed to be updated. Basically, it's a reference to Dalek. And Dalek got updated. It's been like two months. And no update on the PR. So I'm like, I, I can't approve it yet because it's still pointing to a personal branch of Dalek. Instead of the updated one. And I don't have, I don't, I mean, is Dalek at 3.0 now or 2.0. I think they just went to 2.0. And we got released because last time I looked, it was still at pre. I thought it was officially out. Maybe not. I'm looking now. Because that was my note still says one. Oh, okay, maybe not. But anyway, I don't know. I mean, honestly, the two hours a week I spend on RSA is more than I can afford to spend. At this point. I don't know what to do about it. Because I, well, I'm freeing up some of my time, but I have a hard time justifying it. Because it's so bloated and no company I work for has cares about hyperledger at all. And that's the problem. Yeah. So I don't know what to do about it. So it's hard to justify it. I mean, if Ursa said, hey, all code will be audited. I don't know what to do about it because then I get the free audit, right? So, but hyperledger is not ponying up anything for it. So, and the, the only project I know that's kind of still going is fabric. Are you, I think there's a meeting later today. Is it today? Yeah, I was Sean. Yeah. I mean, that's. That'll be the time to get that question answered. Yeah, because I mean like heart never comes anymore. Well, no one ever since sovereign dissolved and ever in him, like kind of lived along versus had no, almost no activity really. Yeah. Yeah. And the Aroha folks showed up and we're like, Hey, we want to make this better. Like that sounds awesome. Let's do that. And we're just kind of stuck. I think they were surprised at how much. The amount of participation there was. Or how little. Yeah, it's pretty much died. I mean, I was doing most of the work before when I was at sovereign. And then since I left sovereign, it's had little to no action at all. Yeah, the pieces that people are using people are satisfied to keep using. I mean, I would have, I mean, I already have a non-crit's to working in a separate repo. But I don't know. I mean, it's just hesitant to donate it. So. I don't know. I mean, I probably get some good feedback. I just don't know. That's hard to say. So. I mean. If you could do anything right now, what would it be? Related to what? Related to this project. What would you do with it? I would just assign resources to update the BBS implementation so that it is more in line with the. Work that's happening at IRTF. It's just become bloated, man. That's why I gave up on it. I wouldn't use BBS plus period. I mean, there are constraints under which most companies operate that require them to care about things like standardization. Some. So I'm not swayed by the pure cryptographic concerns. Like, yeah, I get it. There are smaller and better signatures out there that are. It's not, it has nothing to do with smaller. Or say it's just the pure bloat that's come along with it. So. But I mean, quite frankly. Brent, every company I talk to, none of them want to use an ID. I think it's going to die as well. Because. Every, every company I talk to is adopting polygon ID. Because it's going into production. The system is easy for them to understand. It's based on open standards. So they're all going to use it. Not one. If anything polygon IDs. Implementation is going to win. And the non-creds will just fade into the background. And on credits one totally. No, the non-creds too. I think it's going to die as well. So they're all going to use it. Yeah, we'll see. All of the companies that I talked to are banking on Jason web proofs and BBS. And when you have somebody like. Paying identity and somebody like Microsoft. Saying that. I think that holds a little bit more weight than polygon ID. Like you might have some really slick stuff, but. Well, I'm the companies I'm talking to are all with three companies. A single one wants to use BBS plus. They kind of look at it and go, Hey, why would we use this when we can use polygon ID? Right. And that's fine for web three. But. I mean, I, one thing that was not clear to me while everyone was in his heyday was how. Utterly fringe most of the web three stuff is. That's the best fringe as you might think. Having spent the last four years in it. I mean, that's just it. You're in it. The view from outside is a little bit different. Yeah, I get that. But I think from what I, from my point of view, that gap is narrowing. So I'll be surprised at BBS plus. I'll probably find some market just because it's getting standardized, but polygon ID is like coin base is going to adopt it. And they've got quite a bit of weight finance, trust wallets, Verizon labs, lit protocol. I mean, all of them are looking at polygon ID. So polygon stuff that looks pretty slick, but. My biggest gripe with is based on grot 16. So that's a problem. So like one company wants to replace it with a different type of stark. But they can't justify the, the lift. Even though it's a better proving system.  You know, offerings from it, right? So you go, okay, we just replaced it with instead of gross 16, we're using Starks. It runs 50 times faster. But that's it. No new functionality, nothing. So. And because it's, you know, Starks are so large, they can't justify the on chain. Requirements. So now they're just back to square one. So I don't know. From a web, okay. So let me put it this way from a web three perspective, maybe polygon IDs, the winner. So what do you classify BBS plus then. And the non-crits group. Is that also considered web three? No. No, when you're, when you have companies like Microsoft that are building solutions on top of the Jose stack and OIDC. That's. That's pretty much as far from web three as you can get. But they're using BBS plus. Yeah. With OIDC. The OID for VC spec is. Dammed clever. They took the, the traditional OIDC three party model. And made it so that one of the parties. Is the holders wallet. So I'm still authorizing a relying party. To obtain information from whatever they call it the. The provider, but the provider is under my control. It's just my wallet. So instead of, so they've taken the, this is OIDC. It's always phone home. They've split it in two. So on one hand, I'm the reliant or my wallet is the relying party and I'm getting. Access, you know, for my wallet to gain information from the issuer. And on the other side, I'm allowing the verifier. To obtain information from my wallet. It's, it's. Converted it into a fully SSI like. To party system. It's brilliant. And it has all the people who are already using OIDC going, okay, cool. Instead of going, what's did come. So like they're building on top of that. They have. They have what they're calling selective disclosure Jots. Which. Aren't awesome, but it's essentially the. You know, the hash base selective disclosure systems. Where you only reveal the. You know, it's salted hatches. So I can reveal things or not, but you only ever see the salted hash values unless I'm revealing the information, which doesn't prevent prevent, you know, doesn't help with unlink ability doesn't prevent correlation. But honestly, BBS LD signatures or whatever it's called now doesn't really help with that either. No, it doesn't. They got rid of holder binding. They got rid of. You know, I mean, the way that the end quads are canonicalized. You're revealing identifiers right and left. Yep. So, you know, from a, from a purely able to track information perspective, it doesn't. I'm BBS LD side of things seems marginally better maybe. Yeah. So, you know, I mean, I've seen SD jot with a plain ED 255 19 signature on top of it. But tell you what, one of those is a hell of a lot easier to implement and convince big people to implement. Then the other one. And in the same vein, Jason, web proofs. Is. You know, gaining a lot of momentum. One thing that I've been impressed with like. I've done W3C for a long time now. There's a lot less politics and a lot more expertise. Yeah. Like people go. You know, I am a photographer and this is what I see going on here. Or I have built systems using these things for decades now and here's, you know, here's my concerns. Here's my question. It's like just the, the whole. You know, seeking to understand questioning aspect of it. It needs to, it seems to lead to better things. Yeah. So, so with Jason web proofs, you have a Jose. Affiliated data structure. I'm looking at the Jose web proof. Whoever wrote that has got PS signatures in it too. Yeah. I mean, it's, it's, it's legit. Yeah. Yeah. Yeah. Yeah. Yeah. Curious signatures in there. Yes. It's compatible with all of those things. And it doesn't have opinions about it because it's just the data structure. So. With JWP and OID for VCs. I have. Like. The, I have. Pieces of the puzzle that the federated identity people. Find acceptable and they still run the identity game. Well, and the fact that I can still see. The fact that they have PS signatures in there. I'm game. Right. Yeah. I mean, it's like, and the only reason BBS is going to have a foothold is because it's going to be the first signature that standardized enough for companies to use with JWP. It's not going to be the last one. Yeah. But it's going to be, it's just like, okay, I've got a job. How is my job signed? Well, the job will tell me how it's signed. So it doesn't really matter. Yeah. There's issues with that. Obviously bad, but. The fact that. 10 years ago, Jots were signed with something different than they're signed with now. And they kind of like the job still exists, even though. Oh, it used to be signed with an RSA signature. Now it's signed with. You know.  Or ED 25519. Or EDDSA, or just like, it doesn't matter. Yeah, it doesn't matter. I can swap out which ones I need to use or can use. Having us another data structure, that you can do the same thing with. I think it's going to be. It's going to be awesome from be like, Oh, And I also, it's hard to underestimate the impact that larger players have on the space. Yeah. You know, I would love honestly I would love for the web three vision to take hold and for. You know, the worldwide impacts that are potentially there to be realized but I don't maybe I'm just too cynical. You know, I've seen it I've seen it used for fraud and for grift. Far more often than I've seen it to change the world or attempt to change the world even some of the more dreamy Dow stuff that I've seen has been like borderline fraud. I don't blame you. This is why I like bigger companies, you know, like coinbase for example, or having to up there. Do I see right now. So yeah, it'll be interesting. You know, I still, I'm still mildly concerned that we're, you know, fashion the tools that will be used to create the perfect dystopia. I just fail to see how it can contribute to any of this stuff now. Yeah, it's, it didn't, it hasn't grabbed hold of people's like people just don't see it as a place to go to get something. I honestly wonder if I should donate a lot of the go code of cryptography I wrote and then because they feel like more people are prone to adopt that then rust personally. Yeah, I mean rust is great. I love rust, but Oh, don't get me wrong. I love rust but no one else does. It seems like the only companies writing rust or those writing cryptography and web stuff like Cloudflare has tried to get me and they're doing tons of stuff and rust. It's not even cryptography related. Cloudflare is doing a lot of cool stuff period. Yeah. Did you see their real world crypto thing. Now, I've been to robot crypto since I left sovereign, unfortunately. It was, I've seen two projects they're doing but I haven't seen anything new cryptography wise that they're doing other than privacy pass. Yeah, the privacy past stuff is pretty cool. I'm trying to find the What year was it. It was the one that just happened. Try to remember which one it was. Was it the zk. Oh, I think it was the I'm pretty sure it was the post quantum privacy past stuff. ZK dilithium with an all this of course being actual on credits not Indian on credit. Yeah, really just pretty cool stuff. I mean they've taken basically they taken the, you know, the potential lattice based that has been interesting, but only theoretical or semi practical so far. And they've, they've made it so it's legitimately like, okay, this is potentially actually usable like, I don't know it's It was interesting. It was like it was the, the leap forward kind of presentation that I wasn't expecting for another couple of years. Like, you know, here's how we did post. You say a non creds what do you mean, like with stuff like this right on credits. Well those are only good what time is privacy past tokens only good ones. Yeah. So I was just curious what that meant. Really what the presentation was on was a post quantum blind signature. Okay, that's like an actual practical in size and scope post quantum blind signature that's what was kind of exciting about it. Anyway, yeah, real work there was fun this year. Oh, I see Greg Nevin presented how a blockchain can keep many secrets. Yeah, it looked interesting. Yeah, I saw the time lock one. Yeah, there was. During the Nevin talk. It came unfortunately came across more like, or like an advertisement, then like a solid thing. It was a, it was an advertisement for the internet computer more than it was a, hey, this is cool tech kind of presentation. That was annoying. Well, I'm just curious what where we go with person now because honestly I don't, I think there's existing people that like it, but I think all new stuff no one wants it. Well, I think that there's a lot of potential there. I think. You know, there's, there is a solid plan to reconfigure it so that it's not as bloaty so that I can just get the pieces out that I need. Well there's a plan but who's doing it. Exactly. Like there was some. We've had like the PR like the aroha guys who are like going to start doing it but they're also busy doing a roja. I don't know if anyone that's using a roja. I mean, I, I'm going to. I don't know how much longer I'm going to be able to justify the time that I'm spending on it. Yeah, me neither. Probably have to bring that up this afternoon. Yeah, me too. Well, there's nothing else to talk about we should probably just get 30 minutes back. Good to talk to you though I guess I'll see you this afternoon. All right, see you Mike. Okay, see you. Bye.


Ray, one all draw this afternoon at the University of Brockwood Stadium, how would you reflect upon that game? I mean it was a pretty tight game, they had some chances, we had some chances and then obviously they got the goal but we kept at it and then eventually we got the equaliser Adam. I'd say it was a good shift from the boys, everyone kind of gave it their all and I thought we were good in both halves at certain periods you know and yeah I mean draw unlucky to not come away with a win but I mean we'll take a draw. Yeah enjoyable brilliant in terms of the numbers of the card the boys knew about it leading into it so walking out brilliant and in terms of the game yeah I thought we'd go with the things probably the best we've been. Disappointing so not take three points, seeing the goal back as well probably disappointing as they all are but impressed boys were really hard. Made up that we got the goal because I think it's the least we deserve made up for the fans for the boys and yeah I think it was a positive day. And again sort of holding them to just one goal they are a very high score inside we've come off the back of three clean sheets as well the defence doing very well at the minute how proud are you of that back line? Yeah yeah I think it's probably being the common theme in terms of last year before I was here and since we've moved on we've always been solid and I think there's been little blips on the way but really proud we've got we're blessed with centre-arts at the club Ashley's obviously coming in done brilliant today and Pat is done brilliant and Keyron and JT when we've all been in so yeah we're all together we all train hard we're a close group in terms of centre-arts as a defender so proud of that as disappointed as we are with the goal like you said I think there's one of the highest scorers in the league so to limit them to one or to limit them to seeing the shots back a lot I think they had eight but none of them are really you know testing the other one the first half in the goal so so positive made up for Adam as well in terms of the other side of the pitch to get his goal. And getting your first goal as well how good was that like what was what was the initial feeling when you when the ball hit the back of the net? There's no feeling to describe that it was unbelievable just all the fans just cheering so wow it's a good feeling. The balls just bounced up in it and then I just landed on it and then I seen Adam running through so I just thought let me just give it him and then obviously Magic in it done the rest. And I'm not sure if you've played in front of the crowd this size before I think over 21,000 in the building today really intense atmosphere both set of fans well up for it. What was it like playing in that sort of atmosphere? Yeah it was good. Lively and I think that's how the fans kept backing us when we was one year down. Oh you always hear them at home I think today was even more so to be fair to the rectum fans well being down this end you could hear them but it's positive especially when they sell it out and we sell it out it makes great atmosphere it's great occasion great day and I think the game probably replicated that it was high template I remember thinking first 15 that started started quick and the fans the fans have been great like I said the day have come in. We've had tough times at times but we've had some good times and they've always been being there backing us so today was brilliant hopefully we'll get a few more days like that and we can try and get the three points reward them. It was a great feeling like again the type of describe if I could bottle the feeling up and take it home and I would but it's like there's no better feeling than that really but it's a good atmosphere and it kind of just pushes you a bit more. And back into the Saturday choose the cycle with the trip to Milton Keynes on Tuesday night are you looking forward to that and what's the feeling in the dressing room ahead of that? Yeah of course I mean you just have to keep going every game because it comes around quick Saturday Tuesday so again we'll just on Monday be getting ready again for the next game. I think everyone's really confident like obviously it's a good point today obviously we wanted to win but there's a good vibe and a dressing room at the minute and everyone's looking forward to Tuesday. Yeah brilliant tough week in terms of in terms of the teams we're playing with the travel and then it will go off to I think next week's Tuesday Saturday as well so so the boys will have to be on it and it'll be it'll be a team effort will be like Kev said then to be fairly it's it's it's a it's a team thing you know boys will will be disappointed to not play but I'm sure everyone is gonna get used moving forward so but now in terms of the atmosphere brilliant really positive we've thoroughly enjoyed working with Kev he's been brilliant and I think probably the results have looked that way. So yeah excited for the week big game Tuesday nice stadium big team so we'll go that positively and then we'll move on.


Everybody forced here ripping 2022 NT collegiate football hobby for box case number 14 random team style You can always find these results right here late in sports cards calm. Thanks for joining everybody and good luck. Here we go NT collegiate let's see some wild patches Does anyone have favorite patches out of this product? Rose Bowl PlayStation fiesta Bowl Citrus Bowl orange Bowl Team logos maybe like Ohio State or Georgia I tried I guess we're starting with that one Chick-fil-a patches. Yeah, they took filet one There was a an iMac member the cheese it that cheese it patch lane, but the cheese it bowl That was a good one. You can also see Reese's patches from the like senior bowl patches Those are pretty neat magic be the captain preseason championship on the way to Orlando this year everybody DG. What's up? What's up? We'll see a one-of-one here Bill's Josh Allen 46 of 99 Jersey card Colts Alec Pierce 7 of 75 Didn't he just lean into it? What does happen there? Did he lean into it? Got team logo signatures Brock Purdy 42 of 49 49ers Can you see that? Silhouette signatures patch auto Carson strong Eagles 35 of 39 Oh, it is bad. It is bad. Did it go fair? No The one foul and I mean if that's the third try this third strike is it if you can't foul on a bunt. No hit the bad day What just happened? I'm trying to process it too Vaughan that was wild That's a bunt foul. That's that's a third strike Another Carson strong here 13 and 99 Eagles Oh weird Silhouette signatures patch auto Kenneth Walker the third seahawks 23 of 39 nice three color Michigan State patch That was so fast I guess you could hear that the bat if you're right next to it though If you're watching live What a way what a way to go out. Oh, and then he got got out of it looks like yeah And patch auto Texans Derek Stingley jr. 24 of 39 Texans all right back to the breaker. Sorry. That was just That was very confusing for me Steelers Kenny Pickett One of 25 on the rpa book Congrats Steelers Picket here picket there picket everywhere. Go Ryan B Congrats on the picket. Heck. Yeah, man. Awesome picket Padres got a bunch runners all left on base right now Like four left on base after two innings God Joe burrow nine out of 10 nice jersey number Joe the Bengals Kyle Hamilton on the team logo signatures 15 of 49 ravens Nice vet hit here jersey auto Justin Jefferson 77 of 99 Vikings Jay Jetta's right there So good. It's a weirdly thin jersey auto cards Jersey auto for the Buccaneers Chris Godwin one of 99 Thank you. Yeah, I appreciate it What do you bring you I needed some more Those are fun. Those are fun jumbo jerseys sam howell 73 of 75 For the commanders Yeah, he is a beast Um, get back on the cards. I recommend opening opening something cheap first buying singles that that sort of thing just to get your toes in and You know see what things sell for in ebay and all that good stuff 42 and 99 jumbo jersey matt corral for the panthers Just to get familiar Redemption CJ shroud treasured moments signatures blue Random at the end big time shroud. Good luck on that one everybody And falcons desmond ridder rookie jersey auto book to 75 73 or 75 Good break so far. I got straw. We got pick it Come on bullpatch Let's see it Let's get that 2021 NT filled up as well Random division style. I think it's down to one I think it's got one to go everybody. That's it. That's it It is down to one. There's still five Diamond memorabilia break spots left as well. Those are random hit style You're guaranteed to hit from a diamond box, which could be freaking huge Any brady zappies tonight?  I think we had Maybe like a numbered and legacy. That's a bet it so far. Maybe one's coming though Aaron donald the 75 rams 57 to 75 Book wandale robinson. There's three books in this box. Sorry, Sean RPA book wandale robinson 40 of 49 for the giants There's books this product just to have books in the product. They're just like, you know what? Yeah, we're putting that way everyone stop loading tonight, dude. There's needs to be a product of only books It's like playbook, but it's like three books a box. That's it. Oh my god. There you go giants Hasan haskins 2 of 99 titans ricky jersey auto book Chargers rpa isaas spiller 33 of 30 of 39 Chargers two color rpa patch Jersey card, justin herbert one of 10 Quack, quack, quack, quack, quack.  Nice damien pierce. He's been a beast for about two or three weeks now, right? And steelers patch auto george pickins 18 of 25 man steelers do so well on this Grat steelers on the awesome hit Ryan be again. We'll get that magged And last box Dodger's threatening now too on no out and snell Uh-oh Running into some trouble Who's coming up? Who is that? Can't if she's a big glare. Is that taylor? Barnes, Barnes the nine hitter Uh-oh mookies up Most likely getting mookie and freeman here. Oh something's stuck on the bottom of this one. Okay That's fun Bill's josh allen 42 of 99 kj. What's up? Jersey auto alec pierce 26 of 49 team slogan signatures colts Is he the number two receiver? He might be Chargers rpa isaac spiller 14 of 39 Another spiller rpa to 39 Patch auto mattel durant 2025. I keep looking this guy up. I forget it every time steelers and it is steelers I remember now steelers mattel durant 2025 patch auto Super mario patch car 3 of 5 marcus mario da or the falcons Patch car dak press got one of 10 cowboys And we're tired too The show goes on Show goes on damian pierce jersey auto nice break for the tech since 43 of 49 You go gator. Oh I'm never actually saying Who would say go good? And a notable nicknames auto jamo jamus and williams 19 of 25 Jamo, I think of a certain spirit If you will There you go lions nice jamo auto Because the old the old jamison's what I think of Not not uh, not james williams, but uh, yeah, it's the best my favorite So good Here let's try this and I was like, oh hell I'm gonna do with that I tried it. I was like give me more Never wanted the pale juice so bad. Give it to me Uh Stroud all right shroud redemption random to everybody big one one of the bigger cards in the break actually Good look We're gonna go four times on the random. I rolled doubles again So why does she keep like a four rolls doubles counter because it happens more often than it doesn't It's pretty wild All right, I don't know why that Four times over some time gets the stroud. Good luck one two three and four victor victor j Congrats on that one potential first qb taken For the gators got this week paul Dude that'd be so sick if tennessee beats baman this weekend Also, that's a question paul as a gator fan. Are you rooting for bama or tennessee? In that game Tennessee is not a huge driver. It's pretty big. It's not like george of florida like that's a big rivalry Or like florida florida say that's a big rivalry. All right. Here we go. Cowboys. Dak Prescott patch card super mario falcons three of five Yeah, that's a pretty good man Exciting team got one of ten justin herbert with the chargers kennedy brooks eagles matt corral hanthers A sam howl for the commanders and alex pierce to 75 for the colts Um, we'll go rpa books now demian pierce For the texas i'm always pausing on him hassan haskins titans wandale robinson giants desmond ritter falcons And kenny picketed 25 Nice Steelers autos now jamo nickname auto williams for the lions demian pierce texas mattow durant steelers asia spiller chargers alex pierce colts asia spiller again for the chargers out 33 a 99 and you had the 14 of 39 justin jepperson for the Vikings chris garwin bucks kyle hamilton for the ravens derrick singly jr. texans Kenneth walker the third seahawks carcin strong eagles carcin strong eagles rock purdy niners Got a cj stroud there went to victor jay and the random congrats on that one na pickens 18 of 25 patch auto steelers That's gonna do it. Thanks again, everybody. We've got another nt collegiate coming up


Realistic Gaming here. Today we are back in Animal Crossing EXC. As we can see, Animal Crossing has just released like past week or two on the Switch. So that's pretty big right now and today we're gonna be doing an EXC version of that. So let's see how that goes. And whenever the comment of the week goes to Victor Bradley. Now congrats to you Victor Bradley and make sure to comment below so you can claim your code. Alright, so let's begin with this animal crossing. Let's see where this takes us to. It should be quite interesting. Okay, what is your name? My name? That is one very hard major question. Oh, okay, it's Villager. I don't want to be just Villager. I want to be something else. Let's be Villager. Let's be Villager Yee. Okay, Yee. Oh, we can't spell it. So we're Villager Yee. Alright, we're Villager Yee for today. So let's press OK in advance. Okay, so he's asleep as we can see here. Yo, wake up buddy. Get out of bed. Oh, it just seems like there was some sort of explosion or something. Alright, let's get up and roam around. Let's go see what that was. It kind of shook the whole screen. I don't know if you guys noticed that. It must have been like a major explosion. Oh, it was right here. Dude, there's like a hole. Maybe a lightning struck. That could have been it since it's raining. Okay, I don't know. Let's still have a look up here. Okay, there's nothing. Okay, I guess we crossed the bridge to Terabithia here. It's not really to Terabithia, but it's just leading us somewhere. Okay, so where are we? We're like in the forest, huh? Okay, here the gust of wind blowing. So this can either go very terribly wrong or it can just be very normal and we can just be wandering about. But let's figure that out ourselves. My god, okay, I think I found the correct path. Very good. Dude, that's K.K. Slider. What is he doing out here? He's playing his guitar. Well, hello there, villager. Yay. It's been quite some time since we've met. You know, it's not a good idea to be out here at night. I was put here to go out the woods for a bit. You might want to go back. But before you go, why not check that tree over there? What? Why does he want us to check the tree? There's something there for you. Okay, I meant to give it to you this morning. My god, all right, let's go see what his surprise is behind this tree. Or on this tree. What?  Oh no, the EXE has begun. The EXE madness. Oh. I just heard like someone get slashed or something. This is not a bueno. What? So we're Isabel? Oh no, we're going up to Isabel. Oh, that's us. I think we might be evil or something. Mr. Mayor? Wait, is that us? He said Mayor. We're the villager. What? We just got jump-scared. That was it. That was the end of the Animal Crossing. He killed Isabel.  Okay, well, that definitely came out of nowhere. Dude, that's it. That's the whole villager crossing the EXE. Come on. You guys could have done better to this. Right, so I found this game on Game Joel. I don't know if you guys know what Game Joel is. It's right here on the screen. They have like all these fan-made games. We're like just games that people make in general. Like scary games, funny games, whatever type of games you can think of, man. We got it. It's like another Roblox. You can say it in a weird way. Right, so it seems like there was supposed to be a Part 2 10 months ago. What? So it seems like there was supposed to release a Part 2 since we just seen Part 1. It was fairly short. But I mean, I like the whole little jumpscare and everything they added to it. So I don't know if Part 2, well, it says in development. But I don't know if it's ever going to release or not. I guess we can just hope it does so we can continue off this little four-minute gameplay we just played. Oh, guys, that was fairly short. Well, that was Animal Crossing EXE. If you guys enjoyed the video, make sure to slap the like button. If you're new to the channel, make sure to subscribe and turn that notification bell on. And I will see you guys in the next one. Yeet!