 Okay, I'm not sure if we are live or not live. Yeah, I think so real life. So it's always tricky when the streams take some time before. Hello, everyone. I need to do one important thing what I'm talking. You can enjoy the nice view behind me. I need to share something with my guest, the link to connect. Okay, so let me do that right now. And then, yeah, all our things, people. Say hello on the chat, be chatty. This is, you know, a relaxed show. You know, we are there to, you know, you love the Star Wars Legos. Okay. No, no, by the way, that's not Star Wars. That's breaking that, James. But anyway, I think my guest joined. So I will be able to bring him on stage in a few minutes. I see him there. I will bring you to stage in a few minutes. Anyway, welcome everyone for the show number. I stopped counting. Anyway, I'm really happy. I'm streaming again from my garden. Why is that? Not only because it's cool, but also because I'm streaming with my phone. My connection is my phone, my 4G connection. And I realized I get the best connection when I'm streaming, when I'm outside. Okay, it's double, more than double down and double up my speed. And yeah, and I didn't ask if you can hear me well, but I assume you can hear me well. Otherwise, people will complain. James is there. So rest of the people say hello in the chat. Okay, don't be shy. Please don't be shy. I'm really happy to bring about our guest today. I will bring him on stage in a few seconds. His name is Nicky. And well, great thing. We won't only speak about that, but he works at Lego, which I find so, so cool. We will speak about that. But he's also a passionate developer. And yeah, I have a lot of questions for him. And yeah, that's it. So let me go to my studio and let me see if I can bring Nicky on stage. Hello. Hello, Sebastian. Hello. Yeah, well, I can see you well. I can hear you well. That is awesome. So our things. Oh, things are great. Yeah, good weather too. Like you have apparently. So everything is cool. I'm standing here in the new campus from Lego. So the new headquarter in Denmark, super cool. Super cool. Okay, I want to know everything about it. But before that, I usually, well, my first question is just, who are you present yourself in a few seconds? Take the time you want. Okay, yeah. So my name is Nicky Milheim. I'm a developer that works for Lego. And I've been in the industry since the beginning of the 2000s. So, so I've some of the beginning of my career was in IBM. So I've been there also, probably one of them more, more noticeable companies you would know about. And then of course, Lego too. And I've been in other places, small companies and so on have had a lot of different roles, you know, Java developer, Java instructor, no predicate developer, so other languages than that. So that is what I'm doing lately here in Lego, working a lot with cloud and so on. And I'm very active on Twitter. So, which is also why I guess you I told you are interested to be with you. Yeah, I've been following you for a long time. I don't remember when I started following you. I think we never met, right? No, no, no, no, I've been to Denmark a lot of time for grill comf, you know, grills, you know, super cool conference. All of those are great technologies. Yeah, yeah, organized by Soran. That's how I entered the open source community. And actually in Denmark, great one was my second conference ever. And yeah, I have really good memories there. But yeah, I think we never met. But yeah, you you treat a lot. And you also treat some open positions sometimes at Lego. And let me be honest, I'm, I'm really happy at red. But every time I click, I say, Oh, and my son, he says, Hey, look at that, because my imagine my son is completely crazy about about Lego. But you're, yeah, so you, your favorite, you are Java, you consider yourself as Java developer? I don't, I don't, I don't like to use that predicate anymore, because I think actually it's an anti pattern we have in the industry that we like to put people into a specific language and so on. So for example, I'm doing hiring as you also say now, what I'm looking at is not I'm not looking for a Java developer, I'm looking for a sharp mind that can, that can show that they have, you know, programmed before and they are able to solve solutions. So I don't really care what language they come with. You know, there are of course extremes where I say it's too alienated to what we're doing. But if you are wonderful JavaScript developer, wonderful TypeScript developer or scaler developer and so on, then you can very well then this position too. So so that's how I feel. I think I've moved a bit myself there in the last five, six years. I've traditionally always focused a lot on Java because there's been so much in the ecosystem, you know, in surprise edition and so on spring was was an aspect still. So of course, I'm the kind of type that likes to specialize a lot in stuff. And now I'm specializing more in cloud. So probably you can see that on my tweets, it's AWS, everything right. So this is where I put in my love now. I still have the background, a lot of heavy Java stuff, but I'm doing a lot more non Java today. So a lot of JavaScript and TypeScript, that is my everyday now. It doesn't mean that I don't do Java anymore. And I don't like it. It just means that the situation is different. I actually think that the because I've landed, you know, a position in my services, the situation changes a little bit from having a big investment in in one type of language in comedy to actually accommodating different types of languages. And you see that a lot here in Lego. So we don't only use Java. There's a lot of that, of course, but there's also a lot of other languages like Scala, Python, and so on. So you will find everything here. Yeah, that's great. Yeah. And so what is, what are you doing exactly as Lego? Well, I imagine Lego is huge. Even the IT department must be huge. Are you managing the retail stuff or managing the factory? I don't know. I can enlighten you then. So I'm working actively as a developer doing backend development, you know, databases, mostly no SQL at the moment, DynamoDB, because we are in AWS to infrastructure code, because we build the entire solution ourselves and operate it and so on. So we don't throw it over the fence as we did in the old days. So you can say that is some of the technologies that I'm broadening myself with right now. And the product is the B2B web shop. So the web shop shop not used by you, but a company's Walmart and so on, that buys Lego and sell it in the stores and so on. So I'm doing that and this is all AWS. We have serverless Fargate containers, right? So yeah. I want to talk about cloud. We will talk about cloud. And just curious, you said your move to the new headquarters. Is it close to Lego land? Oh, it's super close, actually. I also, I think I tweeted it recently that you're back to the office, right? So it's super fun. And I still, even though I've been in Lego, so if I count everything together, it's, I guess, five years almost, if I round up and try to break with it, right? So I'm still fascinated by the spirit and the things that you see when you see Lego land and the people and the joy and excitement there. And that's, that's how it can be for some of us in Lego. I'm sure, right? It's very close. So it's a new, very shiny big campus. It's still being built, actually. And some of us moved in already now. And it's very close to Lego land, yes. Okay, cool. Yeah. I went actually, when I was young with my parents, we were traveling through Norway because I have family there. And we stopped at Lego land. And yeah, I was 10, something like that. And four years ago, I went to Lego land in Frankfurt. Yeah, I think it's Frankfurt. There's another location in Germany, which was, yeah, my son was completely crazy because he was a huge fan of Ninjago, you know, and you have a whole area just for Ninjago. And also the nice thing that I remember, and then we will move over class, was you have a sample factory or like a real part of the factory, how does it make the blocks? And that was so, so interesting. And at the end, of course, you arrive in the shop, but it's the shop where you pay per weight, you know, crazy blocks that you never, I think I was crazier than my son when I wasn't there. Anyway, so super cool. So yeah, Lego and the cloud. And you and the cloud. Yeah, let's see. Is is Lego a cloud company? Well, did you did the shift entirely to the cloud? So we still have on premise solutions in Lego, but there's no doubt about that we are moving more and more into the cloud. We have been doing that for years, and it's continuing to rhyme. I don't know if we are going to not have on premise solutions, but we have a lot in AWS, which is our primary strategic cloud partner that we have. We also have stuff in Azure, but it's when we develop on my team and the teams around me, it's in AWS. Okay, you also have Azure. Okay, interesting. And when you say AWS, are you deploying on pure on VMs or on Kubernetes? Yeah, so it's very different depending on where you are in Lego. Some we are very, you can say, autonomous teams here and there. So we are not working entirely on the same products. It's very heterogeneous, the products that we make. Some have developed and invested in Kubernetes setups, and others have not. So in my area, it's, you will find mostly serverless technologies, but you'll also find something that is a bit similar to Kubernetes, which is AWS Bargate. So before they offer this managed version of Kubernetes, EKS, we, there was also Bargate, which is a companion technology where you don't have to reason only the EC2 service and so on. And that made sense for us originally to invest in those kind of technology because it allows us to move fast. So that is one of the biggest selling points of serverless technologies and so on. And then you, as an extreme of that, you obviously have AWS Lambda functions and so on. You find the similar technology in other cloud providers, but I'll say that it depends a lot on the setting. So if you have a lot of developers working on a platform like hardening the Kubernetes setup, then of course, that's a bit different. And you will also find that in Lego, actually. Okay, interesting. Really, yeah, yeah, you have, looks like, that reminds me, I remember I visited campus of Facebook, where you have so many different teams doing almost everything and they can choose almost what they want. And when I hear you, almost this feeling of that you have a lot of flexibility inside your teams. So it's the best. And that is also something we are talking about now. As you have also seen, we are going through a very impressive digital transformation in Lego. And I know that there is some awareness about this complete autonomy that we have had and enjoyed for a long time, and then getting a bit control over that. And that is a work in progress for sure. So of course, I know that there are talks about the Kubernetes and so on. And I'm also thinking about it. Is that the right approach? Because you can argue that it's the right approach if you have the setup and the investment in the platform team. So one of my colleagues comes from Salerno. I think he's online now actually. He's on the chat, if you want. They have actually invested a lot in that, right? So you'll see them dominating a lot in Kubernetes' landscape also. And who knows, one day maybe we'll get there, right? Yeah, sure. Sebastian, I can tell you, I'm very fascinated about both worlds. So you can say the choices about going serverless in our area has been dominated by. So what is wise, given that we don't have the platform team, is it wise that I and my colleagues start to work on that only and don't get to deliver business features? Or should we use the cloud that we have and simply take off the shelf, which is highly available stuff, the hardened security, all that that you will get for almost free there. For me, it has been a no brainer to go down that road to get the same approach with Kubernetes. You need a very mature team that can do the same, right? Especially if you're going to persistent technologies like databases and Q-Systems. And it's not fun anymore. So the compute power is the easiest part, right? So everybody can do that. It's the other part that I'm more skeptical about. Yeah, I understand. You say you're moving fast. Did you go up into production? I'm just asking you. So it's very different according to where you are and they go also, of course, because we are so autonomous in the end there. But on my team, it has been for the last year a focus to be able to do this with a great confidence that we can do it. And we have no problem deploying on a Friday, but we do consider it before we do it, right? And we are not that competent. My team is not the one that can go and claim we release 100 times a day because that's simply not where we are. But it is something I'm thinking a lot about because as I see it going, you know, making frequent deployments to production, that means they are smaller, hopefully, right? So it means less risk and so on. So I think it's the right approach. I totally buy into that idea. And it also means if you're fast to production, it also means that you can undo it fast. So you deploy something, it's rotten, you need to, you know, release a patch fast, right? So I think it's super important and my team is we have been discussing that, you know, for the last years, right? Yeah, it's not just about going faster to production. It has so many benefits. Sebastian, so it's not only about, so if you want to go fast to production, it also means that you need to have control over your quality. You cannot do it if you have no well-tested system. That is why we totally buy into testing our stuff and we do it because we think it's the right thing to do. It's not because you want to check off something. It's because if I have it under control, I know it will catch something, right? If there is an obvious error and if it doesn't, and we find there is a bug, we add a test to the test suite so that it's, you know, called by regression test the next time. So I can tell you that everything we do on our team is to harden that go live process. We are talking a lot about it. We could use a lot of main power, but we are trying to do the best we can. Best you can, yeah, yeah. Be efficient. Build the best set. I'm just making the analogy with Nico. Are you using any methodology in your teams? Are you agile, scrum? I don't know. I guess. Yeah. So I think you can easily call us agile, right? And if we are following scrum, yes, we have been there and done that and we have been the process a bit. And I know as soon as you start to bend that process, you may not be doing scrum anymore, right? But here, there is the best way we have evaluated. Is it the right thing to do to have the daily stand-ups every day? And it's not necessarily the right thing to do every day for our team, but you may find other teams where it's super important to do that. But we have been discussing all that. You can say a process that is in scrum, whether it makes sense for us. So it's something we work on. And I don't have the solution for every team. I actually truly believe that it's very team-specific. How much binds that process, right? So you are pragmatic. I like that. I hope so. I think you are too hard on some methodologies. And I'm unlucky, but I have been in a lot of teams. I never really saw it working perfectly. More in teams where we are organic agile by nature and deep mathematics. And Sebastian, that's also what I believe in. It's the right approach. So you start with that rigid model, because this is the book. You have to follow it in order to learn it and get it under your skin, right? And then at some point you step up and say, hey, this really doesn't seem to provide the value that we feel it should provide, right? And that is we have been there for several areas in the process. And one of the biggest wins of scrum is to have those retrospectives, because that is super important to stop up and breathe and find out. So can we improve it somehow, right? And then I cannot remember if it was on a retrospective. We decided to tune the process along the way. But I still think it's super valuable. I think having some process is valuable. You may argue that on certain teams, you don't need all the bells and whistles in scrum, let's say. Yeah, it all depends on the team itself. If you are a lot of seniors or a lot of remote, they're so much moving forward. And that's where you see good team leader or manager that can adapt the right approach. Serverless. Let's talk a bit about serverless. First thing, because I think there are still people not agreeing. What is serverless for you? Okay. Yeah, so of course, there are extremes. One technology that I get to think of is, of course, AWS Lambda. I have some piece of code I deployed. It's a zip file. And you know, that's super serverless to me. I don't get to think about what is behind the scenes. I may know that there is a Linux runtime there, but it's not something I have nightmares about in which, right? So that's one extreme. Also, I think having DynamoDB is serverless enabling technology, right? You point a click. I only, my abstraction layer is a table and index is on that level. You know, it spares me from having nightmares about how to operate the hosts below it and having the heart and circuits there and be attacked by SSH idiots out there. You know, I think it's, and then, of course, there's this gray scale, right? So it's Fargate, serverless technology. And I would argue that it's almost, this is right, because I get to provision my tasks, probably relate to it as parts or something, right? And this is my abstraction level there. But still, when I do work with containers, I still need to find the point at which it scales out, for example. So I need to find out, should I scale out on CPU usage or should it be Merian's one? When I work on AWS Lambda, the scale out model is so simple that I don't get to think about it. I know that if I send a request into my Lambda function, and another one comes in, they will pop up a new container next to it and another one, and another one. So it's idiot safe in many ways. And I really enjoy that. I can tell you, I recently had to work again on our Fargate setup. There's a lot of things I love about that. But it was very apparent to me that it was another abstraction level. I was closer to the metal, and it sounds insane, because of course, it's all virtual, and it's in the cloud and so on. But that's for me a big difference there when you compare, let's say, function as an abstraction. And I know you have similar technologies if you go Kubernetes and so on. So you can get the same and I'm flexible. And I don't argue that one is the perfect the way that I think about it is, how do I ensure that I can sleep well at night? So I go on weekends, right? Then I would love to not have nightmares and choosing some of those serverless technologies like Lambda and DynamoDB. They're good examples of that. S3, an enormous fantastic technology. When you use those technologies, I'm not thinking about those technologies causing trouble. What I'm talking about is the data that I put into them are tripping up other scenarios in the system. That's where the problem is. So it has shifted from being technical problems because I couldn't operate a Kubernetes setup. So that's how, given that we are the size we are in our team and the teams around me, then serverless is super fantastic as I see it. Yeah, yeah, yeah. It removes a lot of friction and yeah, yeah. So I'm more on the Kubernetes side these last days and I'm using Knative for the serverless solution. You've probably heard about it. And yeah, what I like about it is that instead of writing three different long YAML files, I just say I want a serverless service and I want to run this container image and maybe I want some health probes and that's it. And I send it and all the magic happened for me. Skill zero if I want. Skill two, I don't know. I don't have to care about that. And yeah, and it's native to Kubernetes. So if I am running Kubernetes on my Amazon, but I also have some Azure, well, I will be able to deploy the same resources on all these clusters. I totally appreciate that, Sebastien. I would also consider that as a serverless technology, given that the hosting platform is under control and so on. And I totally appreciate that. So I think you will also find the situation here is because of the staff that we have. And as I also told you, LEGO is in a very huge transformation right now, IT-wise. So who knows where we'll go in the years. But I have this major point that is if we go away from all the truly serverless technologies hosted by AWS, or it could be some other cloud trainer, then we better do it at least, you know, almost as good ourselves, right? Because otherwise I'll get troubled. My job is down. Our job is down. So this colleague that put around and the other colleague, we will go to that, let's say platform team. And that will not be of course fun because, hey, there's no income while it's down, right? So that is how I see it. If we go that way, it has to be robust and stable. And I know we have it somewhere in LEGO also, but we have been very isolated here and there. So some teams has it under control, like perhaps you have experienced also, and others have chosen serverless to get the work done and move fast. Yeah, yeah, yeah. So, yeah, you said you are in a global, the IT is getting, is involving a lot lately at LEGO. Does it also involve a cultural change between, you know, dev ops, dev ops, breaking the silos? Is that something that you also have in mind? Yeah. So I think that is implicit. And I think that journey actually started for a lot of the teams out here years back, varying degrees all over the company. What we are doing right now is something that is bigger than that. We're trying to shape the organization in a way that is more product oriented. And as you know, it can reflect how the software products also kind of end up, right? So we are trying to organizationally, you know, make a perfect, not perfect, but a good and, you know, streamlined setup. And that is the big change we are experiencing right now. And in addition to that, we are changing a little bit how the engineering teams are up put together, at least somewhere, some of the places in LEGO, right? So I think that's in many ways even bigger than if you just operate it and, you know, yeah, but we have been doing that for years. Okay. Um, whoa, I'm attacked by a bee, but it's gone away. That's the risk of doing that in the garden. About AWS, I see you treat a lot about certification. So you, yeah, can you tell a bit about this certification process? It's, there are a lot of certification. I remember I saw someone on Twitter that managed to do them all, which is crazy. But what is your, why do you do certification and how much time does it take? And yeah. Okay. So in the old days, before I threw my love on AWS and cloud and stuff like that, when I was developing Java code for the application servers, it was the application servers I was trying to get to learn so that I could recognize the errors and why did it perform that it did. So I've always been like that, that if I put my code somewhere, I want to know where it's running and how it works. So that's, that's my, you know, starting point for all this. So the reason for me investing a lot of energy right now in all the AWS stuff here is because I'm using it a lot. We are losing using it a lot. So when there's trouble, I want to know why I want to be the, I'll try to be the go-to person if there is some, you know, I am problem to some permissions that doesn't work. I want to tell people how it works with the locks and how to enable metrics and so on. So I want to know the runtime where my code, the code is just one point. And it also, it depends also of course on the translation that we operated to, right? And that's, I don't just develop the code. I have to operate it effectively too. So I have to know about services like, you know, instrumentation like X-ray or and so on. Right. So for me, it's an operator that if I want to do my best, I need to learn the platform. If I was in a Kubernetes setup, you would find we bring the same, but with Kubernetes, right? Yeah. Okay. Yeah, totally makes sense. And this takes you a lot of time. Is, are these certification hard? I guess so, but yeah. So Sebastian, it depends very much on your mileage. So if you have had exposure for AWS for years, which I actually had before I started this, it went nuts last year, I guess, right? I guess around December it culminated with me, you know, putting, you know, the the pedal to the metal, right? And so I'm spending more and more time on it. And during that journey, it also became apparent that if I wanted to take more than one certification, it was a good time to do it once I just took the other one because some of the things I learned I actually could use in the next certification. So there's no point in waiting a year for taking the next one. That's why you have seen me super intense in the last months too. But I can tell you that I think once I've, right now, I'm focusing on the professional, you know, the Big Brother certification to the solutions architect associate and trying to look at that now, right? So I'm getting up early trying to study, you know, following video content and so on, and looking at FAQs, playing around and so on. So I'm doing that now and that is also because I don't want to delay it a year because then I know it would be a much bigger task. So it's very practical and that I do it. Then there is another point to it also. I can also see that it inspires other people, not only here in legal, but also outside legal. So it inspires me that I want to do it even more. But I can also tell I'm a bit tired now as business and I've been doing it very much for the last month, right? I think and I still have some family and so on. I want to keep it. Exactly. Yeah. And are the exams as crazy as, you know, for Kubernetes or the any exams you, since it's online, you have to have nothing on our walls. And that's the same, Sebastian. I have been forced to move my laptop around to show what's under the table, what's next to me and so on. I have to show my wrist, right? Because I have a smart watch on your wrist, right? So I think it's actually also okay, because there's nothing worse than a dishonest achievement of certification. I can tell you that I'm trying to keep my focus on why am I doing this? I'm doing this so I can move so I can use it in discussions with my colleagues next to me. I like to say that I'm not doing it just to get the certifications. But of course, there's also, it becomes more fun when you get them. So I guess it's just enforcing it a little bit, right? Especially, I think one thing is you can go around and tell yourself that you know all this. But the real test is, can you actually, if you go down the study path to one of those certifications to really understand, I learned a lot. So even though I had years of exposure and eight years before I started this, I have learned so much, right? And I think a lot of the people out here that say they don't really need it because they're better than that, of course, right? I think they would learn a lot. It's like taking a, you know, I took all the Java certifications when I started in the industry. That was super hard back then, right? And I wanted to have the perfect score there, right? I gave it all I could, right? And I couldn't really do it here in AWS. But the last month, it's the same again, right? So it's difficult to combine that, you know, intensity with also having a family. So I'm getting some, I'm being beaten up a little bit there, right? Because I'm apparently not always there present in the mind. But you know, that's how it is. But yeah, I like the fact which said it's also just about learning. We must keep learning new stuff. The thing is, there are very skilled people here, solutions architect in AWS that has curated a start, you know, some points that they want to have people proven that they can master, right? Because if they master those points, it means that they have awareness of different situations in AWS. Who am I to question that to begin with? Maybe I can do it, you know, in a few years. But I think it's really a good, you know, approach to master an ecosystem in, right? And I hope it's the same when you do clinical certifications or whatnot. Yeah, I was just checking the chat. Well, people are making fun about name delay, how you write Lego, right? Because someone write Legos. Let me see. Collect an AWS certification like the rest of us collects Lego sets. Okay. I've seen that, Sebastian. Of course, that's the thing is, once you take, let's say the practitioner certification, take the first associate level solutions architect, it's so much easier to take the next associate and the next associate. So that's why it can make sense, even though I can see it seems intense and weird. But that's actually why for me it was an operator to continue it. Yeah, yeah, yeah. Okay. Well, we are almost at the end already. Just, just the last question. Let's talk a little bit about Java again, because in the Twitter trend, you mentioned, oh, I will maybe be mentioning Spring Boot. Well, you just mentioned it's one, but I love Spring Boot as well. Have you ever tried or played with Quarkus? Do you know Quarkus? Yeah. So, Sebastian, my knowledge of Quarkus is what I've seen in presentation. I've never actually used it on the job. I cannot even remember if I put it down the shelf and actually tried it out, because my mind has been all sorts of other places. You will find me, when I go back and I'm not thinking about so much AWS, you'll find me as Spring Boot fanboy. And when I say Spring Boot, I'm actually referring to also Spring Framework. Maybe if you followed me for years, you will see that I was a bit like this for Spring Framework at some point. And it's still there, but I also find a lot of other technologies, you know, super amazing. I like to work also in JavaScript and TypeScript. I'm amazed about what you can do with TypeScript and it's so powerful compared to what I can do with Java. And so, I think I like to say I'm a bit more open now than I was. Let's say six years back, right? Then my world was very specialized and I don't think it's the answer anymore. It's not for me at least. Okay. Well, that's it for me. I really, really, really enjoyed the discussion. It was really interesting to understand a bit how things are working at Ligo, but also your approach and yeah, ending up with the certification. I really enjoyed the discussion. I'm going to do now some live coding for the rest of the people and maybe play a game. You can hang out here or stay on the chat. But I would like to thank you so much for joining and yeah, hopefully one day we will be able to meet. Hopefully. And thank you for inviting me. As you know, I don't like to position myself as a rock star. What you know me from is from being active on Twitter, right? I find it amazing that you want to listen to me. I hope it makes sense. It was a well, not a well guess, but yeah, I was following you for a long time and yeah, I tried to find interesting guests every two weeks and on different profiles and yeah. And you are present on my time, so I say yeah. So thank you so much, Niki. And well, hopefully see you next time and enjoy the rest of your day. Okay. Yes, have an awesome day, it's a blessing. Thank you for inviting me. Thank you. Bye bye. So everyone, are you still letting me double check here? I'm just with one screen. It's a bit tricky, but oh yeah, there's some delay. I still see on the feet. I still see Niki. But yeah, it was great. It was really great to have Niki. Really interesting point of views as well. I like to share to hear other points of view like he's on the cloud, for instance, heavily, but he isn't using still Kubernetes. I think almost all my guests I had previously speaking about the clouds, they were all speaking in fact about Kubernetes. Anyway, let me see how many people are there. Yeah, well, we are still a lot of people here. I haven't prepared any game, but I can deploy a game at any moment. But before we deploy a game, I would like to show you some fun stuff. It's been a long time that I didn't do programming. I will be just live demoing one pretty cool stuff. Okay. I'm checking here on the chat. Okay. Let me share my screen. I share my screen here. And yeah, so here we are in inception mode. You can still see Niki there in black and white. He's hanging out. But what I want to show you is this, oh, not web, not WhatsApp, but web captioner. Let me put that in the chat, by the way. It's a simple service to go there. It's a really simple service where you can do captioning of your voice. Okay. It's really important. I still must think about it how I could include that in my stream to make it more inclusive. But yeah, my English is not that good and so real things are there. But let me just show you how it works. You go just on with this website and you can say hello. My name is Sebastian Blanc. Blanc. Blanc. Okay. Sebastian Blanc. Okay. Oh, maybe I'm the brother of Josh. No, I'm joking. Anyway, I'm living in France and you can see here it's capturing my voice and turning that into a text, okay, to a transcript. So that is pretty nice. I'm not sure which mic it's using. But yeah, let me stop captioning and let me show you something. This is a cool site. Okay. But there's something even cooler. You can add, let me go to channels here. You can put channel, you can integrate this web service because it's a web service to third parties. You can add it to Dropbox. Not sure what it will do, but to OBS, that's the streaming platform. Okay. To Zoom, if you want to have live transcript of your Zoom meetings, you can add it there. But you can also add a web hook. Okay. And a web hook, actually, you can point to any service that is running. Okay. Let me go. Oh, still has my old one. That's not a problem. Documentation. Okay. Let me increase that a bit. There we go. You can point to a URL and for each word that is said, you will receive this payload as a post request. Okay. Containing this transcript with the word you are saying and the sequence, if you need to order that, et cetera. Okay. So I say, hey, that's funny. I want to play with that. Okay. So that's what I did. Okay. So let me show you a small application that I did. Let me just double check here first that everything is going well. Hi, people there. Okay. People still are there. Awesome. Oh, yeah. You can see. Let me see. Okay. So all you need to do is to configure this and point to a web address. And look at this, I can point to my local address. Okay. So what I have here is a simple application, version in Quarkus, of course. And let me see. This is my rest. End point here, listening on transcript. Okay. That's my end point. And then I have here, well, post method, maybe we'll see that later. We have this post method. Okay. And here I receive because, yeah, they don't send it as content type as JSON, though I cannot march on it directly to an object. I receive that as a string, but that's not a big deal because I can easily with a JSON object extract from that, the word that I'm saying. Okay. And here you can see my awesome programming skills with a lot of if and else because I have no knowledge about how to manipulate transcripts and stuff like that. So I've just been playing, but it starts there. Okay. Here I get the transcript. If the word that I say is get called skill. Okay. So here I do a system print out. Yeah. I don't do a log. I set this variable to true. Okay. And then the second time that I arrive in this, in this, in this method for the second word, I check here if I'm in skill mode. So in the second state of my recognition state. Okay. If I say, okay. I'm now in deployment mode. And I capture a second word and this second word I stored in a string called deployment. Okay. Finally, I have a when I come the third time in my method, I listen for the third word that I will be saying. Okay. And if it's up here, I'm using a Kubernetes client. And I pick the name. I search for the name of the deployment that I said before. And I skate it up. Otherwise, I should say here, if it's down, I scale it down. And the idea here is to be able to scale up or scale down my pause just with my voice. Okay. And well, we can try to make it run. Okay. I think I just need to do two things before. Let me say I need to run. Yeah. I need to start. I need to start a Kafka cluster but this is because of another stuff that I will maybe show you. But anyway, let me run that. Let me run Minikube. Minikube, remember, is having a Kubernetes cluster running on your own machine. Let me increase the font because it's the quality stuff. Start. Let me do that. Okay. Let me double check the chat. What language is this? It's asking AJ. So, good question. I was making too much assumptions. This is Java. This is Java code and I'm using a Java stack which is called Quarkus. I can show you that. If you go to Quarkus, hopefully, yeah. If you go to Quarkus.io, okay. I will put it in the chat. Quarkus.io. Let me see that. Quarkus.io. And I'm just making sure, yeah. You will see that there's a Java stack and it makes you able to build really powerful cloud-native applications. Okay. You can compile it to native as well as you want. It integrates really well with a lot of existing frameworks like Hibernate, Infinity Span, Neo4j. And yeah. I love it. I felt really in love with this platform and there's also a great developer experience. Okay. Meaning that you can, let me see. Everything started here. Yeah. Java app. So, I can start it like a Maven project. Let me say Quarkus.dev. Okay. And that will start my application in development mode. Okay. So, build my project. Run it. If everything goes right, let me see if I didn't miss anything. Okay. Yeah. It's good. It's running. And now I can make any change to my code and, well, it will still running. Okay. That are some of the great stuff. But look, my application is running. Okay. And you remember I exposed here in my code something called transcript. Okay. So, let's go back to my web captioner, which is running here. And let me do this. Update channel. Okay. And now if everything, if the demo goes are with me, I will start captioning and it will capture the words. Let's just make sure if that is working. First step. Start captioning. Hello. This is me speaking to my application. Okay. So, let me stop here. You could see here in the lock, it's capturing my words. So, each time that we are here, we are in a POST request. Okay. That's cool. But I didn't set the word skill. Okay. Because if I say the word skill, then it will trigger. It will enter the other if statement. Okay. And that's what we are going to do now. Okay. So, I got here a cluster running locally. If I do a Qubectl. Let me do a watch. Qubectl get pods. So, here we will see the pods that are running in my cluster here. You can see I have two pods called banana and I have one pod called, two pods called apple and one pod called banana. Okay. And what I'm trying to do now, what I will try to do is to scale down my apple to one pod. Okay. So, let me see. Okay. Let me start the captioning again. Okay. And we will try it. Start captioning. Scale. Scale. Apple. Down. Down. Okay. Let's take a look here. And look at this. It's terminating my pod. Okay. So, it's working. Let's try to scale up banana. Okay. Scale. Banana. Let's take a quick look. Luke is creating for me a new banana. Awesome. Isn't this? It's really funny. Let me show you something else. Let's deploy another pod here in our cluster. Let's, here I have banana. Let's make it. What can I give it as name? Let's call it orange. Orange. Orange here. Orange. Orange. Let me deploy that. Okay. So, here I make a new deployment. And if I do my watch, you can see I've got my orange pod running. Okay. So, I can prove you I'm not saying you anything wrong. Let me double check on the chat if everything goes right. Okay. Everything goes right. Okay. There we go. And he's still capturing my voice here, you see. Okay. Let me try that. Oh, I'm lost. Let me go back here. Let's try to scale up orange. Orange up. Okay. You saw, because I mentioned the word, I am not going to say this. Otherwise, he will, oh, and that's a funny thing. He didn't understand up, but he understand down or don't remember what I say. Hmm. Okay. Can I try it again? Scale. Orange. Orange. Orange. Down. So, look at this. I don't know if you see it. Okay. Yeah. And there we got an exception. In the suit French instead of orange, which makes me, which is really funny. Okay. Let me stop this app. Let me try to show you the other stuff that I did. Okay. Because I had a lot of fun with this application. I mixed that. You wonder why I, maybe I started a Kafka cluster because I said, well, since I can capture my words, maybe I can send each word as a Kafka record to a Kafka cluster. Okay. And then I can do some manipulation with the words I'm saying. Okay. Still following. So, let me show you what I did. Still in the same code here. I got here another method, which is called, which has a sub path record. Okay. And what I do here, I have an emitter. Okay. That will send some load to a Kafka topic. Okay. So, I don't go too much into details. It goes to a topic called Craig event because I've been playing with Craig as well. So, I'm just reusing some stuff, but I'm sending that to a topic. Okay. And then I have a second application that will read this topic. Okay. And it will make some aggregation. It will count how much time I say the same word. Okay. So, for that, I need to start a second application. If I remember well, I put it there, backman, no, not backman, record it. That is something else I'm playing with. Word aggregator. Word aggregator. Let me start it. Let me start this. And let's see if it's working. Okay. So, let me start this app as well. And let me update now the captioning here. Stop captioning. Oh, yeah. The web hook is failing, but that's not a problem. Here I say record. Okay. I update the channel. So, it will go to my other point now. Let's still check that everything is working correctly. Yeah. My aggregator is there. Okay. Let me see. Let me open this page here, localhost 8081. Okay. Word counts. Oh, I forgot to... Yeah. I forgot to delete my previous stuff, but it should still work. Okay. You can see that is a test I did before. But let me try it. Let me start the captioning. If... Look, and now it's updated. You saw? I say if two more times. So, it updated to 18. Okay. And now 19 because I said it before. If I say if again, it will update to 20. If I say a weird word that I didn't say before, like elephant. Elephant. Tiger. Tiger. Somewhere here. If I say tiger, tiger, tiger, tiger. There he is. I lost my tiger. Where's tiger? Tiger. Two times. Okay. Oh, and now three times because I said it. Tiger. Six times. Okay. So, that's just to show you how we can do crazy stuff quite easily. Okay. So, I will share all the stuff for you. I'm sorry today we didn't play a game, but I really wanted to show you some live coding. Well, some live demo. It's been a while that I didn't do that. I hope you enjoyed it. Let me go back to the chat to see if there are some questions. Yeah. We have Andy say, hey, Kors say nice. Andy, that is sweet. Yeah. Son, hey, son, hey. Sorry, I don't understand anything you're saying. Maybe French. Exactly. Orange. French. I'm just curious. Let's see again if the orange. Orange. Oh, now French. Orange. Orange. Okay. So, please play with that. Okay. I will try to share the code that I did on my Quark. As you can see, it's really simple. Really simple. And for sure we can make this better. I need to make some kind of state object, you know, that can, every time that you enter this method, the state object change. So, it goes from instead of all these if skills, but I haven't yet think of all what we can do. Maybe a Pac-Man that I can play with my voice like up, up, right, right, right. But yeah, we can imagine some crazy stuff. Okay. Thank you everyone so much for attending the show. So, we will start, we will, oh yeah, and now we will be back in two weeks. Okay. I will let you know what the guest is. Okay. We'll be really nice guests again. Next week, it's tech talk. Okay. Just let me remind you how you can follow everything that is happening. If you go to dn.dev slash upcoming, and I will paste that in the chat as well. Okay. You can see everything, all the upcoming events that we are doing. So, right now, it's a show. It's now. Okay. So, next week, we have a definition talk, building streaming application using a managed Kafka service. Hmm. That sounds interesting. Okay. And by the way, remember, next week is also Red Hat Summit. Okay. On Tuesday and Wednesday, will be some great announcements, some crazy live demos and keynote demos. I'm also part of one of the demo on day one. So, be sure to be there. But did I paste the link? No, I didn't paste it. Let me paste that. There we go. Okay. So, hang on there. And yeah, enjoy the rest of your day or your evening. And please stay safe. I know we are going through difficult times, but yeah, that's also the reason of the show, to have some good time all together. And yeah, love you all and see you next time. Bye-bye.