Lightning Talks 2

Speaker 1 [00:30]

We have less people than yesterday. I want more people inside. Come on in, come on in. We need to start. We're about to start. I really want to be on time today. Brilliant. Five years less. I'm going to call up you on stage. Nice. If you need any announcement, you can start coming up here. If you're doing event announcements, please, can you come up on stage in the meantime? So we're going to do that bit super quick. Okay. Tom is going to come at some point. He's been running around probably. Okay. Tom, come up on stage. So we're getting ready for the announcements in the meantime. We also received a submission about a conference in Africa, PyCon Africa. Is that person in the room? If it's not, we're going to skip that. We can wait later. Yeah, absolutely. Are you here? Fabulous. Okay. You're going to go first. When I finish introducing the lightning talks, you're going to do your presentation. It's basically already there. All right? You can wait here. Thank you very much. All right. People are just pulling in. Valerius on his place. is on time. Every other is not. So, folks, are you ready for the best session of the conference? Thank you. I really need that. All right. Lighting talks. I'm going to be super brief about introducing the session for those of you not being here with us yesterday. Lighting talks are five-minute talks, zero mercy. Anyone can sign up. Any topic is allowed. Python, data, kittens, the universe, whatever you want to talk about. Anything that ruined your weekend is also very acceptable. Five-minute timer. We're going to have a timer and a timekeeper. I'm going to introduce your host very soon. Beginners are very encouraged. This is the friendliest stage of the conference. I'm your host, Valerio. Yesterday was the chance caster, roll over the enchanted dice, I introduce Beaker, I roll the occasional die, and remind you that the best talks, like the best spell, have a randomness baked in. I also have with me the fabulous Johannes and Lisa. Johannes is going to be the timekeeper, and he's going to be very merciless, as yesterday. Lisa, the torchbearer of Django Girls, carrying the Django Girls torch into the lightning storm, here to cheer the loudest when a first-timer steps on stage. And also, let me introduce our special guest from the future, Andy Allora, visiting us from a different time and space. Hello, hello. We are from 2077. We are here to witness a historical event. Someone in this room, we cannot tell you who, will be responsible for preventing the AI apocalypse. up. Good job. While we're here, we will be taking notes. They are for future historians. You would not expect to read them in your primitive 2026 script, so don't worry if you don't understand what we're writing. All right. Thank you, Andy and Laura, for being with us. You're wonderful. Okay. Something to tell you, everybody who submitted a Zlips for their proposal received a mystery constraint card. It's like something they can play with. Every speaker has this secret card they need to do if they want to during their presentation. Its card is a tiny harmless rule they have to wave into a talk. And your mission as the audience is to spot them and clap louder if you spot it and cheer if it's weird. But you don't win anything apart from smug satisfaction if you find them. I just want to say that We had today 43 submissions. So can I have a huge round of applause for everybody? This is really great for all of us. We're really appreciating you wanting to do lighting talks. Sadly, we can't be accommodating everybody, but we're trying our best to do as many as we can. That's why I'm rushing a little bit. One minute left. One minute left. Thank you. talking about pineapple pizza, this whole thing. I can skip that. I'll leave it to you. Warning, if you were not here yesterday, shenanigans may occur, and if you were here yesterday, more shenanigans are actually occurring. And now, I want to pass on to two minutes announcements for community events, and we have Pike in Africa. Please come on in. All for you. Good evening to you all. My name is Sumayana Lukwago from Uganda and this year we're going to be hosting PyCon Africa. PyCon Africa has been happening all over Africa. Last year it was in Johannesburg and this year it's coming to Uganda and I'm here to give you reasons as to why you need to be in Uganda this October. So first I would like each one of you to join us as we celebrate Python and celebrate the community that we've built over the years. PyCon Uganda started in 2023 and we've continuously hosted PIKE on Uganda 2023, 2024, 2025 and this year we are glad to be hosting PIKE on Africa 2026. So it will be happening from the 7th to the 11th of October at Speak Resort Munyonyo. Tickets are live and you should be able to still submit talks. CFP is closing tomorrow. Yes, so Uganda is just located right there in East Africa and PIKE on Africa will be hosted in the capital city of Uganda, which is Kampala. And we have a vibrant Python community in Uganda that's PyCon Uganda, then we as well as have PyLadies Kampala, which holds its sessions every other single month. So I look forward to seeing you in Kampala, Uganda. You can submit your talk, you have about eight hours from now, and then you can as well as get tickets. Yeah, you can as well as purchase tickets so that you get to see me in Kampala as well as you know we get to see each other again so we can connect via that link thank you so much i look forward to seeing you all well done amazing conference i wish i can go but i know not everybody can go to a conference and who here know why it's at mtv okay i know your age now thank you um yes what if we mix uh you know 90s MTV with the Python. So we have done this earlier this year. And it is actually an online conference. So I know yesterday we talked about how close each conference together are, but this is right at your home. So you can watch it on YouTube. And please like and subscribe. So it happened earlier this year, but, well, it's YouTube. So we can have recording and watch it. So scan this QR code and watch it. We have a lot of amazing people like if you can spot the cartoon version of them then then they are our speaker So please scan it watch it and like and subscribe. Thank you Hello everyone, I have a quick question who's ever been to Europe I think before Okay, a lot of people but a lot of people haven't gone yet Europe I think is a seven day long event It's been traveling Europe for the past 25 years every year since 2002 and we're having a 25th anniversary this year We're going to Krakow in July 13 to the 19th. It's two days of tutorials three days of Conference talks and then two days of sprints and workshops more than hundred talks and five tracks, etc You can go to the website and then see all of that this year We're also hosting a language summit, which is an event. We're bringing from Python us for the first time back to Europe. We have a bunch of other summits like a Rust summit, Wasm summit, a packaging summit, PyLadies day and then the if you've ever been to the organizers open space at EuroPython this year is going to be upgraded to the full day summit and also you might have heard about EuroSciPy yesterday. This year we're co-located at the same city at the same time and we have a joint sprints with your SciPy, and with that, I'll leave you with Oleg from our sponsorship team. Yes, so we still have some slots left for the sponsors, so if your company is interested, please check our sponsorship website, but this year we're offering a special package for startups. It includes a three-day space in the exhibition area, and this opportunity was specifically designed for startups to show their products, connect with the Python community, and gain more visibility. So if you're a startup and would like to apply, please fill in the form on our website. But keep in mind that this is a limited offer because we only have five slots left. Okay. We start the ticket sales next week as well as publish the list of the talks. And if you have any questions or require some additional information, you can check out our social media or europath.eu website. And we're looking forward to meeting you in Krakow this summer. Thank you. That was Q right in time. I forgot about one more thing, that we also have a keynote. If you want to go to Poland earlier than July, we also have a Warsaw Python Pizza on the 9th of May. Who ever been to the Python Pizza event before? I see some hands, but not enough. There's some organizers from Hamburg Python Pizza in the audience. I've seen them before. It's a one-day event, single track, 10-minute talks. The CFP, unfortunately, closed yesterday or the day before, but the tickets are coming soon. So, if you want to visit Warsaw on the 9th of May, 2026, that's Saturday, please scan the QR code. Everything else is on the website. And, yeah, that's it about the Python Meet stuff. Thank you. Sorry. Hello, world. My name is Thomas. I have like this flyer. You might have found it already scattered around the venue. Like this flyer is an advertisement for one of the best conference concepts. It's called Python Barcamp. Python Barcamp is an on-conference style conference, which is mostly a weekend long, and it's really nice and you should check out. Normally people who join are hooked and will do their own Python Barcamp in the city. So we have four Python Barcamps currently in Germany. You see it on the Germany map, which Johannes designed and pinpointed every city location where we're hosting it. So please check it out. Pick up the flyer at the registration desk or the lounge. Please leave it there and have a great time. Thanks. Thank you very much, everybody. And that's it. Let's get striking. So we're going to pick who's going to go on stage now. And then the next one. We're going to pick two. So I can have one. You say the first one. Joining me on the right side of the stage will be Larissa with how to get into data science. Just the question, not really the answer. And after that, could Irina please come to my side for FCA? You can already set up here. All right. Irina? Irina, are you here? Okay. While they set up, can I ask in the back end if they project this link? We have a story to catch up. So if you can scan this QR code in the meantime, I have a very important question I need to ask you. It's sort of the same kind of questions I asked you yesterday, but if you were here yesterday, there would be more surprises. All right. So while they're setting up, let me reveal the question I really needed you to answer. How would you describe your mood right now? Sleep-deprived, that's interesting. OK. Getting answers. Ba, ba, ba, ba, ba. Ba, ba, ba, ba, ba. All right. Let's reveal the winner. Sleep-deprived. OK. Thank you very much. Take it away. SPEAKER 1, SPEAKER 2, SPEAKER 3, are you ready? SPEAKER 1, SPEAKER 4, SPEAKER 5, SPEAKER 6, take it away. So okay nice first lightning talk and as my first lightning talk as well Take as many as much time as I can no um I What I was not sure if I should present this project, but I decided if I would not talk about it And then nobody would know and so I'm writing a book about how to get into data science in Germany, because I studied political science when I decided my bachelor's, I thought political science pretty cool, and then I saw, hey, statistics is much cooler, and then I somehow turned into a data scientist, so back then I had some issues, and I made maybe some mistakes, and I had some different opinions that I had to learn how companies work, how data science in companies work, how corporate life works in comparison to research and in comparison to university. So, for example, I thought, hey, I need to be super into tech and I need to be super deep into all kinds of topics and I need to be a developer that identifies as a developer. and then I realized, hey, I can also be something else, like I can maybe explain the business, how data science works, and a colleague of mine will do all the crazy stuff, feature engineering. So yeah, I learned a lot of things, and I want to learn from you as well, because I'm not here for the answer, I'm here for the questions. So I want to ask you, as I think here are a lot of people that want to transition into data science, that already did this transition that want to share their experiences and want to maybe discuss with me some of their experiences because also my journey is now seven years old and things have developed since then. So I just wanted to let you know you can contact me. So please, you will find a contact form here and I'm looking forward to your messages. I want to discuss with you about your opinions and about your questions, what you want to know about how to get into data science in Germany. So, thank you. Larissa, while Lisa is pulling the next card, would you like to have one of these special edition Schnitzeljagd cards? They're not the same. You get them. Nice. It's me! Well, I've pulled a test, not a real entry. Somebody is testing the box. Are they testing the box in the future, too? It was not us. Marsha Cabral, afraid to make public speech. over here, Marcia. But now we will hear about FCA, I guess. Hi, my name is Irina and I also have a question for you and that's actually a question for you and I'm not going to give an answer, although, unlike the other question, the answer exists. And I have a task for you. I want you to come home after the conference and relax and everything and ask chat GPT, what if formal concept analysis or whatever other assistant you can use or even Wikipedia or whatever you like, because what else are you going to do? Are you going to learn about agent stuff? Everyone is doing agents, and also there's a danger that it's outdated in a week or tops half a year or whatever. Formal concept analysis is here since 1980s. No one is doing it, but you will. And also it was invented in Darmstadt by Rudolf Wille, and actually his great-grandfather was a great friend of Otto von Bismarck and was involved in unification of Germany in 1871 and he always said we need to formalize a concept of unification. So then Rudolf Wille made a step forward and formalized a concept of a concept. So if you do have data, and you need to ask yourself if you can represent your data in this form, when you have objects, you have attributes, and you have relations between them, then you can try to FCA it, and what will you get? Maybe you'll get a graph, an insight from this data, or maybe your brain will explode. So actually, last year, I gave a talk on FCA here, and then one of the questions was, what about FCA and hierarchical clustering? And I was answering, like, maybe worth looking into that. And then accidentally, I got an ongoing project where I needed to take the data, and it was already structured. It was categorical. It had categorical features, and I needed to kind of understand more about the data. There was the existing categories, the subcategories, and I needed to find other clusters which are sub-subcategories and also with some interpretation, and if I would use some hierarchical clustering, I would need to define a distance, and then I would get a hierarchical tree, right? And with formal concept analysis, I do not need to define any distance. I can have all possibilities of clusters in this hierarchical structure, which is not actually a tree. It's a lattice. And on top of that, we have a trivial case of clustering, one cluster for all data. At the bottom, we have the unique combinations of the features of the very specific clusters, which can be like almost all your data points or whatever depends on the data. And there you have a structure in between from most general to most specific. So it's actually really great as a data mining tool. And Lattice is like all possible trees but together. So my question remains and what is FCA is your job to find out and to find out how it What applies to your work? And I would like to ask personal questions to people on the stage. Will you Google or chat GPT what is formal concept analysis? Well, I mean, I learned formal concept analysis in Kita. It's very popular in 2077. Are you from Darmstadt, maybe? I mean, I've been here in many timelines. This is a great version of it, though. I love it. Will you? I don't really know. Are you going to do this or not? I think I will do. Thank you. I'm going to do it. Of course. You can pick one of these nice cards. I think Marcia was so afraid of speaking that she didn't show up. So now we need two of them. Yes. You go pick the first one, I guess. On the right side of the stage, this is Lingara Jaya. I got it. Hi, ladies and gentlemen. Come meet my family. And right after that, please come to my right side, Jashita Jain, space between biology and coding. Are you here? Yes. Please come to the right. All right. While this sets up, I need your attention for more shenanigans. Can I have the screen, please? I started the timer too early. Come on. Okay. It's working. It's working, it's working, it's working. Best Python web framework. I've seen this before. Sometimes first isn't always best. You might be surprised by the answer here. Shall we read it? Do you know from the future the winner? Well, I know it's not who you expect. Aha. It's going to be bottle. Right. OK. Take it away. What's worst is best. Exactly. She's from the future. Do we need to pull another one? I think we pulled another one. Do we have the next big one? Oh, no, she is here. Come to me, please. Come on stage. Come on. Don't worry. Thank you. Do not be shy. I see from the future you did an amazing job. Oh, nice. Now we need to get the next slides on. Here we go. Just a minute. Yes. Okay. So how many of your students over here? Raise your hands. Okay, not many. Okay, today I'm here to introduce you to my family, the extended ones, brothers and sisters, next to kin and whatnot. So a moment of gratitude to the universe and the almighty. I wouldn't be here if it weren't for them. So, could I have an applause, please? Thank you. You can use the seat dongle on me right now. Cutting razor. Seat dongle, HDMI. So, building the anticipation. And they are my friends, ladies and gentlemen, are them. So, all of us know, we all know, all of us have been using it. So, what would that make us, all of us? Silicon siblings, maybe, aren't we? Definitely. so these are the newest members that I've been using and currently trying a little bit some of the old fellas so I don't remember most of them I don't know most of them but then they've been there even before I could ever exist so I think we have to have some tribute for them as well and some of these so what are they doing Netflix, Spotify YouTube and Instagram and all that they're just for the vibes come on we wipe code and then spotify just hits different when you wipe code it puts you to a zen mode doesn't it so yeah and yeah all the places that i plan to be this summer so beautiful switzerland oh this is lapland and these are the places that i haven't been but i plan to be this summer. This is Barcelona, I guess. This is Dubai. Oh, this is Aurora. Everybody knows. But the places I am, fortunately or unfortunately, Monday mornings. Yeah. The general channel. We would all know. Yeah. Teams is not enough. We also have to have Google Meets. And that one person who always has his face visible, that's my CEO, by the way and this is the team so they're also fun guys they're they're not the bad or boring so don't be deceived it's not this happy always and yeah teams is not enough meets is not enough we also have to huddle nowadays a little bit you know one-on-ones that's also needed and yeah we got to do our personal stuff as well this is also there and I've redacted some of them but then it's okay and one is not enough we got to have two who would just the freebies right yeah free storage and all that and here the places I mean this one could be a little I think we could this is an exception I like to be here so it's okay and this is the family that I currently belong to Expedial and notice the spelling of the family so it's if they call you family it's not always that so beware it's it's deceiving and this is my actual family unlike the other guys my people they are a little concerned about privacy and things like that so by the way I myself I'm an MLM engineer I work from home completely and that's the reason and these people actually do mind privacy and stuff like that But, yeah, I'm looking for students for Heavey positions and research student positions. So if you are looking for a new opportunity, you could just scan my QR code over here and then just hit the connect button on LinkedIn or reach out to me. That's Xperia. And this is, you might be wondering why the slide is. This is the only serious slide. This is for my friend over there to take a picture of me. All the other slides were not nice. So, cameraman, DOPs. Yeah, made the best out of the time, I believe. So this is the one thing that mattered. Thanks. That's it. That's my bit. William. I'm bored. Oh, you win a card. you're missing the best bits alright let's take another one meantime I have questions again can I have the screen please fabulous and while we do the question there was a situation we didn't have in USB to HDMI hub and the great people from the venue had a solution for all our situations can I have a big applause for them oh yeah Before revealing the thing, I want to ask Joachim Schmidt to the stage for working with age-diverse teams. Are you here? Are you here? He's coming. Brilliant. Brilliant. All right. Get ready. I need to know, tabs or spaces? Whole wars were fought over this. Very brutal wars. In the future, an entirely new character was invented. What? Tabs? What? I have something to tell you, though. Life and timelines, always chaos. What does Python look like in the future at this point? I wonder. It has a lot more dimensions. Ah, right. Interesting. Let's reveal the winner. Tabs. All right. It was a random draw, actually. Okay. We are working on the AV. Ready? Okay. Okay. All good. Take it away. Okay. Shall we switch the slides? You can start. Let's go. All right. Thank you. Oh, so, this is my first time at PyCon, and this is my first time I'm giving a talk. Thank you so much. And since I'm challenging myself, I decided to give a talk in a way with a skill that I hate, and it challenges me every day, that is cooking. I hate it. So today I'm going to tell you a recipe how a computational biologist is made. So we start with a person who is confused, you know? They don't know they want biology or they love coding, like a girl stuck between two boys. Like maybe I like him more or what. So that's me, hey. I'm that biologist and I'm that person who is confused and I turned my confusion into my profession. So what it takes, it takes some data. Oh, I'm being unfair. A lot of data, a bit of math, a lot of confusion, a lot of deep learning, and bam, you have a computational biologist. And though caffeine cakes, an existential crisis, even though I don't want it, they're still there. I'm focusing on a cut on my sugar intake, so that's why. And then what we need to do is we start right in the middle. So you get imposter syndrome from both the worlds, okay? Not just one. Both of them coming right at you. So I have wet lab biologists working with me who are saying words that I have never even heard. And from the last two days I have been at PyCon and I think I'm a complete idiot. So I start right in the middle, okay? But don't worry. You need to just embrace the frustration. Why? Because you can't avoid it, so embrace it. That's what you should do. You can't avoid crying, so just embrace it and cry over it. Then don't plan too much. Because your plans are not going to work. You think you do something on your computer and that is going to work on the bench? That ain't happening any time. So you stir, you stir, you stir your data, you repeat your experiments. And bam, your data doesn't negotiate with it, with each other. Don't worry, it will never negotiate with you. So let me tell you that there are many players over there. And I'm very lucky to be in this field, because I feel that every day this technology develops and tells us more and more about the biology, the health care, the more we can improve the lives of the people. And we have many types of technologies emerging. And this is the space I want to be in. I want to help the coders who are actually building to understand biology and the biologists who are struggling with coding, and I built something in between called the BioCabinet. It's still a work in progress, so it will deal with all the modalities of the data, making the life of the wet lab biologist easier, better. They can spend more time doing science rather than just struggling with the different types of data. And here I am. It does get you the pathways, get you what the biology is happening when you're doing your experiments. You don't have to worry that how you will deal with the data, how you're gonna do it. Because we have so much emerging in the field of Python, of the field of artificial intelligence, so why not we take advantage of it? And I as a biologist take pride in it, that I can do that and I want to do that. And then you just serve this recipe hot to the biologist on the wet lab and they're very happy with it. They're literally happy. Just serve it and let them enjoy it. And yeah, you need to adjust the expectations, though. Don't tell them that you run it once and all the environment issues are solved just like that. Don't do that. And yeah, that's me over there. I'm a biologist by profession and a coder by heart. And it's still a work in progress. So, yeah, thank you. So just a reminder that Andy and Laura are actually writing something that we can't understand in 2026, but if you ever want to take some of those fantastic, should I call it drawings or are they actually writings, or what are they? You can actually come to me tomorrow and you can grab them at the booth in the community lounge. You get your card? Fabulous. Thank you for your talk. Okay. Time for another question while you pick up the next speaker. All right. Shall we call in the speaker in the meantime? Sure. I've got Julio Muscarello bringing PyTest to the lab with Pyvisa. Are you here? He was here yesterday. Brilliant. Fabulous. Let's go for the question. Worst thing to find during a code review? Sometimes it's better to be close than to be there. Don't let perfect be the enemy of better. Okay, this is interesting. I'm really curious to see what we got. Okay. You from the future, would you know the winner at this point? Again, I think it's not the one you expect, but it's close. It's global bibles everywhere, which is right the second one not the first one good. All right Take it away Hello everyone, my name is Joachim Schmidt and I'm a specialist in implementing end-to-end processes and Today is my first lightning talk I would like to talk with you about an important topic inspired by a video by David Thielke which made me reflect. I want to talk about the challenges in age diverse teams. As an important note I intentionally leave open what old means in this context. I'm also aware that this topic is quite controversial and sensitive and of course the problems described later do not occur everywhere and it's common for developers to work in age diverse teams this has many advantages such as knowledge transfer and having high having different perspectives on a topic hands up who works exclusively in a team with only young developer. However, collaboration also comes with challenges. There are different working styles and communication gap between generations. There are also maybe the underlying tension. For example, seniors often earn more. It can also sometimes be difficult to teach new things to other team members. Many of these issues are manageable in daily business, but during highly stressful phases, they can become overwhelming and leads to interpersonal mistakes. I would like to focus on one particular point. And again, this does not apply to everyone. So for many people learning new things quite takes longer with age and that can be discouraging for younger developers when they have to explain the same things over and over again, things they already understand. When it takes much longer to onboard older colleagues into new projects and make them productive. There are three levels of knowledge. Domain knowledge, process knowledge, and tool knowledge. Domain knowledge is stable over the time and change rarely, while process knowledge also changes but lasts quite a while. In comparison to that, tool knowledge changes frequently and quickly in the IT sector. When a technology shift happens, developers can often carry over only little from the previous technology, a lot of knowledge is lost. This means that in the area of tools and frameworks, developers often have to relearn things almost completely. So why it's harder for some older developers? There are two points. First, older people often find it harder to learn new things than younger people and the reasons are biological. Slower neural processing, changes in the hippocampus, etc. Second, there is less time available. I can speak from my own experience. During my studies, I had a small shared apartment room and could fully focus on learning. It was no problem to program all night, experiment, or just play games. Today, I have a family with two small children who need their father, who need to be driven around, who require special food due to their allergies. My oldest child has special care needs. In addition, I have a larger apartment compared to my studies where sometimes always something is breaking, it has to be maintained or to be cleaned. In five years, I will have to take care of my parents as well. So for me, the focus has simply shifted from being learning focused to responsibility focused, and this certainly applies to other developers as well. So what can we do? In my opinion, the most important thing is to create awareness. Especially in stressful times, we need to treat each other professionally and with respect. If you are older, stay close to technology, avoid falling behind, and remain open to new things. And if you are younger, be patient, supportive, and considerate of different life phases. And don't forget, one day, you will be the older developer. I'm actually 300 years old. But I don't look a day over 150. All right. Okay. Now I'm going to ask you two questions. Let's start with the first one, please. All right. Let's start the round. Most important soft skills for developers. Ooh, that was fast. And while the people vote, I can call up on stage Friedl with Pomodori. Get better in 25 minutes. Friedl? Yes, he is. Is that nice? All right. That's the winner for this one. All we have that most voted is saying no politely. No, I can't. No, I don't think so. No. What do you think? No. let's say Patience Yeah Okay, let's try the other one best conference fuel Pretzels club mates coffee gummy bears currywurst pineapple pizza. Don't you dare? Don't you dare? Apple pizza We knew that was going to happen. Pineapple pizza is not allowed. It's illegal. Joking. Take it away. All yours. So, hello. So, hello, you might have seen this slide yesterday, sorry for the problem. Anyway, I'm Julio, I work at Hohenschwarz. If you do electronics, you might have heard of the company, because we do not only software, but most importantly hardware, we do measuring instruments, and I want to share with you how we use, how we actually got to introduce PyTest in the measurement labs and also use We'll see in a while what it is. So what do many of our customers do? They usually have a laboratory where they measure either, maybe they have electronics, and they want to measure that the radiation, electromagnetic radiation that they produce is below the limits because there's laws about that, or vice versa. Some clients are special, they are like space agencies, and they do the opposite. You send a satellite in space, you don't want the radiation from space to impact your electronics, so you put it in this room, which these are like isolators, you produce some known radiation using an instrument, and you test if your device works correctly. So what we do in this is the instrument that goes behind it, be it a generator, or a spectrum an analyzer or an oscilloscope, these kind of devices. The problem is there is so many things. It's not only us doing this kind of instruments, there's different companies, mostly are Windows, some are Linux, some are like specific, some are old, some are new. Yeah, let me introduce you to the iceberg of hardware testing. So you know the meme, the first one is most known and then it goes deeper and deeper into more obscure topics. First one is the solution for peasants. So you have your chain of devices, they have a touch screen so you can just click buttons, read the data manually, yeah, it's bad. You can do it once, you can do it twice, but then you really get bored of it. So what did they invent to do this? There's a thing called VISA, it's a standard protocol, it's text-based, and you can use it on measurement instruments, on generation instruments, on plenty of things, really. It's quite simple, I would say. I'm not a developer of this, so maybe, sorry if you want those. So let's say, for example, you have an oscilloscope here in the image, you say, oh, I want to enable one channel, okay, channel one on, And then I want to measure the amplitude. Okay, amplitude, question mark, response, five. Cool, works over plenty of things. Most nicely, TCP IP, so you can just put your devices into a network, and then you can read them all using something. You can automate it if you have some client of sorts. Okay, so layer one is you no longer have to press buttons. You can just write some code. Maybe you have some kind of homemade visa library, some kind of homemade test driver. Plenty of people do this. It's still not optimal. Why? Because you are reinventing the wheel, right? If you're in this room, you likely know of a very good testing framework. You might have a different opinion on how good, but anyway, it exists for sure. It gives you already a concept of how you test things. You have a class, for example. Each class has different functions. fixtures, blah, blah, blah. There's an excellent training about this, so plenty really. It also works with your editor, so you can actually type a test and have it type checked live. You can have a CI for it. You can also debug it, which is, I think, kind of cool, especially in these situations. So you can say, oh, when I send, let's say, some white noise with this intensity, then my system actually misbehaves. And I can be, okay, where's the line where I set that, okay, can I go back, can I go forward? It's really nice, it's already a big step. In case you never used PyTest, I think this is a really nice showcase, let's say. So let's say you're connecting two instruments, you can just say, okay, I send a query, and And then I query another measurement, say, oh, five, okay, actually, it got 5.03. It's different. Oh, cool. Then I know, okay, it's at this line. Very nice. This is a simple usage of PyTest. You can even go deeper, and that is really nice. Ah, sorry, I am so late. So you can have a JUnit, which works with all test consumers. Which assertion? Yes. Thank you. Thank you very much Julio, sorry about that. So I've been working on the humor of this timeline and I think I formulated a father joke or dad joke. So why did the actor, so why did the AI not want to act in the movie? Is it because they didn't have union rights law? No, because they didn't want to be the token character. I'm told that for the joke to work, it must make you feel slightly sad inside. So I think it worked. Do you enjoy this sort of thing? I think it's some sort of socially normalized BDSM. We're not in Berlin. I have the next talk to come up here on the left side of the stage. Rana, will you come to the podium for Pai Singh? Ooh, nice. Oh, get ready for that. I have a next question for you. Are we setting up there? All right. what do you must delete on Fridays all very important questions Slack notification I see you there and read emails yeah okay let's reveal the winner I'll read emails do we have emails in the future we have a form of mental telepathy which arrives digitally when you least desire it. That's naughty telepathy. Are you ready there? Can we take it away? Fabulous. Do you have your video there? Yeah. Hello. I'm Friedel Leszakowski. My first lightning talk. Do you have your video there? Hello, I'm Friederik Leszakowski. My first lightning talk. Thank you. I'm doing it without slides. But that's no problem because we have all on stage what we need. This talk is not about AI. This is not about tech. And this is not about code. This code, this talk, sorry, sometimes I'm confused, I'm really, it's just pure old school tools used. So, what might it be? What do we have here? Here we have a clock, and we have our prime. And with this combination, we could do very nice things. let's get some interactive who likes Italy no one some pizza ok some more pasta ice cream espresso tomatoes ok let's talk about tomatoes and in Italy. It's called pomodori. What a pomodoro. I don't know. And what's pomodori and our brain and this clock in common? So there's a method from the 80s. Who knows this pomodoro method. Wow, nice, nice, nice. I learned it two years ago, and I wished I learned it more, more, more. Ah, longer. So in my study times, maybe. Or when I started to work or something. So what's Pomodoro? It's like a time frame work. And everything you need to know is you You have 25 minutes of focusing to your task, then do 5-minute breaks, then again 25 minutes of focusing, 5-minute break and a third time, and after this you can have a 25-minute focus and a longer break. So this is all you need to know, mostly, to do it. And all you need is your brain and a clock. And it doesn't matter which clock. You can use your phone, you can use your clock on your desktop, you can have it analog somewhere and let it ring. And it's nice to your brain because you get in a state where you get focused and you can reduce all your unneeded stuff beside this focus and left it for those some minutes. And then you get rewarded, kind of, with a break. Then you go fresh into it with a new view on your problems, on your learning stuff, on your work, I don't know, and start again. So it's an old technique, and I missed, because I don't have my slides here, something which could add some gamification to it. Getting a reward of this routine tricks our mind. You turn this into an analogue life hack. You can beat procrastination because you just start with 25 minutes. It's not hurting. It's just something to do. You start with and then you get your things done. And you can skip your distractions. That's another nice thing. Because everyone could wait 25 minutes over their call. Thank you. Thank you very much. All right. Get ready for the next important burning questions for you. This is actually very interesting. What's your most useless desk item? Rubber duck, mechanical keyboard, single air pod, laminated shit-shit, vintage Tamagotchi, stress ball shaped like Python. And the next person, remember, sometimes it's what you do in the last seconds that count. So, let's see what we have. A mechanical keyboard, okay. The next person on stage will then be? Dennis Wayland, Blood on the Clock Tower, why you should play this with your colleagues. Are you here? I see you, come on. Is it coming? Yeah, fabulous. But I think you can start. Get ready for the next talk. With all these lights already. Okay, let's do it. Hi, I'm Rana. This isn't my first lightning talk. I had it. I had a lightning talk two years ago in PyCon PyData Berlin. It was my last lightning talk, so now I'm here again to try the same thing I tried two years ago and I failed. So I hope it works with you because you're a different crowd, you have more energy, I'm sure. So let's do it. So today we want to make some sound. So the sound is three parts and we will learn it together. The first sound is just a beat. I'm sure everyone can do it. So it's like doom, doom, doom, doom, doom, doom, doom, doom, doom. Thank you. Perfect. You can... Thank you. This was the first one. I think everyone can do it, hopefully. The second part is that we want to give it an answer, since we all love PyCon, just let's scream PyCon. So it's like PyCon, PyCon, PyCon, PyCon, PyCon, PyCon, PyCon. So I will do the Doom, you can do the PyCon. Let's do it. Doom. PyCon. Doom. PyCon. Doom. PyCon. I love it. I love it so much. Thank you. So what we want to do, we will just split it, like the right part, your left part, is doing the dum, and the right part can do the higher beautiful piken. So let's just do it together. So dum, piken, dum, piken, dum, piken, dum, piken, dum, piken, dum, piken, hey, that works. It's much better than two years ago, so I finally have one. years ago, so I finally have one. So let's do the last part. It's like when my hands go up, we all go like, shh. Let's do it. Shh. Wonderful. So let's just practice again, and then we will do the last round. So dum, python, dum, python, when it's like, shh. OK, so let's do it. And dum, biker, dum, biker, dum, biker, dum, biker, dum, biker, dum, biker, dum, biker. Shh. Great. So let's do it the last time. I will say just random dummy stuff. Please don't stop. Just continue until I do it. Okay? So please do it loud but full of energy. It only works if all of you do it. And then I don't need to do it again two years, next two years.