 Oh, I'm live on Twitch. I can hear it. OK. Hey, hi everyone. Sorry, I just need. Maybe we are already. I just need. OK, awesome. Hey, awesome. Welcome, everyone, for this new show. My guest is already there. Don't worry, Daddy. I will bring you to stage in a few minutes or a few seconds. I'm just checking that everything goes well. Yeah, everything goes well. So say hello on the chat. Say where you come from. I love that. A lot of people are already there. I'm still in the garden. You can see that a different location. I moved from a few meters because it's starting to get hot here in the South of France. And I need some shadow. Otherwise, my tutor won't manage that. And I won't manage that. OK, so I'm really, really excited today because we have an awesome guest. We will talk about a lot of different topics. And after that, as usual, we do a bit of live coding. And we will play a game, a new game. Well, not a new game. You know I love Doom. We already played some versions of Doom, but I have a special version of Doom here. I leave you, you will see it at the end. OK, and let me see in the chat. We have James, we have Jordy, we have Orelie. Hey, everyone. So it's so glad, so awesome to see you all up there. OK, so now it's time for the interview. I need to go back to my console here and bring Daria to the stage. I have to click the right button. Yeah, there you are. Hello. Hey, how's it going? Fine, how are you? Good, good. Can you hear me just fine? Yeah, I can hear you fine. Oh, and you put your Twitter handle in the, awesome. You did it all perfectly. Yeah, usually I have a few minutes before the show. And but now there's a show just before. So I cannot do all this setup with the guest, but I'm lucky all the guests managed to set up everything right. And so it's all good. So I'm so, so happy to have you on the show. So what I always ask the first question is, who are you, introduce yourself, take the time you want. And so let the people know who you are. Sure. Hi, I'm Daria. I am a Java developer advocate at JetBrains. I've done Java development ever since I graduated from college. I joined IBM, worked on a product called WebSphere and Open Liberty. And then last year, I switched careers to developer advocacy. And I do a lot of content creation around different things and education. I love teaching, so I do a lot of education around things like, you know, JPA, Java, EE, Jakarta, EE. I just released something about Docker because I had no idea how to explain that well and did that. And I've really enjoyed the switch from a traditional developer career to developer advocacy. And I'm really enjoying talking to the developers and figuring out what they need. So yeah, that's just a little bit about me. I'm based out of Minnesota in the USA. And I'm originally from Egypt. So I've gone to different, you know, directions. And I have some background there. OK, cool. Super cool. And we will speak about advocacy. I'm interested in about the switch because I did also to switch the big switch last year. Because before that, I was already doing a bit of advocacy, but it was not official. And just to clear my memories, did we meet together in Agadir? Is that correct or not? I don't really know. Where? And where are you at Devox, Morocco? No? No, I wasn't. I was at DevNexus. Were you at DevNexus? No, no, no, sorry. Then I mixed it up because two years ago I was in Agadir and there was, I briefly, there was an IBM booth and there was a developer advocate. And I thought, but you know, I meet so many people. I know, I miss meeting everyone and seeing everyone. I was doing it as a side thing when I was lead and I kind of, you know, found the time to do it and now I can really do it, but I can't travel. So it's kind of interesting the switch. Exactly. No, no, well, Agadir, you quickly, I made a switch back last year in January. And I was part now, I'm now part officially of the advocacy team of Red Hat. And I was planning to travel like crazy. Now that my kids are a bit bigger, it's easier for the logistics. And yeah, I travel once time and then in March, you know, the world changed a little bit. And yeah, well, we became what we're doing now, live streamers. And to be honest, I enjoyed a lot as well. I can't wait to travel again to meet people, but yeah, I got used to it. But yeah, so about advocacy, what was the trigger for you to? Is that because you like to, you say you like education, you like to share, is that, is it related to this? Yeah, so back when I was, I worked on a product called the Migration Toolkit for WebSphere. And during that time, we did a lot of like Java migration stuff. And around that time, we were also doing a workshop at IBM about like speaking and all that stuff. And I was kind of intimidated by the idea of going off and talking to a bunch of people about what I do and like helping them and stuff. But one of my mentors, Kevin Sutter, really encouraged me to like apply for a, do you know Kevin? Yeah, Kevin's awesome. He was like, Delia, you should totally apply and see if you get in. And I did apply and I got accepted for my talk and I ended up going to Dev Nexus of 2019 for my first conference and I absolutely loved it. I loved people saying like this really helped me with like understanding what the problems with migration are gonna be. This is gonna help me with my, you know, application. Like feeling like you can actually impact someone's experience or make their job easier. Like I love that feeling. And I've always taught, you know, or tutored like math and calculus ever since I was in middle school. So I already loved like teaching people things and educating them. So ever since then I started going, applying to more conferences, I went to EclipseCon and I did a few and I've loved that. And then when I was kind of looking around for new opportunities, my husband told me, okay, you seem like you're enjoying this conference thing. Why don't you start like looking in that area? Cause I was looking at traditional development roles. And I was like, oh yeah, that's a good idea. I should totally do that. So I got in contact with Trisha and started talking and I've been really happy with, you know, what ended up happening there. Yeah, yeah, yeah, I guess that you are working in an awesome team there in Jet Marines together with Trisha and who else is part of your team? Are you a big team? It's just the four of us. So Trisha G, Malagupta and Helen Scott. Yes, yes. So it's like an awesome team and I'm learning a lot about that area because I feel like developer advocacy is not something you can like study. You have to like see it in practice. And I'm really grateful that I get to, you know, learn from, you know, the best basically. So it's been great. Okay. There are a lot of discussions about what is exactly developer advocacy. And I remember there was a Twitter space and you were, you tried to join but you had a, I think you remember this huge Twitter space that started a few weeks ago. But maybe for people, what looks like your typical day of work? That's a good question. As I asked that of Trisha when I was interviewing, I was like, what exactly do you do? She's like, that's a good question. Let me think. It really depends on the day. A lot of it has to do with basically trying to use the product that you're interested in, you know, getting feedback on. So for example, back when I was doing the Jakarta EE stuff, I tried to create a web application and use IntelliJ IDEA for that. So, you know, I went through the experience of a typical developer that's just trying things out. I tried it out, I wrote a bunch of code and then while I'm doing the product research part, I was like, okay, this is not working quite like I expected to. So I go and talk to the developers on the, you know, ultimate team, I would tell them, okay, here's what a developer experience would be and how can we do make this better? So a lot of it has to do with like being the first person to try something out and then giving some feedback or hearing a lot about, okay, a lot of people are running into this issue, how can we solve that? I was doing a lot of the new Jakarta, you know, namespace stuff and I had to go back and talk to the folks about like, by the way, this is not really working because not a lot of people had tried it yet. So a lot of it is like coding and doing this stuff and then some of it is, you know, content creation whether you're writing a blog or writing a conference talk or creating a video. I see it as like a teacher doing a lesson plan. Like, you know, how do I explain this well enough? What would I have wanted to understand in order to get started with Docker? It's funny with Docker. I was seeing that a lot of people know how to do a couple of things, but they don't really understand why they're, what it works. And for me, that was a really interesting kind of dilemma. How do you explain something well enough so people can use it and understand why it's working? Yeah, so. I love this challenge as well. And yeah, it's not, yeah, it's not easy. Like containers, yeah. We recently, we do a lot of content creation. We have deep dives, you call them. And we have really advanced deep dives and lately we started a deep dive called container 101. And it's more or less related to your video, but in one hour long we live, we explain. So what is behind the container? What is exactly the technology? So we don't dive too much, but yeah, it's C groups and Linux name faces, but you don't have to care about that because, and then slowly we show how to, and it's really interesting to build this kind of content. Yeah, isn't it hard to simplify? Like I found it hard to simplify. Yeah, yeah, yeah, it's really hard, but you quickly have the feedback. When you see people reacting and enjoying it, then you know you have the trigger. If you have no reaction on your talk and people ask you question that clearly shows that they didn't understand what you say, you say, oh, maybe I should rewrite my content then. But yeah, yeah, yeah. Yeah, my favorite response is usually like, oh, I never understood this before, and now I understand it. Like that's my favorite comment. Yeah, yeah, yeah, yeah, yeah, I love it as well. And so you do a lot of stuff for the community, also for customers I assume is there, is it a 50-50 balance or could you give- You know, I haven't officially talked to a customer since I started this job. It's more of like the developers that use IntelliJ Idea, which there's a lot of them out there. So a lot of times I just kind of look around and see, you know, if someone tags IntelliJ Idea on Twitter, you know, I answer questions around that area. If they're doing this and that, it's not a traditional job. Like, you know, for example, before I would talk to a web sphere customer and talk to them about open liberty and talk to them about specific products. In this case, it's just a lot of people in the community use it and ask questions there. And it's really cool to see, like, you can just kind of look anywhere, whether it's LinkedIn or Twitter or whatever, and or Stack Overflow, and see people use your product and see people's questions, feedback, all that stuff. And I think that's why the role is so important is that kind of connecting that to the product team so that they can make something better. Yeah, you are also customer number zero, as we call it sometimes, you know, beef. Exactly. Yeah, yeah. And as you said, there's so many people who are using IntelliJ that you have a huge community of people, it never stops. Yeah, that must be huge. I was just thinking about it, yeah, that'd be crazy. I love it, I love it because there's a lot of people that say, like, I'm solicited, they're like, we love IntelliJ Idea and, like, working on a product that people already really enjoy, that's such a joy. Exactly, yeah. Make it easier, I think. Yeah, it's really awesome. Or more challenging because, yeah, how can I make them even happier? Yes, and it's more feedback because more people are using it. So you get feedback from everywhere and anywhere. Yeah, yeah, yeah. Hey, I have a question from the chat here. Let me bring it here from Jordy Sola. He is asking, Daniel, any recommendation for getting over the imposter syndrome and start feeling your words are actually worth? Yeah, that's a great question about imposter syndrome. I know Aurelie is here in the chat as well and she has done some talks about that. But what's your opinion, your recommendation about the imposter syndrome? Yeah, that topic is extremely interesting to me because it feels, it seems like with tech, it's really prevalent. And for me, like, a lot of times, you know, starting a new career like this, I felt like, okay, do I know what I'm doing? Like, they're just gonna find out that I don't know enough about this or that or all the stuff. And I am definitely not gonna claim to be an expert in the area, but what has worked for me is that I take the time to appreciate the areas that I'm an expert in. And like, for example, like building expertise in Docker. Before that, I didn't know as much about Docker, but building expertise and looking back and seeing that I can learn any technology that I set my mind to and I can even help other people that way. So really focusing on what you do know instead of like what I don't know and getting control over your mind and these voices in your head. Like, you know, you're not good enough, you're not blah, blah, blah, all this stuff. It really helps to figure out why are they seeing the things that they are and is that true? Like, confront it, like, is that true? Do I not know enough about Kubernetes? I'm like, no, I know a little bit about Kubernetes, but if I really wanna sit down and learn about it, I can learn about it because I've learned so much about this and that. And really celebrating your wins, that's a big thing too. The other thing that has really helped me is having a good support community like around me. That's why I love this team because I get a lot of emotional support from them. I get a lot of mental support. Like they have my back. I highly recommend getting, you know, a good group or a good support group around you. Reaching out to fine mentors. I love having mentors and sponsors and all those things. But definitely getting control over your mind and when, and confronting those thoughts. So that, you know, you tell them, no, it's not true. Everyone around me, they know a lot about one subject and that's why they seem like an expert, but they've had years to build those expertise. So that's kind of what works for me. I'm sure a lot of people in the chat have a lot of good insight on that too. Yeah, yeah, yeah. I'm keeping it. Yeah, yeah, yeah. Let's just know. Oh, you got it. You got it. I'm just checking. I hear myself. I hope it's not me. No, no, maybe it's me. I clicked somewhere. Maybe, no. Okay. Oh, looks like he's gone. Okay. Anyway, awesome. Yeah, that was great. So let's talk a bit about, let's talk a bit about technology now. Your domain of expertise. So I guess we could start with Java. I assume you love Java, so. I love Java. Can you quickly tell us your story with Java, how it started, and where it went? Sure. Okay, so it's a little bit different. So when I was in high school, I took a course on programming. And to be honest, I didn't really pay much attention. I just needed to get that A. I remember we wrote some stuff and like God bless him, my teacher, Steve Strong. He tried really hard to get me interested, but then I kind of brushed it off and went to university and majored in engineering. But then I was sitting in a calculus class and I was thinking, oh God, I don't want to do this for the rest of my life. So I switched to sociology and criminal justice. So I did that for a couple of years. And then I sat there and I was like, you know what, I really don't want to do this for the rest of my life. And I was talking to one of my friends and he was like, Talia, I think you'd really like programming because you'd like math, you like physics, all those stuff, you should really give it a try. And then I ended up taking a class in Java, in Python, and in C at the same time to just try it out and see if I like it. I took the classes, I enjoyed the C class the most for me because it was a lot more like, here's exactly what's happening. There's no concepts of objects and all that stuff. And in my Java class, I would show up there and be like, I don't know what these objects are. I don't know what you're getting at here. Like C was a lot more straightforward for me. And I was thinking like, what is this inheritance? And like the teacher, he was a great teacher. He was like using toolsters to demonstrate different things and I just couldn't get it. But then, you know, goes on, you go on, I started working for my internship at IBM and I started really using Java in real life, like applications. And I was like, oh, that's what an object is. That's why he's an object. And it really started to click. And once it started to click and like really understand the concepts, it was beautiful from there. I've really enjoyed working in it. The community is just great. Like, you know, you look around and you see so many great people that want to help, just want to help. And I think that's something we take for granted, but not all communities are that way. There's like the Java champions really want to help out. The people from Oracle really want to help up. Red Hat, IBM, you know, all these people really want to help you out. And a lot of times it's, sometimes it's not really just about the technologies, it's also about the people. And I've just enjoyed both sides of it. I've enjoyed Java and how fast it's been, you know, improving and iterating. And I've enjoyed the people and how much they're, you know, inclusive and welcoming and all that stuff. So it's just been, it's just been really a good experience for me. Yeah, yeah, yeah. Yeah, as you said, we're really blessed with the Java community. It's a, generally speaking, yeah, good people. Because as you said, in some communities, and I won't mention any community, but it's, yeah, you can, it's more complicated to say it this way. Yes. Yeah, yeah, yeah. But let's move from Java to Java EE, I should say Jakarta EE. Yeah. And it comes from your time at IBM. So, and I saw in your Twitter profile that you are at Jakarta EE Ambassador. So that is everything about Jakarta. Yes. The first, so the first project I worked on during my internship was working on EJBs. Okay. And it's interesting because no one talks about that in college. Like you don't really talk about like enterprise technologies or, you know, EJB or JPE or any of that stuff. So I went off and like did a lot of research on just saying like, what are these EJBs and why are they important? So I worked on that for a little bit and then I started working on JPA and JPA, I feel like that's a, you know, it's EJB, you talk about it and people are like, oh, you worked on EJB, but JPA, you start talking about it and they're like, oh, JPA, I'm like, yeah, okay. Hi, Renee. And like Eclipse link and that's the, that's my first introduction to open source development. It was, you know, working on a project called open JPA and then move on to Eclipse link and then, you know, getting exposed to hibernate and all that stuff. So from my perspective, I was more of the provider than the user. So, you know, we would take in someone saying like any manager.persist or save or whatever you're using and figure out, okay, how do we talk to the database based on this really simple, you know, method call. And that's a lot of what we were doing is like, okay, underneath the covers, how can we not have the developer worry about this and how can we translate it to the database? And, you know, just framework after framework, you know, Java, even if you're talking about Spring, you're talking about whatever it all ties together because they're all using those standards. And I love the idea of standards. I love the idea of the developer just calls something and not worries about like what's happening in the background. They can just, you know, have an entity and they can persist it to the database and they don't have to worry about it. So I really enjoyed working on, you know, JPA and then moving forward, I worked on migration and then we started talking about, okay, what are we doing about this namespace change from Java X to Jakarta? And like, how do you start talking about developers about this? I don't think a lot of developers are really have started worrying about it because, you know, there's still some work to do in that space, we know with Jakarta E9, you know, you've got the namespace change but not a lot of new features were introduced, basically none. So we're not seeing a lot of people talk about it yet but I'm anticipating with Jakarta E10, you know, people are gonna really see what it looks like, you know, whether you're using Java EE, Jakarta EE, you're using Spring or whatever, everyone's gonna be impacted by this change. You know, you're not gonna be able to use Java X persistence anymore, you're using Jakarta persistence. But as I'm talking to the IntelJ idea folks, they're like, oh, we can definitely do something really quick in the IDE so you can switch that name because it's basically a find and replace but it will definitely break your app. Like it's a simple fix but it's definitely gonna be something that you need to do once you move forward. So definitely don't wanna scare people away but it's something that they definitely wanna keep in mind. Yeah, yeah, yeah. I remember the good questions about do we do the Big Bang namespace change or slowly the new AP? Yes, I'm really glad they went with the Big Bang. I feel like that just simplifies things a lot more. We'll see but I think that was a good decision. Yeah, we will see but yeah. We have to trust us all the developers. Yeah, if I mentioned Jakarta and then I think about Cloud and Java, I think about Micro Profile. Do you have, have you been involved with Micro Profile as well? I have had to have conversations that are Micro Profile. Since Kevin Sutter is my mentor, we talk about Micro Profile a lot. It's definitely something that I love talking about and advocating for. I'm kind of interested to see what the future of Micro Profile is with Jakarta and the switch to more regular releases and stuff like that. So I'm all for providing as much value in the standard space as possible. And I've seen throughout my career, I was thinking like, why is this coding taking so long? Like with the standards and stuff? And it's because you're going through a bunch of approval process and all the stuff. Like it's not easy to have a standard. So whenever I see people trying to do like standards but also quick, I love that idea. And I think that's great that Micro Profile is trying to solve the problem of like, you still want your application to not break with every version, but at the same time, developers really want new features coming out as fast as they can. So they can take advantage of them. So like, how do you kind of go between those lines? I feel like Micro Profile has done a great job at that. And there's a lot of great people involved in that project. So I'm always like fascinated by, okay, how are you gonna, how can you introduce this new change without breaking the old stuff? I'm really interested in seeing how that's gonna happen. Yeah, yeah, yeah. And again, about Micro Profile and Jakarta, there are some heated discussions on, yeah, Micro Profile is more flexible on standards and but how can we bridge those together? I remember a crazy discussion after a blog post from Sebastian Deschner. And I don't know if you remember, he wrote a whole blog post and saying, I don't remember the conclusion, but it was, or we kill, or we kill Micro Profile and we just make it part of Jakarta IE or something else, but yeah. But yeah, I'll go on. I was saying like, I love it when people are that passionate about a topic because you know, the conclusion is gonna be the best for the developers. So no matter what we choose, it's gonna be like, we've weighed all the options. No one's just making a one decision. We've weighed all the options and we're coming up with what we think is best for the developer. Yeah, yeah, yeah. I totally agree. And it's, yeah, as you say, it's a good conversation to have rather than do you prefer spaces or tabs? People can get really heated about it. And I find it funny, but some people really get mad about it. No spaces. Don't even have a conversation. It's spaces. I just lost half of our audience and they're like, it's space, it's clothes. Let me check in the chat. But yeah, moreover, what is your opinion for Java in the cloud? Well, you do a lot of stuff around Docker right now. So you can easily Dockerize, well, containerize Java application. Yeah, what do you think? Yeah, so it's, okay. So it's a little bit of a, you know, it depends the answer. A lot of times, you know, and I have had a lot of conversation with different customers talking about, okay, taking their traditional application, Java application and putting it in the cloud. And their idea of it is like, I'm gonna take this application, I'm gonna put it in a Docker container and, you know, put it on the cloud. And I'm like, that is not gonna, because if you have a huge application, you know, on premise, you move it to the cloud, it's not just gonna magically solve all your problems. And I remember doing like this workshop with one of our customers and, you know, they wanna do the latest thing, they wanna do all the stuff. And I had to stop and ask them, what problem do you have today that you're trying to solve? So a lot of times I have to like, stop people and say, okay, I know you're seeing everyone talking about the cloud and how great the cloud is and all the stuff. The question is, what problem do you are seeing right now that you think is gonna be solved by the cloud? Because if you have an on premise application that is well-architected, it's monolithic, it's works great, and you don't have any issues with it and it works, like... Yeah, why? Why even bother? Why, you know, why spend that resource there? You could spend, you know, adding to it or like creating something that attaches to it or whatever. But if you have a problem with your application right now, you have problem with scaling. It's not as easy. You have a problem with like, you know, finding out what the problems are in production. You have problem here and there and there and there. Okay, what architecture or what refactoring needs to happen to your application so we can break it apart a little bit more and take advantage of the stuff that, you know, Kubernetes provides and Docker provides and all that stuff. So typically when we talk about Java applications, a lot of times I tell people, okay, look at your application on its life cycle. Is it gonna be gone in the next two years? Then is it, it's not really worth spending the investment to put it on the cloud. But if it's gonna be, you know, here for the next, you know, five or 10 years and you're actively developing on it, you're actively doing future development and it's taking forever for you to get the future from the developers, you know, from coding basically to production. Yes, you should definitely revisit your application architecture and figure out, okay, how can I break it up into small microservices? How can I deploy in the mindset of cloud? Not the mindset that we've had before. You've got to shift your mindset. If you've got to understand in these areas, you know, what's gonna take the most advantage, how can you take most advantage of the advantages that you get with cloud? So when I, when people ask, you know, Java on cloud, if you do it right, it's great. But if you go into it, you just want to do cloud, that might, you might want to stop and think and okay, what problems am I really trying to solve with my application? Yeah, yeah, yeah, great. And typically at Jetwains in MTVJ, are you providing tooling to help people that would like to migrate their Java application to the cloud like, I don't know, easily providing health probes or, I don't know. Do you have any tooling around this? Yeah, so we're, so first we have like the Docker plugin. And I've done, there's a video that should be going out here soon about like how you can have, you know, you can look at all your Docker containers and images and all the information about your containers. You can even navigate into your container, look at what's there and all that stuff, which I feel like is really helpful. And then when you're doing development too, it's nice to have it all in one place. So we have a lot of the plugins available for that. And then we have the Kubernetes functionality as well available. A lot of it has to, we're very developer focused. So we're always thinking about, okay, from a development perspective, what's going to help the user most? So for example, when you're writing a YAML file, you know, people complain left and right about YAML files. I was just talking to the developers about how, okay, it would really be nice if IntelJ IDEA caught this. You know, and we were talking about ports and putting quotes around ports and all that fun stuff. How can we make it as easy as possible for a developer to take their application and basically containerize it? And beyond that, they can figure out their, you know, how are they going to deploy it and all that stuff. But from a development perspective, what's going to really help is being able to easily change your application, see the change right away, rebuild your image, run your container and then go, you know, forward from there. So we're definitely, if anyone has, you know, any suggestions on features that you think will really help you on your cloud development needs, please, please, you can message me or you can post in the chat. We'd love to hear that because that's an area that we know that is very important and we're trying to improve on it as much as we can. Yeah, yeah, yeah. It's the same at Red Hat. Well, we are, when it comes to tooling, we're not exactly competitors because we provide tooling for all the IDEAs and to DJ visuals to your code and- We're happy friends. Yeah, yeah, yeah. But I love it. Our tooling team works for both, when they deliver a plugin for Quarkus and extension for Quarkus for VS Code, they immediately release it also for EntityJ. But yeah, and that's also my challenge as an advocate, how to make this step easier for a developer to put his workload into the cloud. And yeah, one thing that I really like in OpenShift, so in our communities, is the latest change that we have, you can now drag and drop a drawer file into the web console, a bit like when you upload a video on YouTube. But now you drag and drop your jar file and yeah, the platform containerize it for you and then create a deployment. And yeah, so that's a cool feature. That's awesome. Yeah, especially for me, for us as advocates, that's awesome to demo, you know. Yeah, and make it as easy as possible. Exactly. I love the analogy with uploading your video to YouTube. You drag and drop it and while it's uploading, you enter the details and here's the same. You say, okay, that's my end point, there are my health probes and yeah, it's uploaded. Okay, and cool. Oh, I'm watching the time, but yeah. I want, it looks like you like to build software, but you also like to build other stuff if I look behind you. A lot of amazing stuff. I will show that to my son right after in the replay. Lego, your friend looks like. So I love Lego based on also my husband's love of Lego. So my husband is a big Star Wars fan and he's gone into collecting Lego and all that stuff. This is actually his room, but I was like, I want to do my show from here. So I've gotten into a lot more building Lego together. It's such a nice fun, like friends activity too. And I love Harry Potter. So all of the Harry Potter sets in the top here, I built those. So we have, we have some in the corner here, we have some like Disney, Frozen, Mulan, women and astronauts and other like Marvel because we both love Marvel. So we kind of take turns building the Marvel sets. We probably have a lot of Iron Man because there's like every set sometimes comes with Iron Man, sometimes it doesn't. So in the Stranger Things, like we have a bunch of, it's like, what do we like? The big house of Stranger Things? Yeah, yeah, we hit it. Yes, and it flips. You can flip the house. Yeah, yeah, yeah. It's so cool. And I love the fact that it's so sturdy. Like no matter what happens, like once you build it, it's not just gonna break on you. It's a very well built, well, you know, toy. But to us, we love it. I love watching a Harry Potter movie and building my logo. It's like the ultimate relaxation time for me. You watch Harry Potter while you're building the set? Yes, it's perfect. My son does exactly the same thing. And he did the thing with the Stranger Things house. He put on Stranger Things and he started building and yeah, yeah, yeah. And yeah, it's awesome. The latest thing I built with my son together was the Saturn work cut. Now the one that went on the moon is this huge. It's amazing stuff to build. That's awesome. Yeah, and I told my son, because we had a discussion just before the stream, and he said, oh, you have to ask her if she's planning to buy the new sets about Harry Potter that come out in June. I have no idea about it, but you probably know. Yes, there's a couple that I have my eye on and we're gonna definitely pre-order a couple of them. I think one of them is like a life-sized version of, not life-sized, but like a big version of Harry Potter and Hermione Granger. And that's one that we got. And yes, so it's funny. Whenever any new ones come out, we're always looking around and figuring out which ones we want. Now the challenge is where do you display them? Because after a while, you kind of start running out of room. So, yeah, good luck with that. Yeah, yeah, yeah. No, no, awesome, yeah. And I know my son is missing one, but it's the most expensive one. It's the street. I don't remember the name of this Harry Potter set. It's like the big castle. Not the big castle, but the street. Oh, yes, yes, yes, yes. I don't remember how you say it today. Yes, yes, yes. It's like four buildings and they take up a lot of space. And I told my husband, I don't think I can get that one. Because it's going to just take up so much space. And I think it's sold out. And yeah, but yeah, he will dream of having this one. So, okay. Well, we spoke a lot, but it's not a problem, because it was a great discussion. Let me just double check here in the chat. So, Jordy, thanks for your answer about imposter syndrome. He says, you mind around, I'm good enough. The idea is hard, but I would take the advice and get surrounded by wonderful people. Yeah, yeah, okay, so that's it. James is asking about the dragon drop jar. Yeah, James, that is in OpenShift 4.8. So, to be released in two weeks or something like that. Okay. It's time for me to do some live coding and play a game. I know you have something after that. But anyway, it was really an awesome discussion. I love chatting. Thank you for having me. Yeah, it was really great. People who can follow Daria on Twitter, her handle is between the... How do you pronounce it? The brackets. The parentheses. Yeah, yeah, yeah. It's between Dutch, French, and English, so sometimes it gets a bit... I'm impressed. Yeah, like it's switching languages, especially when you're talking about tech. I'm always impressed with that. Anyway, thank you so much. Hopefully next year, probably when we will be able to travel, we will meet at a conference, I'm sure. I will take some pictures of all the sets from my son. Yes, hear that. That would be awesome. Thank you so much for having me. See you next time. Bye-bye. Okay, everyone. That was great, as usual. I'm really lucky. I always have awesome guests, and we also always have such great discussions. I'm running a bit out of time, but it's not really an issue. You know what? I want to quickly do a live coding to take five minutes, and then I will show you another game, boom, running on Docker. Doom 1, the old one. Multiplayer, okay? I discovered that yesterday. People from Cloud Fair did that. And I say, wow, let me try to deploy that on OpenShift, because I try to deploy everything on OpenShift, okay? So let me share my screen. Let me share my screen. So we should now be in inception mode. Yes, here you see my restream. Let me check the chat here. James4.8 is in two weeks. Okay, okay, awesome. You know what? I just, before we play the game, you probably know Quarkis. You know that it's my favorite, it's my favorite Java stack, to build applications. And there's been Quarkis 2 alpha release, released three weeks ago. Okay, it's still on alpha, but you can already do some crazy stuff. Let me just create a live, make a live, live show, something like that, okay? Let me go there. Let me create an application using Quarkis 2.0 alpha, okay? I can do that. Let me increase a bit this screen. Clear. There we go. Here. And I do that using the Maven plugin, okay? So here I'm using the alpha one. Maybe there's an alpha two. Let's stick to alpha one, okay? So that will create a new project for me. I just want more feature that I want to show you. So let me put here, that's Sabi, live show coding, show, show coding, show coding. It's a snapshot. Rest easy. Yes, yes. I can keep all the defaults, okay? Let me go into that and let me open code with this application. Empty application that has been created for me. Let it give it some time to start up. So nothing has changed in Quarkis 2.0 for the structure is still, you know, a classic Maven structure. It's taking some time here to load my, there we go. Okay, it's running. So let me open the west endpoint that has been created for me. And what I will do now is just start my application, okay? Using the Dev mode. You all know the Dev mode, okay? And I do MVN, Quarkis, Dev. Okay, there we go. That will start my project, you know, in Dev mode, that means that I can change stuff, add libraries, change my code. But we have a new feature, which is called continuous testing. You might remember when you create a new project, you have some test that has been created for you, okay? By default. And what you can ask now in Dev mode is to run your test every time that you change the code. So here it's running my test, okay? My test path because it's checking on hello west easy, hello west easy. So that's working, okay? What if I change my code? So I change here hello to something like instead of hello west easy, hello. I save it and look here what will happen. Look, my test fails. Yeah, immediately run my test. So what I can do is just go into my test, for instance, and I can fix here the test. Let me fix the test. I save it and look at this. Now all my tests are pressing. It even works if you add code, okay? So let me add a new method here. Let me add a new method. There we go. And I will call this method. I will put it on the pass FR, okay? And I will call this method bonjour. Okay, and here we return bonjour. Okay. I saved that. He will run the test, but there's still only one test, okay? Because I haven't written a test for this. So let me add a test. Let me just decrease once. Yeah, that's better. There we go. Let me add a new test. That we will call hello bonjour end point. And here we say we want to test this new end point slash FR, and we should have bonjour. There we go. And we save that. And now you can see here in my terminal, test all pass to pass where run, okay? And again, I can break it if I want. If I say here, hola. Break it. And I will have expected this hola. Actual is bonjour. Just that I wanted to show you. Continuous testing. It's still in beta. But it's really smart. It only runs if you just change one method that will just change the test method of this method, for instance. And yeah, my role is to make developers happy to improve developer experience. And these kind of features while are awesome, okay? That's all I wanted to show you. And I think there are some mosquitoes here. That's going to be fun. Week after week, there will be more and more mosquitoes here. But hopefully I will have fiber and I will be able to go back inside. Let me stop the app. That's all I wanted to show you for live coding. And we have 13 minutes left. Awesome to play the game. Let me see a bit in the chat if we have something. We have hello. Okay. Continuous testing is an interesting feature. Yeah, I agree. Okay, let's talk about the game. So yesterday I was on Twitter and I saw a treat coming along. I don't have the treat here right now. But basically someone say, hey, we at Cloudflare sorry, we managed to create a version of Cloudflare. So you can play your DOOM. And not the new DOOM but the old school DOOM. The old school one, the shareware version which is open source, by the way. And let me share that with you because the blog post is really interesting. Let me put there. You can read it. They really explain something great about putting your code on the client or putting it on the server. There's a third way with Cloudflare. It's between the server and your client. And this way you're closing to your client. You can put some secrets. Anyway, really interesting to see. But the interesting part is that at one point you read this blog post and then they say, but you know what, the code is available in this repo where is repo? Let me search for repo. The open source code an instruction to compile and run the last DOOM locally can be found in this repo. So I click there this morning. And you come on this repo. I can share that with you as well. And I say, let's try it. Let's do it. And you have some great some great instructions compiling that is the last DOOM. But you also have to do other stuff. And after struggling a bit because I never compiled with WebAssembly, I never did that. So basically it's a special version of DOOM that has WebSocket supports. And that you compiled with WebAssembly. And you end up with a GS file and you can put that in a Web app and you can have DOOM running in your browser and it has support for WebSockets so you can make it multiplayer. So Cloudflare did some crazy stuff. They used some specific stuff from their platform. But you can also run it locally. And I managed to run it locally. And I say, okay, now I have it locally. I want to run it in the cloud. So what did I do? I took my project here. Let me go to my project. That is a, so it's a Node.js project. I say, oh, you know what? Let me create a Docker file. So I created a really simple Docker file from Node 16 and here I do really not so nice work. I just put everything from the folder in my container and I run this script router.js that is supposed to run for if you run it locally on your machine. But I say, now I have a container and you know what? I also have a cluster. Let me try to deploy this stuff, okay? And if you take a look here. So it's my pod is running here. I've got my service. I had to do some stuff here because we have one port for the web app, but also one port for the WebSocket connection. So it's two different ports. So I had to adapt the service a bit. But let me see here. I got this URL here. Let me open that here for now. Port 8000. And look at this. I got my doom running in the browser and I can multiplayer game. I do that and I call myself here a sebi and I do go. I only tried this match. And a link has been created for me. Let me copy that. Let me go to next. And now we will enter the lobby where we wait for other people. Let's see here. Not to open shift. I see four people. I don't know if it's limited. Let's see. If it's limited, you can start another server because it's available. But let me copy the link. No, not in this one. Let me copy the link here. So if you click this link, you should be able to join the game. Let's see if people join the game. Let's wait a bit. We still have some time. Don't be shy. Click the link. Hopefully it works. Maybe it doesn't work. I made some tests. I don't see anyone joining for now. Let me see in the chat if people. People that are still there, click on the latest link. Join me if you want to play against me in Undoom. Let's give it two minutes. The thing is, once I start the game, it's a demo. People cannot join after that. I guess people might have an issue joining the game. Because I see no one joining. Let me see again in the chat if something. Other players. Oh, you have a waiting for other players. Okay. Why can I I should be able to see you here, people. That's the issue. That's not happening. Okay. Maybe it's not getting updated. Waiting for other players. Still here waiting for other players. Okay. You know what? Let me try the game. Let me play the game. We can go on the official site where they did it. I just want to show you. We can really play the game. There we go. I think no one is here. Let me take the rocket launcher. Yes. I almost killed myself. Let me go here. Okay. Okay. I'm not sure people were able to join. Let me take Can I do pose here? Okay. Let me see. Yes, since none there. Okay. You know what? Let's try it again. We have still five minutes. Okay. Start multiplayer. Okay. I go there. This match. I copy the link I do next and then I share it with you. Let me see. So that's me. Oh. Waiting for other players. Hmm. I come back to the game now. Hmm. Yeah. I knew there was a risk to do that. No luck. No luck. Yeah. I'm sorry. You know what? I will be working on that. What we can do now. What we can do now is going to the official site. Silent. Silent. Something silent. Silent space marine. Okay. Let me go there. Okay. Let me close this one. Let me start a multiplayer here. Let me do that. Let me try this one. Once more. See if people can join on this one. That's the other. Yeah. It's right because I tried it myself this morning. I did a lot of changes. I'm not sure what happened. Let's see if this one is working. Oh. Next. Okay. Let me see if this one works. Anyway. It's still interesting. Interesting experience for you people. If you want to try to compile this old school doom, you need the shareware, the what? W-A-D file. You can grab it for free because it's a shareware. Oh. I got someone here joining. Oh, Sabine. I love it. Anyway. It's a really interesting experience if you want to run it locally. Okay. We are all there. So it's limited to four people. Awesome. Let's try it. I can... If I can see some people there. Oh, I see people. There's no scoring system. But since there's a WebSocket connection, you know what? I will integrate it with some... Oh, people are... Someone is attacking me. Oh, I probably have a second one. A second window open. I'm really slow for it. Okay. Anyway. I will integrate that with Kubernetes like deploying pods when you kill people. Oh. And now the game... The game is taking a lot of resources. But anyway. You know that I love this kind of integration. I was happy to manage to deploy it on my cluster. But I still have some stuff to fix. Maybe it's blocked some ports or blocked or something like that. I have to find this out. You know what? Let me stop here the screen share. You can still play. Where is my screen share? The screen share is here. Let me stop the screen share. Let me put back in the big screen. So anyway. I hope you enjoyed this show. I enjoyed a lot. I enjoyed the discussion with Dalia. Then we could see some great features of Quarkis 2. And there will be more. Just one specific feature I wanted to show you. And yeah, Doom. Yeah, I feel a bit. That's also where all humans and I just experiments and stuff. And yeah, expect. Maybe in two weeks I will have a way more nicer version integrated maybe with other games and etc. I love to do that. And that's it. Next week is Tech Talk with Itzan. And it might be possible that I will be we are still discussing that. On Quarkis 2. By the way, maybe I see you back next week same time. But as a guest. Please stay safe. Have an awesome end of the week for people here around in Europe. Enjoy your day off on Monday. Love you all. Stay safe. Bye bye.