Okay, welcome back everyone to day three of CUBE coverage here at open source suburb. I'm John Furrier. We're here covering all the action. My co-host Rob Streche analyzing all the data, conversations, our next guest is Matt Butcher, co-founder and CEO for me on great CUBE alumni. What's great to see you, welcome back. Thanks for having me. So we just chatted at CUBECon EU, CloudNativeCon in Europe, 10,000 people. Yeah, it's fantastic. 2,000 on the waiting list. This event is much smaller. It's more of the insights, the premier show where all the leaders are here, the white people. Not big numbers, it's not designed to get the big numbers but all the top brains are here, Linux Foundation, to look at across all the projects and assess the future, how things are going. What's your take on the summit so far? I mean, before we get into Fermion, what you guys are doing? Yeah, and I can, I mean, this is one of my favorite events. I've been many, many years now. In fact, Fermion's first ever conference was an open source summit. The open source summit in Austin was our very first one. And the reason why is because you get here and you've got lots of different tracks across everything from very low level kernel stuff up through the cloud and on into things that sit on top of the cloud or roll up on the operating system stack. And this is one of those rare opportunities to see, like you said, the leaders of these communities, some of the contributors that you never see out in front of anything but who are quietly pushing specifications forward and the kinds of code that's holding up this kind of massive edifice we build. And they're all in here, like cross-pollinating and sharing ideas. And you see things happen here that just start seeding changes that might even take two or three years to get to, right? As the idea is spread out. But in open source, you know, you get this diaspora effect normally where everybody's kind of going that way. This is one of those rare opportunities to sort of gather people back in together. It's the brain trust really of open source because there's so much change coming on. We've been reporting and we've been kind of pointing out that we turned down other events to be here because there was like, why are you going there? Like, because we can sniff out change. We know where the cue goes, where the action is. We'll do whatever it takes. But seriously, there are structural changes that comes out of this that will have a trajectory and ramifications and economies of scale. There will change the makeup of how the foundation looks. And let's face it, open source one. It is now the software industry. It's no longer staying on the shoulder of giants and, you know, beat the proprietary, they're done, they've been beaten. We have this proprietary differentiation out there in software, but it's generally accepted principles now that the software industry is open source. Okay, great, check. Now what happens next? With the wave of AI coming, for me on your project, your company, your team, you guys are solving a lot of the same kinds of problems. Make things easier for developers, but at the same time, get some stability under the covers. This is real big trend, this idea of making things simpler. Yeah, yeah, I mean, I think we see pendulum effects in a lot of different areas of, you know, science and industry. And this is one of those where, you know, there was the developer oriented movement in the cloud early on and developer oriented, you know, has platform as a service, right? Heroku comes along and really says, developers, we're going to make the cloud a thing that you can do without ever having to know anything about the cloud. And then the pendulum started swinging and we hit Kubernetes and then all the things layered on top of Kubernetes and, you know, the gigantic menu of services you get at AWS and at Azure and all of these hyperscalers. And it tilted very heavily toward ops and we started to lose developers and developers started saying, I don't want to be an operations person, simple by my life for me, right? And serverless is really the pendulum swinging back the other way, serverless functions, the kind of thing that Lambda really kind of pioneered but now we're seeing the sort of resurgence of serverless is a paradigm because developers say, hey, this is easy. So, you know, Fermion, we're all about making things easier and WebAssembly seems to us to be like the platform upon which to build sort of this next little motion, the next wave of cloud computing. Please explain the product. I know we had many times on theCUBE with folks who haven't heard about it because my first comment to you, I think the first thing is about time, someone did this like, what took you so long? What took everyone so long? It's a really simple concept but it took a while and it makes so much sense. It's the future. This is what it should look like. This is success, explain the model. Yeah, and the thing about the way we have built things as we kind of built up in that complexity chain was we started building servers and every software developer has to build kind of a big stack of stuff in order to handle the business logic that they care about. Serverless makes it possible for the developer to say, look, the only thing I actually really care about is this little chunk here. I want to get a request in, want to do a little bit of work on it and I want to send it back. Don't want to know anything about the infrastructure, don't want to know anything about how many systems my thing is running on. I'll build it to be scalable because it's a small bit of code and I'll push it out there and everything else is an operational issue. And that's a lot different from the Kubernetes world. And as a creator of Helm, which was designed, my original intent with that was to build a tool that would enable developers to express Kubernetes concepts in a very easy and reusable way. Not realizing that actually what I was doing was beginning to contribute to the complexity. You know, I was contributing to the problem and suddenly the developer is like, you're telling me I need to write 5,000 lines of YAML and I'm like, I don't know. This is really like an overcorrection for me personally in the other direction. We want to make it so that the developer just writes a chunk of code that they care about and then they push it out there. That's a funny story. That's the story behind the story. You're actually trying to make it better but you made it worse. Yeah, yeah. Which makes you zoom out of home. This is penance.  So I go through China, do I go right through China or do I come out? And I mean, I'm going to say, home is a good tool that has good use cases but my original assumptions were wrong and I contributed to the complexity. Yeah, I know. Yeah, and I think that was actually one of the funny things coming out of KubeCon was the fact that all our demos are still using YAML on stage and how that is really a blockade to getting new people in in a lot of cases.  Are you seeing that it has particularly good use cases for certain applications? So we built it with the assumption that the primary use case would be, you know, building web applications, building the back ends for web applications, building microservices because, well, in part because we've all done those, right? That's just day to day bread and butter coding at this point. We were a little surprised to see that as generative AI took me by surprise, the sudden boom of that took me by surprise as much as it took anybody else, right? I played with AI for years and always thought, yeah, this is a nice little toy, it's not going to go anywhere and then suddenly boom, right? And now we're starting to see people use that because the serverless model and the open AI and generative AI models, that works really well in a serverless context. You've already got this big, beefy thing that's doing a lot of the really hard work. Now you're just writing small things on top of that that can take user input, do a little transformation, get, you know, query the AI and then be able to return some. So I think that's going to be. I think this is the dynamic of AI. We've been asking the question, this tornado of AI is going to impact open source. The large language models and the foundational models, large languages, text, you got audio, video and images and audio and video are really have changed things a lot, even though they're large and take a lot of energy and GPU power, sustainable issues we've been reporting. But the open source community is building more smaller tools. It's starting to get into this kind of self-efficiency configuration and it has that web assembly vibe to it. Yeah, they're very complimentary technologies, honestly. But I think a funny thing happened, like even from when we talked at theCUBE in Amsterdam, you know, when the universe was opening up, right? And we're like, oh, there's all these possibilities. And now we seem to be in that funny moment, happened with the web too. We're in that funny moment when it's like, okay, something big just happened. What do I do about it, right? How am I going to interact with it? And in one, you kind of see some people saying, okay, you know, the end of the world is nigh, right? This is going to destroy everything. But even that seems to be sort of tapering off and now we're going, okay, we understand realistically what this technology is. And it's going to bring some big possibilities. What are the possibilities, right? Is this a good idea? Is that a good idea? Good discovery. I mean, I think the web example, I love the example more than the iPhone because I think the web was crude at the beginning. We all know dial-up, the websites and HTML and HTTP with the foundational protocols for all that markup and then transport. But it was all about a new user experience and capability. I could do new things that might have been crude. So it was a lot of possibilities and how people did things. So a lot of conversations around reducing the time it takes to do something, reducing steps, making things simpler and easier. So those things were in play while advancing functionality. So it was like an entrepreneurial dream. A lot of action happening, opportunity recognition off the charts. Everyone saw a piece of the action, hence the bubble. But somehow we forgot the fear that people felt about that too, right? And we confront fear with large language models and suddenly it's like, oh no, the grand edifice of copyright is at risk now. But that, and in fact, I bring that one up specifically because that was one of the concerns with the web. If everybody can get access to all this text, then the grand edifice of copyright is over. Didn't happen, right? And so there's this, the fear here is starting to move out of the way a little bit. And particularly when you come to a place like Open Source Summit, right? Where you've got a bunch of people who are going, we get excited by the possibility of technology. What can we build upon this? Well, there's a lot of people, I just, on New York Art, I just had a rant on my podcast around, they were fiction writers. I thought he's hallucinating personally. I thought it was written by AI. His whole point was, will AI turn into McKenzie? And then he's, so he's got double, double trashing everything, McKenzie is evil, chopping the blades of capitalism to take away your job. When you look at augmentation of human behavior, creativity explodes, the web did that and then made things easier to find things, and search, self-service. And if you look at, like, say chess, when computers played against each other, they were good, but when you gave a human augmentation, they played better chess against the best people. You have an average person, chess player, can become a grandmaster with the augmentation of the computer that was well-documented in the chess days. And that's a perfect metaphor, not a metaphor, it's a perfect example that we can draw a perilous. But first, you know, now I really want a shirt that says, humans hallucinate too. That was, yeah. But chess is a good example because coding in a way, when you think about chess as a rule system, right? And it's a rule system where I compete against you and we're following the same set of rules and there's an objective. But coding is a rule system to the same extent, right? And I remember when Copilot came out from GitHub and my first reaction was, yeah, I mean, we don't want to use a tool like that. That's basically going to make me a lazy programmer, right? That's going to make me worse at my job. But I was talking to a friend and he's telling me, you know, we measured that, we mandated for our team, all but three people are going to use Copilot. This is Wade from Muvio and he said, what they discovered was that all of the developers who used Copilot to help them write code experienced a 30% boost in their productivity.  And that's remarkable. And these were not like... This is real results. Yeah, yeah. And these were not engineers that, you know, were inexperienced or were learning. These were engineers who were already relatively seasoned and it's just having some... XP, right? Extreme programming and pair programming, right? We looked at that and we said, this is going to be a great idea because when you got two people sitting side by side and we're writing away our code, we're going to produce better code than if I go out and write the code by myself and then try and explain to you, okay, you know, these 4,000 lines of code do something, but you know, in a way Copilot really is sort of the next iteration of pair programming. You got something there that's just, but it's a lot more flexible. You don't have to take lunch breaks at the same time and be in your seats at the same time and share the same keyboard, which is just gross. But I do think, you know, this is a, that initial reaction of fear, right? That, oh, this is going to make me a worse programmer or worse. It's going to make me an obsolete programmer. And every single inflection point, the argument was, you know, jobs will be lost, bad for the economy.  More bank tellers now than they were before ATMs. So services do shift, creativity shifts. I think the augmentation has been a big story here. And the question that we've been asking is, okay, open source went one, the generations of success and the shoulders of giants, will AI topple the infrastructure of open source? How the foundations are organized, the structure? Because they were built for different purposes, the same goal. They had very thin at the top management, they didn't want to overspend on overhead, put all the money towards the product, aka open, and communities. And that was just a very efficient model. And everyone bought into it. Does AI change that, the people equation, how people interact, ecosystems are developing? If it's an industry power dynamic, is that different than say, organizational kind of dynamic? What's your view on that? Well, when there's so many ways you could go with that, but you know, if we rewind back to the 90s and say, you know, when there was that open source versus the enterprise story, right? And open source was seen as a threat. The rallying cry to open source was, we're going to democratize the process of writing software. But really, we didn't totally mean we were going to democratize it at that point, right? Because not all of us knew how to write code and not all of us could participate in this ecosystem. And it was been able to dictate our model. Oh, yeah, well, yeah, well, yeah. By democratize, we mean approximately replicate other models but without anybody making money. Kill proprietary technology. Kill proprietary code. Yeah, that was the real reason. Yeah, and now, but if AI provides us a tool that will help people who have never written code before to start getting involved or people who are reasonably experienced in one language in one domain, suddenly pivot and be able to contribute to another project that's in a different language or a different domain than they would have and have the AI essentially act as that, you know, that other person that you're pairing with. And then we're suddenly going to get, we're going to get a multiplicative, it's going to multiply. Yeah, I think that's the interesting thing is like, again, like, hey, I built this in Python, now I want to go do something in Rust or something like that and trying to have that portability. And I think that's the interesting play with AI. And I think actually it levels, it actually levels the playing field versus unleveling the playing field. I mean, there will be people who can take advantage of it better, but it's a tool that can have that effect of, and I think part of it is, I'm interested in this, I think it will help people get to MVP, get to that first product a lot faster for a lot of these different companies. So if it results in more software being produced, we think that makes a better world, right? Yeah, well, to your point about peer pair programming, extreme programming, I think that's a great illustration that ties back to the chess example. Human plus AI is better than AI alone. That I think summarizes all the conversations we've had on theCUBE this week. Ed Warnacky, who pointed out that book from Tyler Cohen, Average is Over, points that out with chess, and we hit it up with coding. This is human and AI is better than AI alone. So I think, okay, it's a tool for, if you want to look at it as a tool, it's a tool. If you want to look at it as augmentation and an assistant, it's an assistant. If you want to look at it as automation, the heavy lifting, undifferentiated heavy lifting, but the human can move faster with the brain cycles. That's the thesis, you agree with that? Oh yeah, absolutely. And we have to acknowledge that there are scary ways that that could happen. As is the case with every single innovation we have made in the history of mankind from a wheel onward, right? But the opportunity to use those tools to achieve more, and you asked earlier about open source communities, to expand the community to include people who could not participate before. That's a tool we're having, right? The thing that's happening, that other thing we're observing, and I'd love to get your thoughts on this, is when you have these shifts like the web now with AI, some things went away, mechanisms, because the goal's still the same. The mechanisms change. What changes with AI in open source? Is there things that kind of were built for the old model that go away? If the goal is to have great seamless API interactions, systems thinking, I bring this up because the word platform engineering has been kicked around a lot. And so, and that's changed from defining it as S-R-E-G-I-T, as we're calling it. And so you're starting to see these new formations of structure, where the goal is to do what you're doing at Wasim and WebAssembly, which is make things easier, faster, and workable across all platforms. That's the goal. Is there things shifting in your mind that you see out in the landscape that will kind of be new structure that makes things faster, more agile, cleaner? And what, is there things that go away? Because that's something that we're trying to look at and identify with. What do you guys think? I'm going to go way out on a limb here, because I can. Okay. That's it. You know, if we think about how the generative AI works, and particularly in large language models, right? You know, I can express something in my preferred language, English in my case, right? Ask the system a question. The system can do some work and return back something that ideally in the same language. Most of, not most of, all of the edifice we have built called software is about me learning a different language and being able to express to the computer in this kind of intermediary language that ideally both I and the computer understand, right? Well, what if maybe the biggest risk is, or the biggest change is that programming languages in general will go away for the average developer? The coding will be more like sitting there going, okay, so what I want is a shopping cart, and the shopping cart is going to have these properties, and when a user comes, they're going to have a button to click, and I'm going to talk to the computer and it will be building out a lot of these things. Actually, when you think about it, if we learn to articulate ourselves clearly in English, this is going to be a far more concise process to use than sitting there going, okay, do I need curly braces here, or is this, you know, did I miss a semi colon somewhere in there? And probably there will always be room for the kind of low level programming and things like that, but I actually, what would excite me is if we started to see cases where you could express in plain English or plain language of your choice, right? This is what I want to do, and really we're training humans to be better talkers and the system to be a better compiler. Yeah, I think that's a great limb to go out on because that highlights voice, which we all know, hey Siri, which is weak compared to some of the AI coming here. Well, yesterday's chatbot is not today, just seeing that in the format. Yeah, and I think what's interesting is, and the way you approached it is also it's a CX back, it's a customer experience back type of view, and I think that even over the last five years, different companies that I've worked with from a product perspective, working backwards from the customer and understanding that and describing it has been a big piece of it, and I think even for like the last 10 years, getting the engineers to be involved in those conversations, sometimes pushing them out of their comfort zone, but I think it's a different skill set and I think to your point, I think that's where I think you're right. I don't think it's a huge limb to go out on, but you can get kind of a framework built out maybe with AI to begin with, and then you have the people who may not be a socially inclined can go and tune that from there, and I think it's almost like having the business requirements written down in CX, in UX, almost. Yeah, and to your point then, these things are iterative, right? It'll take us a while to get there, we will have some definite false starts. And then when you think about it, the low code, no code movement, I'm not going to call it a false start, but that was one where we were trying to get a similar CX, but we didn't at that time, our toolbox lacked this one new key technology that we have that might be able to realize a lot of that vision, which was let's just make this more broadly available to the people who just need to describe a business process, or to the people who want to build a pet food tracking database, you know?  Don't you wish you were 25 again? Oh yeah. For so many reasons, but yeah, it's awesome.  I mean, so many goodness from a coding standpoint.  I think this is what we are looking at is, there's definitely going to be a rattling of the open source way of life, just by default, it's the tailwind. That's a great tailwind, it's not a headwind. So, you know, what has to lift? That's the big question we're asking, and the work you're doing with Woz and WebAssembly is, to me, I think a North Star for all systems, which is make stuff that works for developers across multiple platforms. Yep, yep. And API's already set up. Yeah. This platform engineering, that's why Rob and I are really kind of honing in on, you know, what is a platform? Yeah. It's not a cliche. It shouldn't be a marketing architecture. It should be a legit platform. Yeah. And have tools and apps that sit on top of it. Medellin's got 4,000 apps. Teams, wow. That's how many teams they have. Yeah. I mean, and when you start to look at it, it's how, if you have to go and actually change those and did, you know, there have to be enhanced or patched or done. And I think you brought it up earlier, and I think it's always been one of those, don't SRE me. Right. So that I've always worked with, or like just don't SRE me. I don't want to have to build and run and get woken up every day at three in the morning cause something goes bump in the middle of the night. And I think that's where kind of breaking things down into a platform, on a platform into smaller pieces makes a lot of sense.  But this technology is still blending with the technology that we don't want to be dismissive and say was yesterday's technology, right? What cloud and then what systems like Kubernetes and containerization and WebAssembly are bringing is this idea that we can distribute computing in new ways, right?  Now it's the first class you take when you walk in the door, right? And that's a hugely enabling technology for how we're going to be able to use the compute power a little more efficiently, waste a little bit less, accomplish a little bit more and that took a lot of design in there. Now we can drop on a new layer on top of this and, you know, the gateways are opening now and we're still kind of looking as the door starts to open and you've got an eye up against there going, okay, what does the world look like? But we know we've built a foundation for something new and it's going to be very exciting. And what you just said is really important because that distributed computing architecture is a system, it's systems thinking. That's why it's the last class in computer science because it's the capstone operating system, systems management class that humans up to. You learn nine, 10 languages going in, you're doing compiler design, writing a link or a loader. All that OS stuff, that's the pinnacle. Now it's entry level. Then you've got cloud scale. Okay, so you've got complexity in the systems thinking and a system that has consequences in collateral damage. You can't just unplug something without having some damage so you can understand all those dependencies and then you've got scale. So I think the combination of that and then now with AI data, data scaling. So data scaling and that's going to create all kinds of glue layer impacts. I think that's why I think the Kubernetes container thing is going to be boom because microservices is going to fill that up with machines. Machine data and machines have to be doing that, heavy lifting, hence the human and machine angle. So that's why I think AI is really, really going to be impactful in the world because you can't ignore it. It's the only answer to handle security. Yep, it may turn out that we built an edifice big enough that we need AI to be able to help us operate it. Otherwise it will just be too, too cognitively overwhelming for us. The large code model. Yeah, yeah. I'll see you in. It's called open source. Matt, great to have you on. As always, a pleasure to commentate, opinionate on what's happening. Put the puzzle together on theCUBE in real time. Really appreciate you coming on. Give a quick plug for the company that you're working on right now. I know you had a lot of press interviews, analyst meetings, what's going on in your world. Take a minute to give a good plug. So for me on technology, we're building the next wave of cloud computing. We believe WebAssembly is a key enabling technology, but this is all about the distributed computing, right? And this is all about building kind of a foundation where developers and maybe machines and not very long will write small serverless functions that will be able to very quickly deliver value right away. Very excited about the direction that all of this is going. Really excited to kind of embrace this future that we're stepping into right now. But I really just want that human solucinate two T-shirt. Yeah, and that's a great punchline. We're never hallucinating on theCUBE. We're always keeping it real. We're riffing, we're going out there, pushing the envelope. Rob, great to see you, thanks for coming on. Great session, guys. Great, great analyzing and putting it all together. theCUBE, okay, live here. Day three, wall-to-wall coverage. Again, intimate event through the pioneers are, the leaders and the new leaders are emerging projects are here at Open Source Summit. This foundation is theCUBE, breaking it to you. All live three days. We'll be right back after this short break.


Okay. Am I starting? All right. Hi, everyone. So my name's Sherri. I'm fine, and I am. I'm going to give you a picture of Africa. Africa is a initiative focused on increasing awareness of the Wikimedia movement among people of African diaspora and addressing multicultural and gender gaps on Wikipedia and other open source. So what this session is going to be is the Wikigolf check-in. On May 16, 2020, in the early stages of COVID-19 pandemic, quarantine and shutdowns left us disconnected from one another. We're still going through it, but in this early stage, the whole world was in some stage of some kind of shutdown or isolation by May 16. So what we did during that time was we began what is called the Global Wikicheckin, which was an opportunity for Wikipedians and others in the Wikimovement to check in with one another, leaving comments about the current times and what we're going through, as well as documenting what was happening in this first few months of the global pandemic. And it was also, as far as we know, the first 24-hour global editathon scanning the world from New Zealand to Philippines, all the Caribbean, the United States, etc. So this section is going to take a look back at that event and tell me. So you're going to see a few images during the pandemic. This one comes via author Disgut on Wikicomments. And it takes place in Cape Town, South Africa. Everyone has been told to stay home. That's the staging for it. And this is the product of those ideas of using Wikipedia as a connection tool via the checking idea. So this is what the Global Wikicheckin looks like right now. You can go on that and find it. After wiki, click check in and you'll find it. And it's a little different than, for example, something that you would see on Wikipedia, for example. Let's say you looked up the COVID-19 lockdowns and you would find an article about the lockdowns, maybe some photos in there about that time and continued information coming in about that. What makes this a time capsule of sorts is that it was for a short period of time to capture the sentiment during that time from people all over the world. So many of us can use Wikipedia for different things, for example. It's not just for articles. It's not just for images. It's literally a tool that you can use to document all kinds of things, including your thoughts, right? So a way of finding your perspective. So a way that this check-in works is that we ask people from wherever you're coming from on the planet to add images. As you can see below, there are some examples of images that were used from as far as Italy, the United States, the Caribbean, et cetera. Sweden I see down there. And you put that in this wiki time capsule, which is called the Global Wikicheckin. And what you do then is you would add what the world looks like for you right then and there, where your feet are on the ground and your world around you. So it doesn't necessarily mean that you would talk about necessarily what it's like dealing with having COVID-19, although that could be part of it. You're really talking about what the world looks like to you from your vantage point at that moment in time. And literally look around you and say, okay, this is what things look like for me. And then we invite you to leave a word or two about it. Another thing that was different about this is that you would find your time zone, right? You would look not only for your country, let's say, but you would look literally for the time zone where you're based. So we didn't base it on your nationality of origin, for example. We based it on literally where you were at the time. So for example, you could be Mexican and visiting Cairo or something like that. So you would talk then about what your world looked like in Cairo because that's where you basically work. So the idea for a 24-hour edit on, you can look at OpenStreetMaps and take a look at where we hit, what the kind of impact was on this project. So from this little image here, you can see we started from New Zealand all the way through the world. I think we touched basically every hemisphere and most time zones. And so in that, for me, as organizer, it was a success. So let's go back to the staging of things. So one of the main reasons behind this idea was not only did the COVID-19 lockdowns plunge us into a state of quarantine and so forth, but it also led to massive isolation in communities worldwide. And it also led to a shutdown of mechanisms and social interaction that are important for the overall psychological welfare of many people. So isolation can not only lead to your basic issues and inconveniences of not being able to do what you usually do, but it also can lead to the psychological harm that isolation for long periods of time can do. So for the Wikimedia community, for example, it also meant a halt to the activities that we did in-person conferences, meaning sort of like this one which we're now doing online at the time. Even that kind of interaction was also there as we tried to figure things out. So check-ins are not any idea, which is what this was. They have been used online to give friends and family an opportunity to connect with one another during natural disasters and other great season Facebook and other social media platforms. So this looked at Wikipedia as a tool against isolation during the COVID-19 lockdowns and an opportunity for checking within the community of as we restored connection and so forth. And so that's the beginning of it. All right, so I'm going to go to the mechanism of how this came about and how did we develop it. So this is a ridiculous statement that I've put on top. Just to illustrate, some of the processes you can use if you're trying to figure out a similar idea or if you just want to get started on something, whether it be a time capsule or 24 hours on or anything else. I think this process can be useful for anyone who's just trying to get started on a ridiculous idea. First, I think it's important that you have ridiculous ideas, that you try things that aren't necessarily have a mechanism for you to use. Then you have to believe in your ideas. Thirdly, I feel like you should try it out. Why not? Why give yourself a reason not to do something that you think maybe you can try and do? Fourthly, I think you should enjoy it. That improves your ability to keep going with that even in the case of obstacles and everything else. And of course, find like-minded collaborators. And with all else fails, I believe you should just go ahead and do it anyway. Because once you can do it, then you'll figure out if it's something that you can go forward with.   That's what we tell ourselves in our heads. Often it's said by others. But more importantly, if you say tw-


Once the correctly charged tRNA has been placed in the A site and has rotated into the peptidyl transferase center, peptide bond formation takes place. This reaction is catalyzed by RNA, specifically the 23S rRNA component of the large subunit of ribosome. Early evidence for this came from experiments in which it was shown that a large subunit that had been stripped off of its proteins was still able to carry out peptide bond formation. Early experiments were seen that large subunit whose proteins were removed, even then this large subunit is able to carry out peptide bond formation which means that no protein is participating in this reaction to catalyze this reaction. Proof that the peptidyl transferase is entirely composed of RNA has come from the high-resolution three-dimensional structure of the ribosome which reveals that no amino acid is situated closer than 18 angstrom from the active site. Most catalysis requires distances in the range of 1 to 3 angstrom, it is clear that the peptidyl transferase center is a ribozyme that is it is an enzyme composed of RNA. How does the 23S rRNA catalyze peptide bond formation? Means what is the mechanism of this catalysis? The exact mechanism remains to be determined but some answers to this question are beginning to emerge. First, base pairing between the 23S rRNA and the CCA ends of the tRNAs in the A and the P sites help to position the alpha amino group of the amino acid tRNA to attack the carbonyl group of the growing polypeptide attached to the peptidyl tRNA. These interactions are also likely to stabilize the amino acid tRNA after accommodation. Because close proximity of substrates is rarely sufficient to generate high levels of catalysis it is hypothesized that other elements of the ribosomal rRNA change the chemical environment of the peptidyl transferase active site. So, substrates close proximity may not be sufficient to get catalysis so this means that there are some other factors of the ribosomal rRNA which change this chemical environment and this change leads to the catalysis. For example, it has been proposed that nucleotides in the peptidyl transferase center accept a hydrogen from the alpha amino group of the amino acid tRNA making the associated nitrogen a strong nucleophile so this is a common mechanism used by many proteins and enzymes to stimulate nucleophilic attack of carbonyl groups.


Hi y'all, Liz here and this week we're talking about the ABCs of cleaning some of the basics. Now most of you already know all of this stuff and it's just a refresher, a quick refresher for some of the basics, the ABCs. So the one I want to talk about today is direction. What direction do you clean and like what does that even mean, right? Okay, so when we're talking about direction when it comes to cleaning, there's certain things that we all know. We know we're supposed to clean from side to side and we're supposed to clean from top to bottom. But there are some considerations in there, which side to which side, right side to left side, from the center out to the doors, from the doors into the center, what does that all mean? And top to bottom always, do we always clean top to bottom? Is there ever a time when we clean bottom to top? Because there is, right? All right, so we're going to talk direction, first things first, side to side. So we clean normally if you are right-handed, you are going to be cleaning from right to left and you should be starting a room at the entrance to the room. There's a few different reasons for this. If you start cleaning at the same point that you enter the room, if you stop for any reason and you tell somebody, listen, I had to leave the master bedroom, I got to the first night stand. Everybody knows exactly what you've cleaned up until that point. They know that you've cleaned.  So the reason for it is so that everybody's on board all the time with where you're going. That's one thing. The second reason is when you're cleaning right to left, your hand automatically flows this way without ever even having to move.  So this way, working right to left, if you're right-handed, is the smarter move. Also, if you're working left to right, if you're left-handed, left to right is the smart move. Many people get bad training in this area. If somebody's left-handed, they'll get trained to clean by a right-handed person. So they'll be trained right to left. It's similar to being trained as a left-handed person, being trained to right with your right hand or being trained to right in the exact same manner as a right-handed person. It won't work. If you're left-handed, you need to put your arm up so that you don't smear your writing and there are some things that you have to do that are different. Same thing if you're left-handed. So if you're left-handed and you're cleaning exactly the same way as somebody who's right-handed, it's not best for your body. It's not good for your body mechanic. So I'm going to suggest, I know you're going to hate this, but I'm going to suggest that you begin cleaning left to right and start cleaning in a way that is better for your body. All right, so left to right, we got handled, right, right. If you're right-handed, left is your left-handed. Start at the opening to the room, wherever you enter the room, and go all the way around until you exit the room. Now, if you do high-low dusting or if you do three passes, if you do one pass, it doesn't really matter. Always start at the same spot and end at the same spot. Okay, now top to bottom. Most of the time, we'll tell, we'll say that we clean top to bottom right to left, right? Everybody says that. It's a very, very common phrase. And 95, maybe 90, 95% of the time, it's true. You clean top to bottom. The reason for that is you want all of the sediment, dust, whatever the particles are that you're removing from up high to have a chance to fall down so that when you vacuum the floor, you have a chance to vacuum them up. But there are certain times when you don't clean top to bottom. A prime example is when you're dealing with liquid. So if you're in a shower, you don't clean top to bottom if you are spraying or squirting a liquid on. Now, if you're using a cloth or a sponge where we're not having any drips, then you can. But if you're going to be dealing with anything that has dripping capabilities, then you clean bottom to top. For those of you that are new, the people around you can tell you why, but I'm going to tell you here too. The reason why you clean bottom to top is if you clean from top to bottom on a wet area and you get any drips, you can get etching in those areas. It can sit on that area for too long. It can be hard to blend that, especially if you're dealing with any kind of hard water, discoloration. Let's say you have discoloration in your shower. Maybe you have an orange discoloration from a rust buildup or something like that. If you apply a chemical or any type of a solution that is going to reduce that color at the top and you get any kind of dripping, the amount of time that it's going to sit on is going to be far exceeded by just dripping than the amount of time that you're spreading here, spreading the liquid up above. By the time you get down to where the drip is all the way down to the bottom, it's been on there so much longer that it's hard to blend it without removing everything to that entire level of color removal. It depends on how much it is. Sometimes you can get to a place where you've actually etched the material that you're dripping on. So, showers, large areas where we're dealing with liquids, start at the bottom and work your way up. Okay, that's it. So we go side to side, hopefully right to left or left to right if you're left handed. Start at the opening to the room, top to bottom on dry areas, bottom to top on what areas and that's it, direction. Alright, question for today is what's the one area that you're like, dang, I always forget. What's the thing? For me, when I'm doing ceiling fans, you know what I always remember? Right after I finish dusting, I'm doing all of my cobwebbing and I finish my dusting and I'm like, oh poop, ceiling fan, worst time right after I've done all my dusting. So I have to wear a little note for myself if I'm going to do that. What's yours? Talk to you tomorrow. Bye.


What's up guys welcome to today's class super excited to have you guys here with me That's good That's what we're gonna go over today not necessarily the perfect haircut for fine hair But I want to talk about fine hair really break it down got a mannequin back here Danielle One of my stylist here at the salon colored it for me So it's really cool looking and I'm gonna show you guys some tricks on that on how to kind of go through fine hair And how to think about it. Let's pop over to the mannequin. I'll show you guys the color before we start cutting it Well, it's pretty cool. She did a great job melting different tones throughout it She used Paul Mitchell pop XG to color it really cool fantasy color you see all through there And we're going to cut so let's break down some fine hair thoughts Before we start cutting because what you want to do anytime you have a fine hair guest in the salon You want to assess where the hair starts to get weak because a lot of times if you look at the hair Kind of from this point down it doesn't look or this point up I guess you could say from this point up. It doesn't really look weak It's really from the neck down or the shoulder point down where this is a little bit weaker So that's what I would want to focus on with my client So I would look at and assess where the hair starts to get a little less dense a little weaker towards the ends And then that's where I want to base my hair cut in now I'm gonna do this dry today because I want to be able to see the density as I'm working in this section Everything's gonna be pretty simple as well. So we're gonna work through that first I'm gonna do the sectioning and then I'm gonna break it down over on the board So right here comb out the mannequin a little bit and what I want to look for is basically going from a session point Back to the occipital bone and I'm gonna draw a curved line from this point back to the occipital bone So right here comb the hair in the direction I want to take it and I draw a curved line back. It's like that I'll hold the rest of the hair in my hand turn it so you guys can see now We're gonna come across the occipital bone and Then I'm going to draw a line on the opposite side and meet Sometimes it's easier if you just want to kind of break this up and you want to clip the one side away If the layers are a little bit shorter, I'm not having really any issues here Working through it. This is really exposing some of that beautiful teal blue color. All right So now as I comb it up in the air I'm just looking for balance on both sides. So I want to make sure Both of these sides match up So now I'm going to twist it up and clip it away Slide that clip in now I'm going to go through and just assess the bottom kind of feel through it I'll look for those weak points. We're going to be cutting kind of a medium length haircut What I find with fine hair is that the longer it gets it's obviously going to get weaker towards the bottom This hair not only has been on the head quite a bit longer But fine hair tends to kind of break off as you're blow drying it different things. It's not as strong You're going to have more density in this area than you are in the ends because some of this hair is already just growing back From breaking through blow drying ironing all that stuff just kind of meeting it up with the hair that has broken off a little bit That's just going to give you more density throughout the cut Most likely your fine hair doesn't get to this point, right? So as it's growing some of it breaks now you got to kind of work and grow it out again Let's just kind of make it a rule that if you want a fuller looking hairstyle Number one is to get it to a length where your hair likes to stay dense. So look for that density I'm going to say this is about shoulder length is a good Length for somebody with fine hair or go shorter But going longer is just your hair is just not going to look as full You can definitely hit it with a wand give it some wave makes it feel a little bit fuller But in the end it's definitely going to always look weak at the bottom now that I have it sectioned away I'm actually going to hit it with an iron real quick I'm going to add a little bit of neuro protect to this bottom section And I'm going to iron over it just to smooth it out because I'm going to cut a nice baseline to begin with Is there a video tutorial for the color not yet? All right, so I'm just going to iron this nice and smooth here bottom section And if a client came in and obviously it's in the best interest to blow dry the shampoo blow dry do all that work Smooth out this bottom. You should do that. So just kind of assess what your client's hair is like Don't just start cutting it dry really blow it dry nice and smooth And then as you're working through it you'll have better results because obviously you'll have a nice smooth palette You're working on what kind of iron is that this is a palm Mitchell express iron Style plus I like this iron because it's nice and skinny So it's easy to work in tighter spots The better to cut wet or dry. So Faye, that's a great question I like cutting dry on fine hair sometimes So it's not an all the time rule sometimes especially on longer hair because I can see that density when the hair is wet It's harder to see how much density you're actually leaving on the head Sometimes it can be a little deceiving one way or the other So just making sure that I know exactly how thick the hair is going to feel when it's done But I like doing it straight so then when I go through it and cut it Obviously, um, I get a nice straight line to it. Then we can add a little bit of wave to it at the end All right, so now I've got the hair smoothed out and we're going to cut one length So let me go over to the board to show you guys something real quick So our thought process here is that we're we sectioned off this disconnection. That's what we're dealing with right now So what we're going to do with all of this hair underneath We're going to pull that hair straight down and cut it blunt not the best drawer But we're going to bring it straight down cut it blunt at the length that we want it What that's going to do is it's going to keep all of the density as much density as we have at that length And we're going to cut our line now The reason we want to do that is because we also want to add layers to this fine hair to create some movement But I don't want to take away and layer all of it So being able to keep almost from that parietal ridge that recession point down to the occipital bone All of that cutting at one length is going to keep it full and then we'll start layering the top I'm going to do all of that parallel to the floor just lift it straight up in the air and start point cutting into it And softening some of those layers So you can see here same thing all of this is going to be brought down cut blunt at that point here And then all the top is going to be brought straight up cut into kind of a square layer on the top of the head That's our that's our work through with this haircut. So first things first. We got to cut blunt I'm going to use a wider tooth comb. Uh, this is available on our shop shop fse I'm going to use a wider tooth comb because I'm cutting it dry and I don't want to hold too much tension on the hair I really just want to comb it down to control it and then let the hair just hang where it naturally wants to And I'm going to start cutting my line You can see how it's you can't see really anything from this point over But then when you get here you really start to see through the hair and even more at this point So I'm going to go a little bit below, but I want to cut my line right down here And this is where we'll have the fullest point in the hair.  So now we've got our length cut I'm going to go through and work the top section Like I said before all of this is going to kind of come straight up I'm going to let this down for now and you'll see it kind of come over everything Now you could continue to cut this hair blunt if you wanted But you'll see that that's hitting right where that density I was talking about so where it gets a little bit thinner So what I'm going to do I'm going to comb this into a couple sections. I'll comb it back find the parting They're going to wear comb it back here one of those days So here's the parting part right there and then I'm going to find what splits the front and back so right here Down to the hairline. We talk about this all the time. So there's that hairline This is kind of the hair that's going to sit in the back of the head. I'll clip the rest of this away I'm going to do the same thing On the opposite side over here find the front and the back down to the hairline All of this hair wants to fall into the back and all of this hair wants to fall into the side Clip that away now. We've got our back portion. So what I'm going to do is I'm going to take this I'm going to elevate it up So I'm going to stand on the left hand side of the head So left hand side of the head vertical section straight down the center back to bring this up now my guide I will see kind of from the bottom you can decide Do you want to cut at that guideline here? Or do you want to go a little bit past it? You go past it. It's going to push hair below the um the perimeter line That's okay You can always go in and point cut that or cut it blunt at the end And that's what I'm going to choose to do because I want to push a little extra weight to the bottom And I don't want extra short layers on the top. So here we go up like that The guideline falls out and now I'm going to go in and I'm going to point cut through the hair So now take a look At how full when you take away these pieces how full the back of this looks right here starts to kind of elevate out Uh, it's got that fullness to it. Um, and that's the same thing I want to do on both sides This side now I'm going to bring it up to the center guideline falls out Now what's happening when I pull this hair up into the center? It's over directing What happens when we over direct when we over direct it pushes weight away from where we're pulling it to So if I'm pulling it away, uh towards my body, it's going to push the most weight away from my body So right here bring this hair up cut your line And you can see how this starts to build a really nice kind of lob shape to it medium length haircut feel Now these little pieces are going beyond the perimeter that we knew was going to happen That's what we can go in and take off later.  This is going to take out very little weight.   Love it. Rachel. Thanks so much Everybody uh Colleen. Thank you Lisa, thank you very cool to see all of you guys in there. Thanks. Thanks for joining today now Super simple in the the other two sides. We're going to go through and I'm going to lift this up We've obviously got our length underneath.  They can help you create a nice little style So I'm going to come over here. I'm going to grab all of this hair I'm going to lift it up over her head and I can see the guideline start to fall out So right here, this is all the little hairs that we cut blunt at the bottom So when I start seeing that and I can see it kind of through here and see my guide from the rest I can go through lift it up and point cut my length across So just like this point cut my length across kind of connecting it to that back point again Not pulling in this perimeter because I want to keep that perimeter Nice and then there we go again. It's a nice length to it Now we're going to do the same thing on the opposite side Let your guest do some of the work have them tilt towards you just slightly that way because there's a chair Here that way you can comfortably get everything over if you want to lean over the chair and pull it up You can do that too. So here we go grab just a little bit of that hair as a guideline Bring it all up to me this point and point cut through now What's happening to the front pieces of this haircut these pieces here? They're going to be a little bit longer Why are they going to be a little bit longer because the forehead starts to move forward So there's a little bit more over direction of that piece because we're cutting everything straight up So all of this is being cut straight up and because it's being cut straight up You're going to get that little bit of extra length So now we've got a nice medium length haircut that has Of a really solid foundation. That's number one really solid foundation This cut which has a really solid foundation in the base area here But then the layers that just fall over top of it to have a ton of movement because of the point cutting So that's the key thing that I want you guys to think about as you go through these haircuts is Everything has to have a purpose has to have a reason of why it works hair cutting is not complicated But if you don't know what you're doing if you haven't been through these scenarios If you don't understand hair texture type density all that stuff Then you're not going to understand how simple it is It becomes simple because you learn and you learn how to kind of manipulate the situation So underneath here solid baseline over top of it broken line Now what I want to do is I want to go through here in this area right here And I want to kind of fine tune it just by bringing this hair down and cutting into with a point cut technique A little bit of that baseline of the haircut right here. You could see where some of that passes by Lily thinks one side's longer than the other probably that's okay We are going to work through that right now. We're working the perimeter of the cut Now what I want to do is I want to comb down wide teeth wide teeth through the hair And I'm just going to soften that line around the perimeter same thing here point cutting I don't want a blunt line now. I want it to be nice and soft got much more modern feel to it As we cut through so here these are the pieces Lily's talking about right here So this stuff we're all we're going to cut it all off It's the disconnection from the elevation that we did this side is a little bit I over directed it more and so that's really what it is. This is the weaker side too So both sides of the haircut are not exactly the same So like as you're working through a haircut if they part their hair on the side like this one She parts it over here to this side show you guys So she parts over to this side here So she's going to have a little bit different lengths Because one side has this much hair and the other side has you know this much hair So but I can see my guide right through there and that's what I'm aiming for So point cut this mannequin does not have thick hair. Uh, Andrea Just so you know, this is actually super thin not super thin I obviously have clients that have a little bit thinner hair than this But she doesn't have thick hair and if you saw it at the beginning, it's very very light density It looks full because of what we just did, but it does not it's not a full hair mannequin I actually the Erica mannequin that I use that has Burnett hair is much Thicker feeling and then some of the other ones have even thicker This one is the thinnest hair mannequin. You can see the scalp of her as you're working through So don't be don't be discouraged and these techniques will definitely make somebody with fine hair way fuller Also has a nice blowout from Danielle as well So you're seeing that some of that volume in there And I'm going to show you guys a couple other techniques that will make it look a little fuller So let me see where we're at. See if we have any questions. You think it looks so easy Now I got Paul Mitchell Pro Tools wand here.  Pop this thing on here It's got a kind of a this nozzle goes in a cone shape in a way So it starts what I like is it starts a little bit wider So when I put the hair into it, I get a little bit tighter wave towards the mid shaft But not super tight at the base The base I just want to create a little extra volume Which is going to give me uh, this is going to give me the volume and then this will give me a little extra twist And then the ends I don't actually even wrap around this and I'm also going to use my ergo diamond head brush This is available on our online store as well. Uh, shop fse Those of you guys that are og's in the chat, can you please write shop fse? Put the link in there so everybody can see it on all the different platforms I'd really appreciate that. Let's see here. I can pop it up as well But shop fse if you guys are looking for brushes scissors our new tri razor, uh, which is this tool here Not really using it today, but just give it a little shout out. Uh, this is our tri razor It's got a three tools in one cuts a hundred percent of the hair 25 and 50 percent all in one tool We're shipping that worldwide. So if you want to purchase it go to our online store Keep posting that in the chat for me guys. You guys are the best I just want to be a little organic with the way that I pull these pieces out And then I'm just going to softly bring it around the iron and I want to put it in kind of a Ribbon motion so not putting it all together. I'll show you guys what I mean So right there you could see how it kind of just lays in a nice ribbon pattern What I mean by don't just kind of clump it all together is take a section and wrap it kind of on top of itself Like this unless you're looking for tighter curls If you're just looking to add a little bit of wave to the hair in turn will create Some fullness to fine hair go through it just like that And uh wave it underneath here. I'll just give it a little bend at the base I have a booklet of all the items in our online store. Um, I do not have a booklet, but we have a website So you could just go to the website. I just redid it too. We got snowed in so spent the day Redoing our online store. It looks super cool. There's tons of videos on there And it's a little more interactive than it used to be Which is pretty cool Just working everything off of the face So you can buy this uh wand iron on paul mitchell's website for sure It's cool too because these uh, it's called unclipped express ion unclipped It's one of my favorite things because these I'm not gonna try to take this off right now because I'll probably burn myself But these oh, there we go. You can unlock it. Look at that. I'm probably not gonna be able to get back on Yeah, you can unlock it and lock it and you can get it comes with different attachments You can buy other ones. It's a bunch of tools in one which I always enjoy being able to change it up a little bit So just go to paulmitchell.com I'm not leaving the hair in it too long for one I don't want to create damage to you don't need to I'm just creating a soft kind of defined wave in the hair And we'll assess the rest of that in a second and see the spray a little bit mitchell worked up Uh, this is a great flexible hold air spray. Um, what I love about this hair spray Why it's one of my favorites is because it's dry So, um, you can kind of use quite a bit of it And it doesn't make the hair feel sticky, uh, which is another good thing for fine hair Because it makes the hair feel thicker and you can lay it overlay it Uh multiple times and it doesn't wade the hair down pieces around it too Sorry, just in front of you guys So number one, I just love the fullness of this haircut how it works How easy it is to do so you can see kind of the blunt edge of it How it really kind of works through allowing the fullness on the bottom But tons of movement throughout the rest So, you know, if somebody had even finer hair than this that is one thing that I think a lot of people are like, you know This mannequin, uh, they're not believing that it has super fine hair, uh, which is totally fine If you had finer hair than this if you believe that your guest has finer hair than this And what I would say is go through it and just don't elevate these layers as much So don't pull them straight up to the ceiling Pull them out like here and then build the weight off of that perimeter line And then you'd have a full feeling throughout here. You wouldn't have these shorter pieces within the cut So that would give it even more fullness as you, uh, kind of work through So I wouldn't blow dryer hair flat because then it wouldn't create as much volume in here So being able to go in and, uh, you know, just give it a little bit of a style with the wand iron Maybe blow dry it with a round brush and then just hit it with the wand iron a little bit to just Create that wave and the body in there and then that helps your shape expand Like thicker hair might kind of get this look if it has a tiny bit of wave too It might already have this look fine hair is going to lay flatter So then you need to do something to enhance that wave Um and going in with the products like I talked about lighter weight, um hair sprays like worked up Palmatial worked up is uh, you can go in and miss over the hair It doesn't sit heavy like some some other hair sprays finishing sprays They go in the hair wet, uh, and they get kind of clumpy worked up You can really just keep working through the hair and building more and more volume and body throughout it So I think the overlaying of products really helps build the body in uh in your fine hair as well What if the client wants to keep their hair length long, but their hair is weak Adele great question We kind of talked about this already though when you look at a client that has longer hair But it looks weak got to cut it unless they don't mind it looking weak That's the thing too like clients might like it weak looking So at that point you just you can just do what you can Don't layer it more because if you layer it more, uh, it's going to get even weaker Um, so what I would do with them is discuss the options Which is taking it shorter to that the point where they have the most density That's my opinion uh as a professional and then if they steer away from that opinion Then that's on them, but I'll let them know that my recommendation is to take it up If they don't want to take it up it's kind of up to them at that point But it's really important to to fill them with as much knowledge as you have with fine hair products styling Choices multiple different looks that they could do. Um, you know with this length of hair They could wear it kind of smoothed out if they wanted to but give them some products to plump it up Powdery products drier products Kind of stack them on there and then you know, then they have options and they see what the style can do And once you've given them that knowledge, then they might make a better choice if you're just like, oh, okay You don't want it long.  So really fun hanging out with you guys today. How to blast Uh, I can't wait till next tuesday. So remember these classes are always on tuesdays 12 p.m. Eastern standard time. We also have other classes coming up But uh next week, it'll definitely be on tuesday. So be on the lookout. Make sure you set that notification bell So if you're on youtube hit the reminder bell also on facebook you can hit a reminder as well So anytime I do anything on live, I post a video you guys will know Um, and you guys can follow along remember Do me a favor anytime you see me doing anything on the internet Just hit the share button and tag me in it so I can say thank you I appreciate you guys supporting everything that's happening here at freesline education If you want to get some tools you want to support the channel even more You can get combs clips brushes tools everything that we used On this video On our online store, you can also pick up a tri razor On there as well, which is you know, you're worldwide you want to purchase something from our store You can get the tri razor on there for $44.95 Three tools in one you can cut textured hair thick hair Skinny hair wet hair dry hair you do everything with it. It's a super fun tool to use check it out on shop fse And uh, it's pretty much it All right Thank you guys. I'll see you guys on the next video Thanks so much