Hi, this is George Kow, and today I want to talk a bit about pricing. You have probably seen pricing out there that is often in the 99s, 97, 49, 47. It's pretty mainstream by now. You go to the store, things are $1.99 or $9.99. They're rarely straightforward pricing that's $10 and $2. So a lot of service providers, even those who want to be honest and ethical in their practices, have taken those on because they think, well, that's normal, isn't it? So instead of charging $150, I'll charge $147. Instead of charging $2,000, I'll charge $1,997. So let me tell you why I don't do that myself and I would hope that you'll consider not doing it as well. What that is doing, there's a lot of mainstream marketing practices that are not ethical and transparent. There's a lot of manipulation going on that if you knew you were being manipulated, you wouldn't like it. If you knew your loved ones were being manipulated, you wouldn't like it. Psychological pricing, you might want to look that up on Wikipedia. It's the manipulation of consumers based on pricing. So 99s, 97s, 49s, and 47s are that.  They don't want you to think about your budget. They want to kind of short circuit your brain to not think about your budget, not think about whether this is a wise purchase, truly, and truly what you need, but they just want you to think, wow, what a great deal. It's $47, it's not $50, $45 rather than $50, 95 instead of $100. So I stopped doing that a couple years ago and yes, I am tricking fewer people as a result. Hopefully, I'm not tricking anybody now. And yes, fewer people will make impulse purchases of my services instead of in the past, where I in part thrived on impulse purchases.  You know, it's not $2,000, it's $1947, $1997. Okay, so know that it comes, that kind of pricing scheme comes from a background, a history of manipulation. And those of us who wish to be, to know that spiritual growth and values is more important than profits will hopefully make a decision. Take a stand to say, no, I'm not going to do that kind of pricing scheme. I'm going to be straightforward with people. I'm going to charge $200, $500, $450, $2,000 instead of those shady numbers. Okay, so that's the first thing I want to say. The second thing is a lot of times your customer doesn't know what they should be paying for your services. So there is such a thing as honest price education. So you can tell your client, okay, my services are typically somewhere between this range and that range and due to my experience in the market and due to my experience with this expertise or due to my certifications, accreditations, due to the results I'm able to get from my clients. This is why I charge this amount instead of the lowest amount. And there are people who charge higher than me. So basically when you honestly educate your client about your prices and why they are such, if such education is needed, if they ask you, if they don't ask you, they're fine to pay your prices, great. But if they ask, oh wow, it's expensive or how come you charge this much? Or then you educate them based on your position in the market and based on the value of your services. Okay, the kind of results you create for your clients and how worthwhile that is. So I hope this is an interesting and helpful discussion about price education, dishonest and honest. And until the next video, and I always open, I'm open to your questions and comments as well. So until the next video, I wish you well.


What's up you guys put down a welcome back to my channel for those of you who are new take a look around if you like what you see Go ahead and subscribe. Thank you guys so much for joining me today So I had a question about the various different accreditation Statuses of PA schools. So that is what this video is going to be about. So For the accreditation statuses you should go to ArcPA.org and that is where you will find all of the information on accreditation and review of you know PA schools and such that's our accrediting body. So here I'm going to go to ArcPA.org so that you all can see and I'm gonna share my screen with you so that you can also See exactly what I'm talking about. So it's ArcPA You can go on this and it will have a list of all of the various different PA schools So now there are different Things like I said, you can have Provisional you can have continuing and our accreditation. You can have probationary accreditation and in that I think there are like two different levels of being on probation So I'm gonna go through what those levels are and then again show you on my screen Exactly what they're talking about. So when you have a provisional accreditation, that just means you're really a new school, right? So you are Provisional no more than five years and in that five years you have to get reviewed three times I don't know if there's like a certain time specifically that you're gonna get reviewed every time like every 1.5 years or whatnot I think that varies from the school and how quickly you get the various different things that they're asking you to update or fix But you cannot be on probation from you cannot be on a provisional status for more than five years So this is kind of what all new schools like very new schools not developing programs But like the provisional like they've gone through the Arc accreditation Process and so they've been granted provisional status now This does not mean that you are going to get continuing status because there are some schools that can go on provisional And then would draw and they're accreditation process from arc and then kind of come back to it again So it's no guarantee that you're gonna have continued status But that is the first step in getting continuing status on the website There is a place where you can actually go see that let me see If I can find that for you all accreditation process And in this this is going to actually talk to you about All of give you a more detailed breakdown about all of what it takes to become accredited And then also it's going to talk to you about Everything that you Want to know as a PA student going into this in terms of like what the various different accreditation statuses mean So here when you go to the currently accredited programs, if you click on provisional then it will pop up to What I was talking about with what the various different Statuses mean as I said, this is usually granted to an initial like applicant school This is a newly program that's been developed and you have students You know coming in and you're getting granted this provisional status for No more than five years and you'll get reviewed every three years And so the thing with provisional status, let's say For whatever reason you do not get a like your full accreditation It's hard because you have to graduate from an accredited program And so that's why it's important to look at all of these various different statuses because You don't want the school that you're applying to to be a school that's losing their accreditation Because you're kind of out of luck at that point in time.  So it's important for you to look at the various different statuses The next status that we're going to talk about is probation, right? And I know in the video I was like, well, I only want schools that are continuing status I don't want anyone on probation. But I mean some people might not care about that But I know when I was applying to pay school I didn't want any when on probation because I knew that if they lost their accreditation Then I would not be able to graduate. I would not be able to sit for my boards You will the school will still make provisions for you to graduate, but you wouldn't be able to sit for your boards So you I think you would have to like transfer to another program or they try to like Negotiate something with another school to take some of their students, which who wants that hassle, right? But when you're on probation, it's a temporary status, right? So like something happened you did something wrong your school didn't meet some particular standard And so you've gotten probationary status However, in that probationary status, you can also have like an administrative Probation meaning that once the program was not compliant with the administrative requirements So a failure to pay fees or submit required reports So you can get on administrative probation for that If you don't fix those requirements in the timely fashion Then you're going to have like a focus visit and you're at risk of losing your accreditation And so that's what that means then the big daddy the one that you kind of really want all of your schools to have is Continuing accreditation Continuing accreditation is a status that remains in effect until the program closes or withdraws from the accreditation process Or until accreditation is withdrawn for failure to comply with the standards. So There are various different Like letters and sections in this so you can have a d next to the school Which indicates that the accreditation incorporates one or more Campus so I know like Arcadia has like three different campuses And it has like one in Del or two in Delaware and one in Philadelphia or it's two different campuses So that will have if they have accreditation they'll have accreditation for Their main campus and then their distance game and then their distant campus And then you have an f in there that indicates that The program may have a focus visit in Their next arc review and the focus visit is like, you know You're being called into the principal's office. So Like it's just something for you to be aware of because if they don't do what they Needed to do on their focus visit then again accreditation could be withdrawn or you know, they'll just get put on probation And then the hashtag indicates that the program was closed for a period of time Since being first accredited, you know, that could be for a number of reasons. Who knows like it doesn't always have to be something nefarious But um a program can close and then reopen and then go through their accreditation status and now they're accredited again So I just want to show you guys on this exactly What those different areas look like so Let me see so stanford university is provisional and it has that little asterisk next to next to it. Okay You see all of these continuing education continued Status and then again more provisional. There are 250 entries right now And you know that there are more than 282 schools. So not all schools have been accredited by arc So that's just something to be aware of so samuel merit university so this one says probation and It has an f next to it. And if you guys remember it's like pop quick What did I tell you those months? So it's on probation because of something that occurred At the school and then f because they're going to have a focus visit in the near future And so we can click on that Again, and it will take you to the two asterisk probation what that means which is If they still fail to comply with their accreditation requirements in a timely manner They may be scheduled for a focus visit So samuel merit is scheduled for a focus visit and a program on probation must provide Clear evidence of progress towards improving the program by the next arc pa review So that is what that means. All right. Um charl guard drew is provisional because it is a fairly new school I guess within the last five years. It's been In the process of accreditation and I said Hashtag, what does the hashtag mean? So the hashtag if you go back to that indicates that the program was closed for a period of time and then Is reopened. So maybe the program had a continued Accreditation it closed down and then it started back and now it's going through the process again Those are just things that you can be aware of and you can ask On your interview and I know that a lot of us are like, oh man, like this is the interview Like, I don't know if I should ask that like I'm really because you're just so desperate, right? You're so desperate to get into pa school. I remember that feeling like just being mad desperate to get into pa school I just want to get in and once I'm in then I know that I'm safe But no like that is not like I don't think that's the mentality We should always go in because if you are getting an interview that obviously means that the school wants you and I think that it's well within your right and You know, just kind of your Priority I fail to do so in terms of asking these hard questions like hey I see that your school is on probationary status through our pa What does that mean? These are questions that you can ask just to make sure that you make the best informed decision for you As a student or possible student of this program because if they lose accreditation and you're still completing the program Then what does that mean for you? So these are all of the things that you should take into consideration and definitely Look into when you're applying to the various different programs because it will help you make a better decision On how you should move forward as a pre pa in the future So thank you for asking that question. If you have any other questions, please leave them in the comment section below Also, please follow me on instagram at it on the pa like this video and I will talk to you guys next time


I have the honor of bringing to the stage a woman who has 30 years of impact investing, banking, working under her belt, working primarily with tribal nations. Those of us who have been studying the history of our people know that these are not new ideas, but they have new names. So this indigenous wisdom on well-being is what our next presenter, Valerie Redhorse Moll, is all about. You all can make some noise for her coming to the stage. Yes? She is a professor at Stanford University, teaching entrepreneurship and social impact. She is the co-founder of Redhorse Financial Group and Redhorse Productions.  So today, she's here and her new role is the executive director at the Investors Circle SVN, Making Social, Economic and Environmental Change. Please welcome Valerie Redhorse Moll to the SOCAP 2018 stage, y'all. Thank you so much. Thank you. Here you are. Thank you, Ashara. Thank you so much. I am really humbled and honored to be here because as she mentioned, this is a very brand new role for me. I am the brand new executive director of Investors Circle and Social Venture Network. And many of you know more about the history of the social impact space than I do. It's been a great learning curve for me and I'm just so honored to be here to be able to lead this session that is called 57 Years of Leading the Way. But I want to clarify that that 57 years is not linear years. That's combined years between Social Venture Network and Investors Circle. And so what happened for me, as Ashara mentioned, I just want to give you a little bit of history about how I come to be standing here. About two years ago, my husband and I followed our youngest daughter to Sanford and we moved from Southern California to Northern California. And as Ashara mentioned, we had been working with tribal nations around the country and what we saw in and around many reservations was some of the worst abject poverty within the US borders. And I was really hungry for sustainable long-term solutions to that poverty. And we would try to bring emergency care and what I would call band-aids to our people and we would bring food and programs and clothing. But I felt like we kept doing the same things year after year. We would weatherproof homes and put riffs on trailers. But I wanted to find something more. And when we moved to Northern California, I had the honor to meet a group of people that, like me, had this passion to make a difference for our future generations. And one thing led to another and I was asked to interview to be the executive director. The board and the staff saw fit to offer me the job and I couldn't be more excited about our bold vision moving forward from here. But what I want to do today is first back up. This entire gathering is so exciting for me to see but we all have to remember our roots. And so the social impact space started with some very enthusiastic pioneers and I want us to remember that journey. Most of you may have been there. Many of you may have been involved with Social Venture Network and Investors Circle in one way or another. But I think it's always a good exercise to take a look back. And so we're going to do that if you will bear with me. We're going to look back at the space we all find ourselves in now and kind of the early beginnings of that space. So I'm going to start and my friend Lauren in the back is going to help me with the video. We're going to start in the 1980s. And that really is when humanity started to realize that we were slowly killing ourselves. And big business was actually leading the way. So from the way we worked to the way we grew and harvested our food, the way we educated our children and waged war, the way our financial systems operated, extractive systems were in play all around us. And what they were leading to was exploitation, financial crisis, and a very negative environmental impact. And the world started to understand that if something wasn't done, we would slowly kill ourselves and our planet. So a very bright idea was born back then. The idea that what if business, not philanthropy, but what if business with a profit could actually be used as a force for good? What if business leaders came together and said that they would commit to impact and purpose as well as profit? The year was actually 1987 when Josh Mailman and Wayne Silby, our two original founders, wrote that original letter to a group of influential colleagues and friends and said, let's come together, let's convene and talk about this concept of business for good. And about 70 people came to talk about that. And that became Social Venture Network, one of the original nonprofit social impact organizations. And those people that came together committed to lead the way with business as a force for good. So over the years, Social Venture Network grew and its membership grew, but then they started to realize that there were lots and lots of specific initiatives that had to be focused upon. And so you can see that several other very important nonprofit organizations started to spin out of SVN, a sort of the parent organization. I'm gonna ask Lauren to stop the slide right there. And let's take a look at that. Most of these organizations are represented here this week at SOCAP. We have American Sustainable Business Council focused on advocacy, Bali focused on local ecosystems, Investor's Circle focused on the flow of early stage capital to impact companies, BSR focused on big business, Net Impact focused on education, Opportunity Collaboration I just returned from Mexico, focused on convening and the alleviation of poverty on a global basis, and B Corporation focused on certification and metrics. Again, very important work spinning out of the original Social Venture Network. So as we continue on in the work in the space, we realize that Social Venture Network as this sort of parent organization is a very important place for people to gather. And what started to happen is members became investors in one another's businesses, they became colleagues, mentors, coaches. And what was so exciting is the world finally started to see the outside world, not just the social impact space, that business could actually be purposeful and impactful and make a profit. And what you're going to see here, and I'm gonna ask Lauren to freeze on this for a second, these are some of the most historic companies that came through the ranks of SVN and really showed the world that you could have profit, purpose and profit. You know these companies, but let's just remember them. Calvert Investments, Ben and Jerry's, Eileen Fisher, seventh generation, Etsy, Kine, Birkenstock, Beneficial State Bank, Stonyfield Farms, The Body Shop, Clif Bar and New Resource Bank. Many of you know New Resource Bank, was recently purchased by Amalgamated Bank and Ben and Jerry's was purchased by Unilever and now is publicly traded and is a public stock on the stock exchange. So again, showing the world that we don't have to give up profit for purpose. So now I'm gonna take you to look at another entity, Investor Circle, one of those nonprofit organizations that spun out of the original social venture network. And Investor Circle spun out in the 90s with a focus on the flow and the facilitation of that early stage capital into impact companies, knowing that was the hardest capital to find. And so what Investor Circle did is they, it was originally a group of about 100 investors and now of course we've grown to be many, many more, but this group of investors came together and really pioneered what we now call impact investing. A lot of discussion this week about impact investing. So this was sort of the original pioneers of that concept. And through the years, what Investor Circle has really perfected is the safe place for pitching, for companies and entrepreneurs to come that lead with impact, for the investors to come and do due diligence together and reviews together. And one of the signature events over the years that Investor Circle is known for is the beyond the pitch. In fact, we have one coming up in about a week in New York. But what is so significant is that over the years, Investor Circle has facilitated about $220 million into over 330 early stage impact companies. And Lauren, if you would hold here for a minute, just like SVN, Investor Circle has its own sort of rock star companies where early stage capital was funded and then of course they grew. So we have Zipcar, Pigeonly, Honest Tea, United by Blue, Translope, Boston Heart Diagnostics. And again, showing the world that you do not have to give a profit when you have purpose and impact. So that's a little bit of the history, but now we find ourselves here and now at a tipping point where social impact, a lot of great work has been done by all the organizations, but now we're not this sort of side conversation, we're not a tagline, we're on the front of Barons, we're on the cover of Wall Street Journal. Every major corporation is talking about social impact. So we all realize we have so much work to be done. And what happened was in early 2018 in January, Investor Circle and Social Venture Network realized they would have more strength by coming together. So they reached a historic agreement and actually re-merged back into one entity. So Social Venture Network and Investor Circle are now one legal entity, believing in the power of collaboration and the power of teamwork. Thank you. You will see our mission that I think is also your mission. We wanna realize a global economy that is regenerative, just and prosperous for everyone, but everyone in this room wants that. So why am I up here? Why am I telling you this story? Is this just to look back so that we can smile and look at all the good work that we've done? Actually, it's a call to action. We have very bold strategic initiatives we've been working on. And as I've sat through some of the workshops today, I realize all of you have the same initiatives. We're working on entrepreneurial services, investor services, impact measuring, asset measuring, education for corporate services, digital present, how do we expand, how do we look at portfolio management as well as direct transactions? And what I realize is that we can achieve this if we work together. Yes, in the 90s, there was a need for those siloed focuses. We had to do some specific work and that work is still being done, but now there's a need to really move the needle and make an impact. I don't know if you sat through the, I think it was an 11 o'clock session and a man whose name I cannot pronounce really had an impact on a lot of us because he made it clear that if we are really going to make change, we have to look at systemic change. It's a big change that we have to make. And I agree with him, but what I think we need is we need to come together and do what we've been doing individually and do it as a team. So yes, in my introduction, she mentioned that I teach at Stanford, I have a daughter at Stanford, but I'm actually a graduate of UCLA and a very proud alum of UCLA. And I believe that UCLA produced the greatest athletic coach of all time in John Wooden. And you know what John Wooden's known for. One of his statements is the true secret and success to stardom is in the teamwork. And I believe in our team, but Investors Circle and Social Venture Network wants to work with everyone else in the space. We believe in collaboration. We don't want to be siloed anymore. And so my call to action today is to come reintroduce yourself if you've already been a member, reacquaint yourself with us, introduce yourself to me and our team. We have a lot of members in the audience here that are part of ICSBN and let's work together. In my community, we do have a philosophy that is the seven generations. We believe that everything we do today will be felt at least for seven generations by our children and their children. And I know every one of you in the room is committed to that. So if we really do want to make a difference, I invite you to come and work alongside us. Thank you so much.


Lady Gaga has proven a queen never loses her crown for she has just broken a major Spotify record with her latest album Dawn of Chromatica. During its opening day, Dawn of Chromatica earned a massive 7.6 million streams on Spotify. In doing so, the project has earned the biggest streaming debut for a remix album in Spotify history. The previous record holder was Dua Lipa's club feature Nostalgia. Dawn of Chromatica however now features several of the biggest names in the music such as Charlie XCX, Brie Runaway, Rina Swayama and Clarence Clarity. The album was produced by Gaga's faithful companion Blood Pop and reworks the original tracks that appeared on Chromatica. Find out about fresh news updates.


What's up everybody, Jason here for JacksonBeesCaseBricks.com 22-a-Do Painty Capstone Baseball just sold out. This is a 8 box, half case break, two random teams each, number one guys, it's a brand new release. All cards ship and everybody gets two random teams in the MLB, Gus. So it says 12 packs per box, 8 cards per pack. And then an average box break, you get two autographs, two memorabilia, other cards, 12 hobby exclusive base reds, two base golds, six hobby exclusive luxury sweet reds and one luxury sweet gold, and 12 inserts. So here's the dice roller, here's the customer names. Again, we're gonna double up your names now because it is two random teams per spot. And then of course, here are the teams there. So let's roll five and a three for eight times, good luck. One, two, three, four, five, six, seven and eighth and final time. There you go, there's eight, Michael, down to Michael. All right, eight times, five, three, one, two, three, four, five, six, seven, eight. Yankees down to the White Sox. So Michael with the Yankees, Stephen, B with the Braves, Chris, B with the Mariners. Dennis with the Red Sox, Michael with the Mets, Craig with the Cardinals, Dominic with the Giants, Chris with the Astros, Jeremy with the Phillies and with the Tigers, Michael Gallucci with the Pirates, Michael L with the Diamondbacks, Marlins, Scott with the Twins, Ed with the Padres, Zachary with the Orioles, Jeremy with the Rays, Dominic with the Dodgers, Zachary with the Brewers, Ed with the Rockies, Craig with the Reds, Ed with the Nationals, Michael with the A's, Dennis with the Royals, Scott with the Guardian, Stephen with the Angels, Jeremy with the Cubs, Blue Jays, and then Michael with the Rangers and White Sox. So, trade window is open, guys, while I go get the case if you guys want to trade. Raymond, every few minutes, Nightbaw drops our link that opens up this Google Doc. If you're in a specific football break and you see that it's sold out, it should be here. And if it isn't, it's just because I haven't gone through orders yet. So, there's no specific time slots. Whenever the break sells out, I go through orders, I put it on the schedule. So, this is all I have for now. I got about another, maybe 11 orders to go through and if other breaks sold out, I'll add it to the schedule after 6.20 Pacific Standard Time, of course, 9.20 Eastern. All right, let me go grab the case, guys. I'll be right back. I'm not sure, Mike. I assume that it's probably a product that was featured in Chronicles, like Capstones and stuff like Cornerstones. And we'll find out. I have actually seen anything today. I've been super busy all morning, so. All right, I'm assuming no trades then. Let's close it. All right, so the case is right here, guys. It's actually a very heavy case, actually. I did not expect it to be this heavy. It's like I'm picking up a Bowman case. Now, there's 16 boxes in here. So, we're gonna open up the case. Let me see how I'm gonna do this, because I was not expecting it to be this heavy. What we'll do is we'll go one, two, three for the left, four, five, six for the right side. Dice roll it, three. So, one, two, three, left side. So, these here will be for number two. I'm supposed to be here on this side. Just because we'll probably run out of one of these later. It's probably a similar design. We'll find out soon, though. I wouldn't doubt it if it looks like other products they've made in the past, or other competitor products, just like their version. It's like copying my homework, but don't make it obvious, you know? Okay, here we go. If this product is really good, then you can see it stick around. Although, I think Panini loses their baseball license, though. I think at the end of this year. I don't know how that's gonna work. I thought it was over in 2023. But it could be mistaken. Oh, you know what this looks like? This looks like Zenith. Zenith Football. You guys remember that? This looks exactly like Zenith, actually. Just a lot more base cards, though. They actually look kind of cool, though. It actually does. Yeah, I didn't take one glance at this, guys. Not even preview cards. Just whatever Nick has is the sell sheet. It's probably prone to getting a damage, a surface problem, I'd assume. Suzuki. So again, I think these reds and golds are like normal per box. So, I think a lot of these will end up being commons, which you're probably really gonna go for is like the relics and the autos. Peek, Matt Barnes, Bryce Harper's summits, Big Bang, kind of gives you a little bit of recon feel, too, for basketball. Julio Redd and Manuel Rodriguez, crown auto. Looks nice, though, I will say. Showtime, Bobby Whit Jr., Glen Auto, New Age, Siri, Déjà vu, Little Trog Griffey. We'll probably randomize these unless there's a lot of them, and if there's multiples, then we'll just distribute it out evenly. That's the case, but we'll figure that out later. Numbered there, Sean Manin. Numbered at 99. Velo. Insert. O'Neill Cruise. New Age, Blue Bob. Thai France, where I like. And Seth Beer. Who's drinking a beer right now, guys? Who's drinking a beer right now? Karlsburg summits, and New Age, Bobby Whit. All right, this one's gonna have a lot of hearts, actually. Okay, next one. All right, so there's a lot of inserts, and I'm assuming, like I said, a lot of those, most likely will be common ones, but of course, if you know this product, a lot better than I do, and notice that I pass up a rare insert, or like a case hit, please let me know. But everything will be shipping, so. And at least for the bigger names, I'll probably just be leaving at least. Two Autos, two Relics. Numbered at 99, Yoann Adon. First Autos, Stephen Quang. Cleveland. We're not a paper, are we, dude? Oh, I never clicked print. That is K.P. Crawford, Dual Relic, New Age. Bobby Whit, Crest. Manny Margot. Or Manuel Margot. Judge Big Bang. And Jake Lats. And it seems like the Crest is like a one per box type of deal. So, any of the bigger names like that, Crest, I'll Steve at least, too, as well. All right, next one. But yeah, Figure Cards Dog is probably the reason why they're all like 75 point cards, so another reason why it's kind of a little heavy on the heavier side. It's a nice product, though. Guess we just had to find out how loaded a case actually is, though. Yeah, it does. It definitely has a crusade look to it. So they kind of took bits and pieces of different products they have created, right? Like you said, Zenith, a little bit of Crown Royale, whooped up a new species. They're like Jurassic World, you know, how they're enhancing those velociraptors and T-Rexes. Next one, guys. Erin Ashby Rookie. Bubby Whits. The Lady. Connor Wong, 275. Ben Yen, New Age. Jazz Chisholm. Peek Otto, that looks really nice, actually. Duh, duh, duh, duh, duh, duh, duh, duh, duh. Wander Franco. Wander Franco. Connor Wong. Oh, did I pass a torque? I'm sorry. I mean, we probably didn't see it. I mean, I don't really have a sleeve where top load was, to be honest, so. I'm just gonna sleeve everything. If it gets top loaded, then it gets top loaded. If not, it's at least sleeved. New Age. Carlson. Booze. Bueller. And Rizzo Big Bang. This really reminds me of Recon Basketball. I was thinking, like, I should wanna look at a card behind it. Oh. Yeah, I guess.  I got out of here midnight, had to pack up some stuff, just removing two floors up in our apartment complex to a bigger unit, and I woke up at six. I only literally got, like, I think I went to sleep at two in the morning. Got, like, three hours of sleep and had to move stuff out. I even got some movers to help out some stuff, especially the heavy, heavy stuff that I can't do on my own. Sorry, I'm running on nothing right now. So I had to get a Venti Starbucks coffee. That game was boring yesterday, Chad. Honestly. I was actually gonna text you when Panix threw that interception. I'm like, who was he looking at? That first early interception? That game was boring, dude. Honestly. So boring. I was hoping it was gonna be a better game, but you guys ended up winning the red. I think you guys are up by, like, a touchdown or two. I tried to pay attention to the Oregon game the other day while I was breaking. Ended up being pretty exciting towards the end. Cool little comeback. Mitch Keller. Love the card. I just kind of hate how the sticker pops, but still a hit there for the Pittsburgh. Bobby Wittz. Kendall Graven. Matt Manning. Oh, so it ended up being like a touchdown win. Oh yeah, that doesn't matter. A bowl win is a bowl win. Bobby Witt Kress. Torque. Otto to 99. Excuse me. And MJ Melendez. Dude, great season, dude, right? That's what I'm saying. I think you're decent. All right, you two wanna see ya? See ya. Have you kept track, Chad? With Oregon and Washington winning, how many other Pac-12 teams have won their bowl games? Are we doing good in that sense? You see how they've played their bowl game already, right? That holiday of bowl though with Oregon was actually cool. I guess it's funny because they always used to play at a Colcom Stadium or whatever it was called now. But I forgot they demolished it, right? And then now they played at Peco Park. It looked really awesome though. Like it only had like I think 36,000 fans capacity, but first football game in Peco Park looked pretty awesome, actually. I'd like to hit up that bowl game like next time. I would have loved to have gone to the bowl game, but it just landed in the middle of the week where it's kind of hard to call off, especially when we kind of already set our schedule like months in advance, especially during the holidays. But that was actually pretty cool. It looked really nice. Although the feel didn't look good though for the players. It seemed like a lot of the grass was just getting chunked up. Who's got destroyed? Ah, no bueno. Dun, dun, dun, dun, dun, dun, dun, dun, dun. Yes, I do remember that one, actually. Who do you see L.A. play?  Mookie. Okay, well, I mean if USC can handle business, I guess the top three did well.  So one of the top dogs win, I mean that's right, Bobby Whit, Bobby Whit. Patch Auto, excuse me. Adam and a Royal. Peak Patch Autos. Akio Badoo for Detroit. Dun, dun, dun, dun, dun, dun, dun, mmm. Oh, you see L.A. Does Oregon play against Washington and Washington next year? I'd love to go to Oregon next year. Next season for sure, though. I already told my cousin that lives up there in Portland. I told him I'll go visit him and then we'll try to align it where I can go to a game in Eugene same weekend. Byron Buxton. And it looks like there is a lot of those deja vu's, so we'll just handle those out evenly. Oh yeah, you're right, we did play, you guys did play come over here, so yeah, it should be up there, nice. Nice. I know, right, let's go, man, I'm down. All right, three more to go, guys. So again, this product looks nice. It's just kind of, you know, trying to get used to it. It seems like I said, a lot of the same inserts over and over again. Seems like the Crest is a one per box type of deal. And like I said, I'm just thinking of the bigger rookies if I don't miss any for just like Wander, Torque, Bobby Whitton, Julio, any numbered cards or for autographs or other like solid product though. I don't actually don't know how much it is per box, but two autos and two relics, you do get four hits, so in the eight box half case, we're gonna dish out about 32. So on Otani, Trout do all on card auto, Pulse saving five star. I mean, I did pull that Harper Trout, but it was a redemption, that sucked. And then I Mike Trout patch autographed last night too. That's what I'm saying, yours was live, right? It was the one you saw. It must be Bryce Harper, he just put it inside. I think Mike Trout is hardly ever really a redemption. Peak, Alex Bragman for Houston. We have left off. It's a soup can you eat, it's nice. Christian Pasche to 99 for Oakland. Is that right Chad? Nice, let me know how the arena is actually. I'm sure cracking games would be fun.  Dude, those tickets are so expensive. I had a customer named Jordan that buys here often too, not as much though, but I'm still friends with them on Facebook. Jackson Coar, he was like on the way list for years, right, when they're cracking or a couple of years when they're cracking, or they finalize everything. And he ended up getting a pair of tickets or four seats. He goes like, bro, I can resell all these and make double my money. I was like, dude, that's crazy. Seattle's only really had the Western hockey league, right? W.H.O.L. for a long time, so I know there's a lot of hockey fans up there. I'm sure it'll be a fun atmosphere. Who do they play on Sunday? Let me know, Chad, we sell cracking complete set boxes right here at the store now. I've seen them the other day, they're like 10 bucks. What you're cracking on? Exactly, that's what I'm saying. Josh Donaldson, it's a 99. Ooh, Michael Taylor.  Like, the tickets were like $100 or something, like, you're right, but they're actually having a much better season this year. One of their top players at Rookie, they got last year the number two overall pick. What's his name? So I'm blanking right now. But he's having a really good season this year too. Yes, I think it's Boehner's, right? I'm looking at it right now. Maddie, Maddie Beeneers, I think it is, isn't it? He's having a pretty good season this year so far. And I think, like I said, he was the number two overall pick last year. No, yeah, he's good. And Islanders, New York Islanders. They're actually a pretty solid team too.  He's like last two draft classes, the goaltender. I'm not actually too entirely sure who's actually really on that team now. I just remember that the captain still has to be, what's his name? Why am I blanking on some of these names right now? Matthew Barzell is on there, that's right. It looks like the Alexander Ramonovs. They're Islanders-Lee, I think is the captain now for the last couple of seasons. Seems like they still have Barzell. Like I said, Islanders-Lee, the captain. They still got a lot of their draft picks, actually, Boulevier. Oh, Zach Parise is on the team. I didn't realize he was there. Sabashin Aho, that's not the Sabashin Aho that was on, that's another Sabashin Aho, actually. Strategy is put it in the back of the net, Chad. And prevent it from going into your own net. And hit, check. You walked yourself into that one. Now I have fun though, man, it should be cool. Let me know how it is. Semi-photos of when you're there, like of how it looks like center ice or whatever you're gonna sit. Kraken. All right, Peña, Trevor Story. Yeah, Sorokin's still the goaltender there. I think they also still have our long off, too. I think they have three goaltenders on the roster. Dylan Coleman. I know, right? Ready for a big weekend this weekend, Chad? You take your bangles? I have your bangles winning. A lot still to fight for, right? I mean, they're trying to lock up number one with a couple of the teams. Kind of like the Eagles. Eli Morgan for Cleveland. Showtime. Yeah, I mean, it could go either way, obviously. Both teams are great, but I think Bangles should win, though. I'm a little nervous, still, for my Eagles game because I don't know if they're gonna, I don't think they should play Jalen Hertz, but I don't think they are anyways, but it's kind of like one of those games where the Saints, obviously, are very desperate because they have a chance at a playoff spot. And I think as long as the Eagles don't turn over the ball, it should be the Saints, but I mean, look at those four turnovers last week is what happened. Still only matched those by six, but that was the problem, those turnovers. Bro, I lost to Nick in semi-finals last week. Look how much I lost by. We both had horrible weeks. I had Jalen Hertz out and Nick, obviously, you know, I would have done the same thing, but he took Garner Mintry from me and didn't even play him. Look how much we lost. Look how much I lost by. Check this out. Look how much I lost by. Look how much I lost by.  Sad times, bro. Sad times. The reason why he won is because he got, parish count, he got 3.9 points to beat me on Monday night. We both had bad weeks though. Like he had a lot of players injured too. So it was very fair, very even, but he played Geno Smith instead of Garner Mintry, which if I would have played Garner Mintry, I would have won. If he would have played Garner Mintry, he would have won easily, you know? Michael Taylor. But yeah, now I'm fighting for third place now. Sad times. Yeah, PPR, uh-huh. He had two catches for like 30 something yards, 20 to one yards, whatever. So he basically got like four points and he beat me like that. Muncie, it was pretty sad. But like I said, the way we matched up, it was just competitive like that. But either way, we both would have got blown out because the other winners, one in four, they both had 187 and 157. So if we would have played one of those guys, we both would have lost. But the way it matched up with us, it was kind of fair because of all the injuries. So yeah, it was a little brutal, but whatever. I had a much better season than my projected. I was projected to come in like, I think like 12th place out of 14.  I did better than what I was supposed to. But the Jalen Hertz injury really messed me up because that was like my golden player like throughout the season. I was getting like 30 points a game from Jalen Hertz. It's the last box here. I think Jalen Hertz has played himself in 10 MVP candidate and one of the top candidates, but I don't think he's gonna win it, honestly. I mean, honestly, if Justin Jefferson went out and broke that Calvin Johnson record, I mean, I know it's a very quarterback-wise MVP, but I'd give it to Justin Jefferson, obviously. He's had an amazing season. But I don't know. I'd be happy if it's Jalen Hertz, but I don't know. I don't think they're gonna give it to him anyways. But yeah, I mean, Burroughs in the discussion now. You know, the way they've been playing, Josh Jalen's always been there. You know, Paddy Mahomes is obviously still doing amazing things. Paddy Mahomes, though, is kind of like on that level of like Jordan. Not to say he is Jordan, but you know, like, he's gonna put up stats and stuff like that every single year. And it's gonna be kind of hard to always give it to him. Right? Like, but he's gonna be in the discussion for every P like every season as long as he's healthy. Yeah, well, see, that's the thing. Justin Jefferson, I think, would have to break it. If he were to break it this week, I think they should give it to him. But he would have to have an amazing season, obviously. But yeah, that was the one thing too. Like A.J. Browner has an opportunity this week. I think he's only like a hundred yards away of breaking Mike Quick's record for, or Mike Quick or, or sorry, Harold Carmichael's like over like 1500 yards in a season for the Eagles. So he would have to break it this week.  So, which is very doable. On the old Cruiser 25. But that's what I'm saying, right? Like my home has all the stats in the, yeah, it's very amazing stats too. So that's what I'm saying. You can easily give it to him, but I feel like you can always easily give it to him, honestly. The way he's been playing the last, or I mean, I started his career, I guess. Whoa, Julio, look at that. That's like an optic. We'll take that. Seattle Mariners. I don't know who has the Mariners. Chris B. Butchholz. That's pretty sweet. I was not expecting that. I don't know how that was even in here. Is that a typo? Or is it in the checklist? And Colton Walker. Is that just an extra auger? Chris and Yellich. Who's his backers, I guess? Jose Ciri. Oh, I thought that guy had like no face. Bobby Witt. Yeah, that was the one thing. And I get it's valid, right? Most valuable player has to be like, if he's not playing, your team doesn't win, right? And Garner Mensch is not a scrub. I mean, he can play in the NFL. He was a starter at one point, right? But I just think that the Eagles ultimately probably lost because he wasn't playing. You know what I mean? Like, yes, Eagles still had an opportunity to win the game, still shockingly known amazingly against a good team like the Cowboys. All right, so Colton Walker, Morgan, Coleman, Badu, Pache, Kolar, Arroyo, Melendez, Wong, Jazz Chisholm, Otto, Lotz, Juan, Manuel Rodriguez, Seth Beer, Julio, Jose Ciri, Relic, and then of course we have a lot of these penny-steep top loader cards, including some Relics in here too. So I appreciate you guys. Capstone Baseball looks pretty nice. A little mixture of a couple of products from Panini. But again, the second half should be in the store. If it hasn't been posted already, I'll post it right now, jazbyzcasebrakes.com.


All right, welcome to this other episode of the Ovenshift Coffee Break. Good morning, everyone. I hope you have your good shot of coffee together with you. And today we will do another episode of the Ovenshift Coffee Break. We may have the wrong title on Twitch and YouTube, but it's fine. Today we're gonna fix it. Today we're gonna talk about the clown native inner and outer loop together with all our guests. So I leave the word to Jafar to present everyone. Yes, good morning, everyone. And thanks again for joining us to this Ovenshift Coffee Break session. So first of all, let's have a sip. So my name is Jafar and I work in the Ovenshift Tech Marketing team. So today we will be joined by our esteemed guests, Alex Groom, Carlos Vincens and Madoko Libali to talk about a lot of interesting features and patterns for developers to work on Kubernetes and OpenShift. So without further ado, I'll let you guys introduce yourselves. So let's start with Alex. Hi, my name is Alex Groom. I'm based in the UK and actually most of the team that we've got here, we're all a part of the Ovenshift specialist or a solution architect team. We're all working in the sort of top of the OpenShift stack where developers sit, where we're using OpenShift to build things to create applications. I myself, I've been a Red Hat for about three years now but I've been in the computer industry way, way longer than that. So, and here we are today talking about developer stuff, particularly the inner and outer developer loop and tools and how to start building your applications. All right, thanks. Carlos. Hi, basically, I did exactly the same as Alex. The only, maybe the only difference is that I do this from Spain, Madrid. And well, I think that's all basically. Okay, cool. And my fellow countrymate Madu. Yes, hello everyone. So my name is Madoko Libali. I'm a developer specialist solution architect. So I think, yes, Alex, you did the great introduction about the team. So same team from Alex. So really happy to be here and I'm doing that based in France. Okay, cool. So thanks. Thank you very much guys for joining us and everyone who's watching. Natalie, Natalie is our famous host. So he doesn't need further introduction. So Alex, you spoke about inner and outer loops, correct? So I do a little bit of guitar and I play with loops, but I haven't heard of those inner or outer loops. Can any one of you guys tell us a bit more what that means and what we will be talking about? Okay, I guess I can start with this. I mean, we talk about loops here really as developers, strange enough, spend a lot of their time doing the same thing over and over again as they slowly build out an application. They'll, for example, the inner loop, they'll write a bit of code. They'll test that bit of code locally when they're happy with it and they're satisfied that it's working functionally. They will maybe add a bit more and then go around that loop again, building stuff, debugging it, writing a bit more code. So they are continually working in a loop. Okay, the thing they're building is changing each time, but they're doing much and much the same task.  And that's typically how we think of the inner loop. It's that really tight circle of work the developer's doing. And if that loop isn't very tight and efficient, then the developer can spend an awful lot of time waiting around for their systems to compile, build, set up, install, whatever it happens to be, when it's actually more productive if they're actually thinking about problems, writing code, whatever it happens to be. So the longer a developer has to wait to test the thing that they've just thought of, the code they've just written, I'll give you the less efficient they get. So it's really important to have a nice efficient inner loop. So they develop themselves a really efficient. So that's kind of the inner loop. Maybe one of my other colleagues will take on the outer loop perhaps. Yes, sure. Thanks, Alex. Yes, I can only say thank you, Alex. So this is what we call the inner loop.  So after that, so we enter into the outer loop and the outer loop is mainly defined by all the automation and all the process.  So development, the test environment, your QA, the staging environment until the production environment. Basically, so the main difference between outer loop and inner loop, it's on the outer loop, the developer don't have let's say less control about this process because it's automated to be able to have a consistent way to deploy and run an application. And the inner loop, it's where let's say the developers can really do whatever they want to have all the control about the environment, what they're going to build and so on. Okay, thank you very much, Madu. So those concepts of inner and outer loops have been of course existing for a while and the developers have been used to working with the run times directly running on their computers and such things. But what I believe you are going to show us today in which is a bit more innovative is how we can leverage containers and Kubernetes and OpenShift in order to further improve that inner loop and outer loop, is that correct? So transitioning from deploying traditional stacks into using a container platform as your development platform and not just as a CAS or a runtime platform. Exactly, I think Alex introduced this situation. So what you want as a developer is change the code, see results, change the code and see results. And when you try to do this with Kubernetes, then you have a problem because you need to wait until everything is deployed, right? Also, I think the idea is just to find how to reduce the amount of time you need to see results. So, and there are several ways to do this. Okay, so I believe you have cooked for us some nice demos and presentations. So we like this to be very live and hands on sessions or discussions. So who wants to go ahead and show us some nice stuff or demos about these? Maybe we start with the inner loop and then we go further. Wait, whatever you guys wanted to present, go ahead and the floor is yours. Okay, then I think I'm gonna start. Let me show you my screen. You should be seeing all this nice stuff. You see nothing, you just tell me, okay? We can see your screen that's coming up. Here we go, perfect, perfect. Okay, so this is a Spring Boot application. I have deployed this application before we started with the session. It's a very simple application where you can just basically see rows coming from another database. So database is a database that I'm sharing across the cluster. You need to think about this as an external protocol database if you want, okay? Then what I'm gonna do is using telepresence. Telepresence is, well, I think I'm gonna explain that later. The magic, I want you to see the magic and then I can explain the trick. Don't tell us the tricks. We just want to see the magic. Exactly, just the magic for now. So let me do this. So what if I do something such as creating a VPN, something like a VPN from my laptop and I deploy the code in my laptop. I use my laptop to run the Java code and swap this deployment with a proxy. Basically that's what I'm gonna do. When you do this, you need some requirements in the backend because you need some permission so that you can deploy a specific proxy. So it's not something that you can do if you're not clustered as me, I mean, it's very best. Yeah, it's worth reminding people at this time, our definition between inner and outer loop is that code commit. And as applications have gotten more complicated, we're discovering that actually open shift is actually becoming part of the inner loop. The original assumption might have been, oh, yes, we touch open shift as part of the outer loop when we're getting into deployments, but applications become more complicated and complex. And actually our application has to live in a world that some of the parts components may be running in open shift already like a database or you're a part of a set of microservices. Half of the microservices already exist in open shift and the piece you're working in is actually on your code bench. And we end up having to integrate or spend our time integrating with the code we're writing and open shift itself. And then later on, we will then actually commit the code and that will close the inner loop, but we still need to be as efficient as possible. Exactly. So yeah, go ahead, Daniel Carlos. No, no, I was just about to say that it's true. So if, for instance, you want to create just this very simple microservice, it's not connected to nothing. You don't need this. So as Alex was suggesting, maybe there are external services. I think that you can outreach from your laptop. But those things are reachable from the cluster. So this is basically the situation when maybe telepresences is something that could help you with the inner loop. So now what I have is there's a proxy here and now I can start doing things like this. So I have an Oracle database. What if I try to reach the database? So the database is reachable. So if I go to this nice SQL, nice, I mean, it's all fashion application, but it's very useful when you try to do these things. So now I test and you see that I can reach the database. So I can start talking to the database directly. And that's something that is not really deployed in Kubernetes, it's an external database. I'm using this external database with a service of type external name, okay? So yeah, you are accessing the external database through a service which is exposed within Kubernetes networking, right? Exactly. I'm doing all this through this proxy. Okay. So now if I deploy the application locally, I mean, if I run it, not deploy it, if I run it, this is a very simple thing. The only thing you need to pay attention is that I'm providing some environment variables because I'm running the application directly in my laptop. So it's not a Kubernetes deployment. So there are no environment variables injected by default. So I'm putting all those environment variables before I run the Java code in my machine and hopefully it will start up and we can run the application locally by talking to the database, which is deployed in Kubernetes or through Kubernetes. So just be with this kind of lazy now. It's about, okay, there we go. So now this Springboard run is connected to the database, hopefully. So before I try to do anything, I should check that localhost is working. It's working and it's talking to exactly the same database. And I know this because if I run this URL, this is an external URL. This is the same external URL.  It's normal. It's the normal stuff we do. So if I change something here, let's go to the index. Let's put something here like, hello, for instance, I saved this and I go to localhost and you see that hello is here. So changing is immediate, right? Something that you can do very easy. So the inner loop is working, although the service, the backend service database is really far away. Yeah. So you don't have to rebuild an image or store that in container. Exactly. Exactly. And in fact, if you change the code, so let's do this first. And I have this from local. I'm gonna save it from Twitch. Okay. I save this and I go here. It's reloading, right? Can you increase a little bit of font Carlos? Yeah, sure. It's more visible. My bad. My bad. This is, it's readable now. Yes. Yeah, it's better. Thanks. Okay, perfect. So now if I do exactly the same, you see from Twitch, but the services I'm talking to from my Java code are in Kubernetes, okay? Okay. If I go here and I use this URL, should it work? Because you see that deployment has been swapped. So this deployment has been, has been scaled down to zero. I'm using the proxy. So the Java code is in my machine. But this URL is, it's an ingress. It's a route to open ship, right? Should it work? Well, yeah, it works. So that's basically the magic. I think this covers basically the inner loop when you're using Kubernetes, okay? Maybe there are other ways to do this. But I think this is a pretty nice way to do this. So now it can be stuck okay. So it's certainly a nice way to get services that are too big to run locally. Imagine that database, you've got about three entries in that database. Imagine if you had 30,000 entries or maybe 3 million entries, then it's not something you would want to bring down to your laptop and run. You absolutely want to remote it and connect to it in an easy way. So we're ready. And so also guys, what you are saying is that with this type of setup, we are able to share environments. So we don't have to duplicate them for every new developer or every new project. So we have remote shared environments that benefit from all the power and the resources of the cluster. Which is basically sort of unlimited compared to what you can have on your laptop. And you are also compliant to all the security constraints if you have private networks and confidential data that you cannot access directly through your connection through your laptop. It's all going through the Kubernetes networking and OpenShift networking. Thus, putting you almost as close as possible to a target environment. So you don't have that notion of, oh, it used to work on my laptop, but it doesn't work now that I am in integration environment or in preprod environment or stuff like that. Is that correct? And that's pretty important because the complexity of deployment, we can now actually practice deployment while we're developing. And that's actually very important because it means the developer is much more aware of what the final state is going to look like. And the sooner you expose the developer to the constraints or the benefits, perhaps of that final deployment, the better it is because their code would inevitably be tested and will work better in that final scenario because it's what they've been using up until that point. But the key thing here is if you're going to get developers to use a deployment system, it has to be easy to use and fast to use. If it starts delaying them or slowing them down significantly in that inner loop that we want to be as efficient as possible, then they're going to reject it and they're just going to move back doing everything locally on their own workbench because it's the fastest way to write code. So it's always a balance with developers whether they do stuff locally or whether they do stuff remotely. And OpenShift brings a number of decisions to be made actually because as said, as your application gets more and more complicated, more and more microservices involved, it actually becomes harder and harder to run this thing locally, reliably when actually the reliable way to run it is in an OpenShift cluster because that's someone's already done the work to define how to deploy it and the relationship between those services. And you have to end up duplicating that if you're going to do all that locally, which is inherently going to introduce bugs, issues that you have to debug and distracting you away from writing your code. So getting people to use OpenShift as part of their inner loop can be very productive. Okay, thank you very much Carlos and everyone, the very interesting ways of improving the developer experience and inner loop while still leveraging all the power of the OpenShift remote platform in your situation. Okay, thanks. So anything else you wanted to show us guys? So is this the only way to do inner loop? Did you have other treats for us regarding this topic? Cause I've heard about several other ways we can do similar things. I've got a demo to show you. Let me share my screen and I'll show you. Today is like, you know, the last three hours we have this three singer, this is a super cool demo. So it's a super session. Really glad to have you all here. So let's go to these other fantastic demo. Thank you very much. Okay, so hopefully what you can see now is, it's basically an idea. This happens to be code-ready workspaces. I've just happened to use that because it was easy. I can put everything in a browser for this particular demo today. But what I'm trying to demonstrate here is develop a busy inner loop. They're writing code, they're testing code. They're building a very simple rest microservice. Alex, sorry to interrupt you. Can you explain what this is? Cause I see that you have almost a development environment that you are in Chrome. Can you tell us a bit more about this? What this environment is, which if you imagine it, below this Chrome tab is our code-ready workspaces development environment. This is something that's actually running in OpenShift. We use it a lot for demos. It is essentially like a VS code environment, not very similar to what Carlos was showing us shortly, recently, except it runs in the browser. Your actual workspace is actually running in OpenShift. So your code and all your builds and all your storage is running in the OpenShift cluster. And all the browser is doing is projecting the front end. It's just showing you the graphics and the code that's going on. What this means is that all the code is stored remotely. There's nothing local on my laptop. So it's actually a very secure way of writing code, but that's not really the issue we're trying to talk about today. It's just another way of writing code and deploying it, et cetera. And even in code-ready workspaces, there's still the concept of local as in running stuff within the development environment and running stuff remotely or in the OpenShift environment. So yes, for the purpose of this demo, it's just a text editor or a Java development environment. And what we have today in this particular piece is this is a microservice that sits among many others. It's very simple. It's got a very simple REST API and it's got a very simple object which it's going to read out of the database. And due to a lot of clever caucus annotations, I really don't actually need to write a lot of code here but I still need to test it locally. And being caucus, one of the features that caucus offers us for that developer loop is a very fast way to develop code, that sort of write code, make a change, test it, debug it is very, very fast in caucus because what we've tried to do is eliminate the long pauses when you had to get Maven to build a Java application, build a Java file. That use actually takes minutes. Whereas with caucus, once the thing is up and running, we can actually make live code changes. And what I'm going to show you here is that working here locally. So if I refresh my browser, just wait for it to wait for the app to start. So can you put the screen a little bit bigger because it's overlapping with our video previews? Move that over there, just a little bit, yeah. Okay, so what I've got here is to test the microservice is got a very simple front end. So I can go in here and test it. And this makes one API call. It's looking at this item, returning this value 35. So that's all very simple. If I want to make a code change, I can show you how to do that quite easily. So if I go in and tweak the quantity class so it returns maybe a hundred times the same values, I make the code change, I can refresh the tester and what it's doing in the background is reloading that code, recompiling it, rebuilding it in a very small number of seconds. And I can immediately test it. And strangely enough, I've hit the wrong one which is set quantity. I need to do the get quantity one. That's why it has to be changed. Let's try that again, do the same thing. So again, and what we're seeing here is why we built this is because so you made the wrong change, you want to test it again, it takes just a... Literally seconds. You can imagine if it takes five minutes to go off and do that Maven build again, I would be either drinking a lot of coffee or tearing out what little hair I've got left, but I can make a code change and within two or three seconds, I get the response back. So by changing the quantity to times a hundred, I'm now getting 3,500 back as a result. What I will do is I'll... Yeah, we can see it on the stream. Can you just put it a little bit on the left? So we can indeed... Or maybe this is a public URL, right? So, okay, cool, yeah. So now we've seen that you have 3,500. Yeah. Actually, we can share this, no? We can share it... Yes, I think this is a public route. But let's not bother with that, but maybe... It's not... This one isn't particularly interesting, but what I wanted to show you next is... This is all happening locally, which is all very well and good, but this is a microservice. It actually sits within a group of other microservices. And what I've done earlier, because it takes a moment or two, is I've gone over to OpenShift and I've actually deployed this complex series of microservices where I've got a front-end, some orchestration, another spring route happen. This is my application that I've been working on, this one here, and it's using a database in my OpenShift environment. Now, what I want to do is test it and develop my code while it's live in my OpenShift cluster. So that's the next thing I want to show you. Now, what I have to do to... Yes, so you are making changes to a Dev environment, correct? It's a Dev environment, yes, but I want to make changes to the version that's running in the OpenShift cluster because I want to test it in its real environment. In situ, it's using a database, it's working alongside other microservices. So I'd like to test it and make code changes while it's in its proper place, not just running on my workbench, which is what I was doing previously, which is perhaps a bit artificial. So I want to try and do this for real. So what I have to do is you've seen the dynamic aspect that Corkus has when it's running in the IDE, but we can split those two things apart and actually run a piece in OpenShift that will listen to changes and detect those changes in the IDE and we will send those changes across to the OpenShift cluster and update the running version in OpenShift. And to do that, I need to run a slightly different build locally. So if you just let me find that and let this start up, but we should be able to do the same thing. What my IDE is now going to do once it's done this build, it will be connecting up to the OpenShift cluster and as I make code changes, they'll get sent across a HTTP link into that running application and update it exactly as we were doing locally, except we're now doing it across a network link. Now, clearly this is not something you do in production because there's a bit of a security aspect to this, but for a developer it's fantastic because I can make code changes and within seconds, have it updated in the cluster environment, which is something that was practically talked about. If you have to go through the full aspect of building a container or building a JAR file, then building a container and deploying it, that can actually take maybe two or three minutes. And what I should be able to do is make changes maybe in two or three seconds here. So let's have a look, see what's going on. This is what my app looks like, but let's just in case there's any doubt or so, let's start from the beginning here and start from my OpenShift cluster and bring up my app. Have you noticed that all these quantities are now about 35 or 3500 is now actually being displayed in the web UI as a stock quantity as part of this web interface. So these 3500s, 1200s, these are all because of that 100 multiplier that I've added, which is clearly wrong, I don't want that anymore. So if I go back to my code, I can take that out. Now go back to my OpenShift application that's running there, refresh that. This takes a little bit longer, maybe five or six seconds to actually refresh because it has a little bit more work to do. And here we see, let me make this a little bit bigger for you, these numbers are now 35, 12, 45, et cetera, which is the correct number. So this is very good. So what I've managed to do is I managed to make a code change. In fact, you can tell me here, it's a little bit small, but it says 4.793 seconds, it's taken to hot replace the code change that I've made. And I can do it again. I mean, yeah, let's face it, this is not a... So everything, I mean, this inventory service is deployed on OpenShift as a container and you didn't even have to rebuild and redeploy the image. It's basically directly replacing the content that is running inside the development container within the OpenShift environment. That's not correct. That's absolutely it. As I make a code change and then refresh the browser, it detects that code change, repackages that code change, sends it across to OpenShift and puts it into that container where it's running. And it doesn't need to build a container or restart the container. So here we are, 350. This is like absolutely blurring the lines. We don't want to say in a loop means don't use OpenShift.  And what we're talking about here is making OpenShift part of that development environment because it has an awful lot of benefits for doing so. This is a very interesting example of where the fear of having to containerize up and put my application in OpenShift is going to slow my development down. Absolutely not. You can carry on making code changes, updating your code almost as quickly as you would if you're doing it locally with Caucus. And to get an update within four or five seconds, that's like no JS, that's like JavaScript speed. And it's something almost unheard of in the Java environment, which would normally be two or three minutes to build your Java file. And then another couple of minutes to turn that into container and deploy it. So maybe five minutes between each code change. We're talking here about five seconds between each code change. So that's kind of the difference we're talking about. And that's why we talk about the efficiency of the inner loop. Okay. Thank you very much, Alex. This is very interesting. Yeah, that's an awesome workflow for interacting with your services that are running on OpenShift, but still have that feeling that it's all running within your own environment and your own app. Cool, thanks a lot. To folks following, if you have any question, please send it in the chat. So we will try to answer your question from the chat here in Twitch and YouTube or Facebook, everyone who is listening. And in the while, we will go to the other demo, right? Wow, such a morning. I haven't seen three live demos at 10 a.m., folks. I need another coffee, wow. All right, so who's next? Are we still in the inner loop or are we transitioning to the outer loop? So maybe before we transition to the outer loop, can you tell us a bit more about those underlying technologies or tools that you have been using? Alex, I saw that you've been doing a Maven compile with remote browser. What was that using on the underneath? What was it, auto or something like that? The technologies that I've been using for this demo are code-ready workspaces in my development environment. I'm using Corkus framework. So that's Java. So I'm using OpenJDK. I'm using Maven as a build tool for that. And then I'm using OpenShift to host all those microservices. Now, once you get onto OpenShift, what are we using things like databases and various different frameworks? Each microservice actually uses a different framework, but the one that I was doing the live debugging on the live coding with is Corkus. On the other hand, there's no limit with OpenShift. I've got one of my components was .NET, another was Spring Boot. The web UI is Node.js. So it just indicates that there are kind of no limitations in what you can do with OpenShift. But the actual live coding is a Corkus feature. So that's a kind of special speciality. But that's really all I've been using today as part of my demo. Files, I think, actually is using some additional features. He's using something called telepresence. So maybe he can just talk you through that and what he actually needs to get that running because I think you need to install that. Is that true, Kars? I'm sorry. Yeah, yeah, correct. Thanks, Alex. Sure. All right, thank you very much, guys. So how about Madhu? What do you have for us today? So yes, today, so just to conclude the part of what we're with the inner loop. So what is really important around all the tools that we have seen today is really what you try to do. It's, of course, to accelerate the developer productivity, but not only. So basically, there is one question and one main question that we need to ask is why it will be good for you as a developer to be able to use, let's say, OpenShift or Kubernetes when you're developing your application. So the main aspect around that and why we would like to do that is really to be able for you to develop better application. So, yes, better application, why that? Because as a developer, there is always things that I was fighting, let's say, in my past career. It's really the fact that sometime when I push a code into a Git repository, I created and generated some bugs. So linked to not the code, not the business logic that I implement, but because there is some infrastructure problem because my application didn't get, for example, the specific dependency because I just left one bad parameters inside the application and so on. And that's, it's really, really, it's really, really, let's say, frustrated as a developer. It's really that the fact that I don't have the right environment to be sure that in my inner loop, when I have, let's say, all this flexibility where the code is mine, I haven't published the code. So I didn't have, let's say, all the resources that I have to be able to be sure that the application that I have, I will be able to test it into the same environment that the application will be used into production. So that's why that we do a lot of work here in order to be able to add these open shifts as a developer, inside the developer phase because I think it's not only for the developer, but also for, let's say, your project manager because I don't know if you are familiar with the concept about the cost of a software bug. So there is a concept with the fact that if you are, let's say that you have a bug into your application. If you find the bug, let's say, during the development phase, so this bug is going to cost, let's say, so 100 euro, right? You find the bug, so you find it into your development, so it's cost about 100 euro. After you push your codes into a Git repository and you find this bug into your QA, for example, this bug is going to cost you 1,000 euro. So it costs 10 times more. Yes, and you can, exactly, and you continue to that until the production because of course, if you have a bug into your production, so I mean the impact will be much more bigger because it's in production, so your customer see the bug, so you are going to have a bug. So very bad feedbacks are going to stop using the application, they are going to post everything into the social network and so on. So that's why to be able to remove this part because when you have a bug around the fact that I don't know my application, don't run inside the container. So I mean it's not, I think it's not an important bug, it's something that you can avoid but really be able and give the ability for you developer to use the production environment or like, so the same production environment to be able also to be comfortable and to be sure that when they're going to push a code into a good repository, everything will be perfect and clear. So this reminds me of a term that I hear which is shift left, is that correct? Is that you are shifting left and way ahead of time, your ability to find bugs, to correct them instead of having that happen later on in the CI CD process? Yeah, yeah, it's really to, yes, to keep people this, yes, the capability really to say that it's not that I'm going, for example, to test my code when I'm going to production or I'm just only to test the code when it's going to go through my CI CD pipeline but I'm going to really test the code so from the first form, so when I starting to enter and to implement my business logic, I will have all the resources to be able to be sure that my code is working, so technically it's working well on the environment and after that what you want to have basically when you have a code, so it's better, it's better, let's say more relevant to be able to have a code around your business logic because it's what you're trying to implement instead of having a code because I don't know you forget to add any specific, for example, cloud libraries that you need to run your application. That's cool, so another topic that I can think of is that you said the number of times I am able to develop my application because I have all my components, so traditionally this is something that have been addressed with things like STABs because the developer needs to have an evaluation of the environment in his laptop to be able to write his application and what you are saying here is that we are sort of improving this way of working without needing those STABs because I can now consume some live services even if it's a QA service, it's not going to be a STAB, it's going to be a real container containing my real APIs and interacting with that. Is that also something that you are referring to? Yes, exactly. Okay, cool. Yes, good. No, I was reading the chat, there's Sebi saying that the shift left is a new password. It's just a comment from Sebi. Thanks Sebi for helping fixing the title of the year. Well, thank you. It's a new, but it's been there for many years. All right, so thank you very much, Madu. Okay, so now let's transition to the outside world from your inner persona or inner loop to see how we can share that with others and push that to QA or even to production. Is that something that you have cooked for us? Yes, I have something around that. First of all, so let's redefine what is the outer loop and then let me share my screen here. Share screen is here. So let me know when you see my screen. It's all there. We can see it. Thank you. Okay, yes, perfect. So as we mentioned, so everything that we have seen today with all the technologies around the inner loop, so the inner loop, so code, you run your deploy or you build your application that you test that your application has the expected behavior and are you doing this loop in order to at the end create your application? After you create your application, so what's happening is especially when we talk about the container, let's put this into a container context. So you are going to build your container of your application once. It's really important. And then you are going to deploy this exact same artifact into the different environments until the production one. So you build your container.  Then if everything gets okay, so you're moving into the acceptance environment, you deploy it there and you run all the tests and so on until you ship your application into production. So everything here, and I think when we talk about outer loop and inner loop, I'm quite sure that within the cloud context or outside the cloud context, it's exactly what you're doing in your day-to-day life. It's what is defined as your application lifecycle, right? And what is going to change is the fact that you are going to have much more container. You are going to move from smaller services and small services is going to compose your application. So that's why that's in order to be sure and to let's say increase the quality of everything that you would like to deploy into production and to go through this, and to go through this journey. So you need to have a consistent way, right? To be able to push and to do all these steps. And this consistent way, it's rich and it's something that you will be able to achieve by automation, so many automation. And that's why we have the continuous integration and continuous delivery pipeline. When I talk about continuous integration for people who are not familiar with that, so the continuous integration is basically the process for you in order to build and create your release and to create, so at the end here, a container. And the continuous delivery or the continuous deployment, so there is a different terminology for that, is to be able to take this release and to deploy it into the different environments. Same thing, so automatically. So this is a part and this is a really, really important to make sure that at the end, what you're going to push in production will be, will have a really higher quality. If we move again, so to open shift, so let me show you here. So let's say that I'm starting here and I'm switching to my developer environment from the developer environment, what I'm going to have here, it's my CN project or one project in which that I'm going to simulate a specific environment, not my dev environment, it's what Carlos and Alex used, but it will be my, let's say my next environment, let's say the staging environment. One way to be able to implement the CI CD pipelines, it's, so first of all, you could use some technology, like I mean, the well-known Jenkins or other technology, which makes the work and which going to work fine. But in this new world, when we would like to, let's say to give more power to developers, so especially when we talk about all the agile methodology around so DevOps, or I should say so DevSecOps, now it's really to be able to distribute the work and the product to the end of this team. That means that it will be a team will be responsible from the creation of the application to the operation, to the same application into production. And to be able to enable that and to give all these capability, what we could use and what we are going to use, so right now what I'm going to demo, it's OpenShift the Pipelines. OpenShift Pipeline, it's a technology based on the upstream project, so Tecton, which going to help you to define some Kubernetes native pipelines. So that's mean that every, so you could give the capability to everyone to use and to create a pipeline. So there is no server to maintain. You just have to define your different steps that you would like to have. And after that, you will left OpenShift deal with such a pipeline. Just to give you a quick example and to coming from the end to end. So inside this project, I'm just going to take the code. So once again, it would be a code that we push into OpenShift into a Git repository, sorry. And from the Git repository, I would like to take my code that we put and take my code there. So we would be this one, so available if you would like to use it. I'm going to specify my code. So from Git here, I would like to deploy which application I'm just thinking about when application spring. I will take the exact same application that Alex used. I shared in the chat the workshop link. And if anyone want to try it, it can do just follow the workshop and also create an account on developer sandbox. I put in the chat also the link to developer sandbox. So it's a free account. You have to add a cloud access to OpenShift. So that's Kubernetes. And you can follow the same workshop Madhu is doing if you'd like to. Yes, let me change like this because it's like demo and I would like just to change a bit about which application I'm going to use. I'm going to use this application. So it would be a backend application that with you, especially Natalie, that we work with to be able to. It's a Qarkis application, but we see so it's just one preview that's what we are going to use. So the end application from the application, it would be a Java application. So once again, I'm not going to everything even to be able to build my container will be automated. I will let the platform running that. Can you please say a little bit there for me? Sorry, so we can see that. Here, so I'm going to specify the name. So I could say that it's so the Twitch app, and it will be at the backend. And here what I'm going to use here is I'm going to, for example, pipelines who is going to create for me, automatically a pipeline. Based on a tecton. So Kubernetes native pipelines here. So I would like to expose and to get access to my application and I push on the button trades. When I'm doing that, so this is familiar. It's something that we push into open shift than you have seen into the outer loop. But what is going to change here is the fact that now I'm going to build and to have this build based on my pipelines. If I have a look on the pipelines that I have, so it would be different step here. So without a different task here. So without going too much in detail, so I'm going to have, so one task is going to query and to get to clone my code from my Git repository. It's something that I have here. Then the other task is going for me to take that source codes in order to create my container image that it will push that container image into image registry. And at the end, if I go back to the detail is going to deploy my container image into my Git repository. The cool thing with this way to run the container, it's really that we're going to enable to run this pipeline. It's that we're going to enable and to leverage all the benefit that we have with containers. That means that each, let's say steps that you can see here running, it will be a specific container. So I could have, so let's say one container focus with Maven, for example, in which I'm going to increase the resources because it's Maven and I will need to take a lot of different, a lot of different libraries and I need to have a lot of resources when it's Maven. And after that, I will be able to have smaller container with smaller resources in order to do just to push into my image registry or to deploy an open sheaf or just to run some script and whatever. So I'm going to have this really good flexibility around dealing with my pipelines. What is good also with the pipeline is the fact that it's, as I mentioned, so there is no server to maintain. So that's been that no server to maintain and I'm only going to consume resources when it will be needed. If after my run here and my pipeline just finished, so it's going to finish and it's going to deploy the application there. So it's in progress. So after that, so my pipeline is now finished. So my pipeline is not going to consume any services. So it's really enable the serverless capability just consume resources when it's needed.  And now if I access to my services, so I can go to the URL as not working right now. So probably I missed something. So let me go to the log of the application. Outchecks, maybe the headchecks. Yeah, the headchecks, the application started before. Yeah, I think you didn't wait enough, I think. No, no, it should be okay. But probably I probably forget something. Did you miss environment variables or something that you need to inject in the backend? No, no, no. It should be good except if I have a different, let me just check that maybe the endpoint backend wise. The backend wise, no, same, okay. Is it red wine instead, red wine? I don't know, it should be, it should be that one. It should be that one. So all seems to be okay. Let me check very quickly in the terminal. Like that. Yeah, yes. The beauty. Yeah, I think. I bet it's the port, do you expose it? For the DNS. No, it's there. It's always the DNS. AT-AT is working, but you need to look into which is the port that you're exposing. I had this problem.  All good, everything is good. How much wisdom in this session, how much wise in this session it is. Check the service redirection, maybe.  All good, all good, yes, because it's a network policy that I've enabled. So it's for security reasons, right? Let me take that. I can, okay, I can write it. Too much security. But it's not, okay. This is a real left-seck of situations. Really? When developer has the power to control, let's say, application layer and networking, they behave like a system administrator, right? Network administrator, we used to blame them, but now with the power, we do the same thing, right? Yes, tak, tak, tak, tak, tak, here. So in my labor, so, I try to expose... Madhu, Madhu, you need to tell everybody that this is happening because you were trying other stuff. This is not something that you need, you want to use pipelines, right? Yeah, yeah, yeah, but on the pipelines, yes. It's just because I'm selecting the wrong, the wrong project. But this is a chance to show out to the back, right? A microservice publishing in Kubernetes. So what we have to look for, the logs, the service, the network policies. So it was also a way to understand what we have to look when we need to debug something. Yeah, so something that will be interesting also, Madhu, is if you can click on the pipeline, okay. So this is something that has been generated, okay? Yeah. Can you make changes to it, like if you go... Yeah, basically, so it's the pipeline, so generating by default. And if I would like to add, let's say, more tasks to my pipeline. So I will be able to edit it. And a pipeline, so what is a pipeline is just different, let's say, tasks or actions that we would like to schedule and to order. And on that, for example, let's say that I build and before... Let's say, before building, I would like to run a specific task. So let me check if I have interesting tasks here. Oh, let's say that, not here, but let me go here. So let's say after that I build my container image. From the container image, I would like to copy my image. So from my current image registry. So to another, so I will have some specific tasks, for example, Scopeo, in which I will be able to define the source URL of my image and where I would like to push my image and so on. I will be able to ask more tasks, of course. So before building, let's say in parallel, I would like to run some specific command. Here, I have some tasks here, so not cluster tasks that could be interesting there for me. But I would like to use, for example, so create a configuration for here and I would like to add more information there. And so I'm just editing some cluster tasks like this. But it's really the way that, of course, you will be able to build a task as you want to build a task and it will have a lot of benefit on that. So you don't have to be a Tecdon-Diamond guru to be able to make changes to your pipeline. That's really nice. And so can you show us where those tasks come from? So these tasks, yeah. These are maybe what we call Tecdon tasks. Is that correct? Yes, this is, so what I just show here, it's the Tecdon task, let me just come to here. So it's a Tecdon task and everything around the different labels. So it's something that, a task is a YAML. So everything that we have with offensive and Kubernetes is a YAML. So I will have my cluster task and all the tasks that I could use so by default from the cluster is there. If I would like to create my own task, it's also possible because it's a YAML to be able to have a good starting point. So we have, so the app, the Tecdon, the Dev. So it's something that we are going also to integrate as a catalog inside OpenShift in order to give you two other spots where people is going to share tasks and that you will be able to reuse. So like you have with the Docker app, for example, other container public registry. And let's say that I would like from this, I use SonarCube. So I would like to use my Sonar scanner. So here it's explaining what is that task. I will be able to just take the task here. So copy that task. Now this task I'm going to add and import my YAML file into my project. So now my task is creating. And if I go back to my pipeline, so I go here from the pipeline and from the pipeline, I'm going to edit.  So I select my cube scanner task and of course there are some parameters. So what is also important is the fact that I create, for example, one pipeline for all my Java application. And after that, everyone will be able to use that same task, just changing the different parameters. And I add my... Yes, and I define here, yes, URL and the key and of course I save it. And next time that I run the pipeline, so my task will be there. Cool.  That's really awesome. Thank you very much. Awesome, awesome. And yeah, this is a nice way of extending the capabilities with your own custom tasks. So thank you very much for showing that. Yeah, no problem. Cool, super cool. We have seen today three live demos on cloud native inner loops and outer loops. I would like to thank a lot, Alex, Carlos, Madu for these three live demos. It's just one hour folks, you know, it's not that easy. We have seen all live demos we shared in the chat of the links. If you wanna try out those demos and also there is the links to developer sandbox if you'd like to try it out on OpenShift online and the cloud access 30 days, renewable for free. You can use developer sandbox. So we also use developer sandbox today. I would like to go to the end and remind what we have in the schedule today. So the next one would be the level up hour. Docker compose with podman version three on 9 a.m. ET time. This is interesting, Docker compose with podman. And we come back again, the OpenShift coffee hour we'll come back again on Wednesday, April 14th with another disconnected series. We will talk about VMware disconnected with IP with Robert Bonnet. Thank you everyone for attending. Thank you to our guests. Thank you. Jafar, do you have any final words to these awesome live demo we saw today? I would just close by saying thank you very much. And I'm just gonna go ahead and try everything you showed right away. So thank you guys. All right. Thank you everyone. Have a good day. Bye bye. And see you in the next session. See you the next Wednesday, April 14th. Bye bye. Thank you. Bye bye.


Gradebook. Eich cwrs in Moodle has its own gradebook which you can access from course navigation, grades. By default students see this link as well and this is where they can access their course grades. Here is an example gradebook in a different course. The first screen is the grader report where you can see the students you have and graded activities. And note that if you have a lot of students and graded activities then as you scroll across you can still see the students names and as you scroll down and back up you can still see the titles of the graded activities. From the drop down grade history will allow you to see the different grades and when they were modified and by whom. The single view or the three dots by a student's name takes you to the single view which allows you to focus on one particular student or one particular grade item. The grade summary report lists all gradable activities in the course with the average grades and you can filter by activity. The user report takes you to the individual grades of one student and this is what a student sees when they click the grades link in course navigation. In setup you can add new grade items or edit existing ones and decide on course grade settings or your preferences. In scales you can add a new scale. Custom scales are what the teacher has added to the course and standard scales are what an administrator has added for everyone. So you the teacher can add a new course scale or custom scale by clicking add a new scale, giving it a name and adding the items with the lowest first. Then it's available to use in your course for example in assignments. You can also import grades that you have offline as easily as pasting from a spreadsheet and you can export them as different formats if you want to print them off for instance. The grade book is very powerful in Moodle and we've only been able to see a few of its features but hopefully this has given you an idea of what it can do for you as a teacher in your course.