Lightning Talks

This video is from DjangoCon Europe 2026 in Athens, Greece.

Lightning Talks
0:44:11
Published October 26, 2026
65 views

Video collection of all the lightning talks from Day One of DjangoCon Europe 2026.

Follow DjangoCon Europe on social media:
*X - https://x.com/DjangoConEurope/
*LinkedIn - https://www.linkedin.com/company/djangocon-europe/
*Mastodon - https://fosstodon.org/@djangoconeurope

#django #djangocon #djangoconeurope #djangoconeurope2026

Transcript

5,981 words · auto-generated · en Show

Automatically transcribed, so expect mistakes in names and technical terms.

0:04

Speaker 1: And I think I hand over immediately because it's time for the lightning talks, is it?

0:09

Speaker 2: It is indeed time for the lightning talks. So we have uh five-minute lightning talks and we have nine of them in 40 minutes. So I don't know who's good at maths. Uh it does work out, I promise. There's maybe some people sharing some slots. Uh do we have the first speaker is Ronnie. Uh is is Ronnie in the room? Hey Ronnie, please uh I don't Oh reverse down. Yeah, no problem. So do we have uh Miha? Miha? Uh somewhere? Yeah. Are you ready? Cool, let's go So we have uh Mia Zidar.

0:58

Speaker 2: Uh

0:58

Speaker 3: okay. Uh hands up who has heard of C D Really? Just a few people? Continuous delivery? Fast Okay, more people. That's it. So a lot of people actually think that you need to have feature flags to have to get to continuous delivery. Well that is true. It's not only true, right? Um I've seen a lot of companies think of like, oh, we have a two or one month release cycles and we're gonna get to faster delivery by uh using feature flags and just delivering every day. And it turns out that Feature flags are a tool, but there's a lot more that you need in order to use that tool properly, right? Uh just hiding a piece of code behind it does not mean you're not gonna break production.

1:46

Speaker 3: There's a ton of uh different strategies that you need um in order to ensure the safety while using feature flag. Uh one of those is basically, hey, if you're using feature flags, you need to run all the tests twice with all the flags turned off and all the flags turned on, right? Um there's my colleague over there on the top, which made a nice helper function for uh Django Waffle uh flags to basically Run the Django test suite and then if any test touched a feature flag, it gets run twice. Or actually all the test gets run twice, but the ones that don't touch feature flags uh get skipped the second time, right?

2:32

Speaker 3: So there's one tool. Um there's also a lot of different uh strategies that you need to do like people try to use feature flex then for every single thing that they can think of and The thing that most people forget is cleaning up, right? So one thing I have had this conversation in many companies, uh and it usually takes six months So I'm I just have less than that now. Uh meaning I'm just gonna tell you one thing the code with feature flags is not the code you write to keep in This is the only code that you write especially to make it as easy as possible to delete, right?

3:18

Speaker 3: So anyone here that wants to use feature flags keep in mind all of your this looks nicer and I'm gonna refactor this this way. No the only thing you have to uh keep in mind is The code that you write is meant to be as easily deletable as possible. If you don't do that, you're gonna mess up. You're gonna have tons of feature flags everywhere and it's gonna cause complexity and like what do we do when there's five of them and like which ones do I need to turn on and off? That is the biggest uh Hint that I can give. There's many, many other, and uh like I said, six months uh is a bit too long for me to to stay up here and talk, I think they would uh agree.

4:04

Speaker 3: Um but yeah that is that is the biggest thing. Test twice And write your code as simple as possible. Oh, one more hint. Never ever have uh an if statement with a feature flag and something else, right? Feature flags are usually hey if my feature then do something else if or else then do something else, right? Uh if feature do the new code else keep the old code, right? Uh never no matter how weird it sounds, right? Don't join other conditionals in that if statement. So if you have a if statement with a bunch of stuff and you just want to throw a feature flag in that, no, nested if

4:51

Speaker 3: Are better again for the first reason you're writing that code to be easy to delete. You don't want to be changing code when you're adding and removing feature flags. And that's the step one of hey We're not just using feature flags, but we're actually using them to make the deployments safer and faster. That's it.

5:13

Speaker 2: Wow. Thank you very much. Thank you. Next up we have uh Raffaela. Is Raffaella here? Are you ready? Yeah, great. So Raffaella you're giving a talk called Learnings from Being an Admin at Django North Space, is that right? Yeah. We'll just get the gone. There we go. So do you have the adapter? Yeah. Do we have a USB C adapter? Does anyone know? Is the one here?

5:59

Speaker 2: Nobody knows. I don't know who's gonna talk to me to be honest. I'm just here on my own. It's coming. We got an adapter here now. Thank you very much. There we go. Oh we didn't expect it and just compared this really No no no I wasn't it I wasn't ready. I wasn't ready for you being ready. Do we start the try starting the start the another round of applause please

6:50

Speaker 4: Okay. Hello everyone, Raffaella. I'm from Django No Space. And recently I became an admin at Django Space. So I wanted to share with you what I uh what I recently discovered in my neural. Okay. No. Sorry.

7:24

Speaker 2: So let's see. Ah, it's frozen. Typical, isn't it? The one time it matters, and you've only got five minutes, so don't worry, I'll give you an extra 30 seconds. So we've got this and we go to the next slide. No, it's not updating. One moment. So let's just exit this and we'll go up to the top here and we need to probably uh extend. This is called live debugging. Um I'm actually not very good at debugging things. I hope no one someone who's competent has taken over. I think this is great. It's funny because there's there's probably you know 200 people in this room here and 120 of you know exactly how to fix this, but no one's offered any advice or anything like that, you know. No problem at all.

8:11

Speaker 2: Turn it on off and on again. Okay, okay. It actually the the slide didn't change. We unplugged it and the slide didn't change. Did anyone see that? Is this a rift in the space-time continuum? How does how does that work? Is it frozen in the back in the back perhaps? Okay, uh perhaps it's in the back because uh Okay. Sorry, that was a third joke.

9:07

Speaker 2: I uh what was that? I think we need to try to create a taco point. Ah, okay, okay, okay. More than something. Okay.

9:54

Speaker 2: We'll bump you to you

9:56

Speaker 5: doing that.

9:59

Speaker 2: Okay. I forgot your name, Ronnie. Are you ready? So we'll we'll do Ronnie's slides now and then we'll troubleshoot this and then and then we'll we'll come back to Raffaela. Uh sorry about that Raffaella that was my fault. It's it's nothing to I d I don't know anything about it. Yeah yeah. We we we'll now figure out if it was uh my fault or Raffaella's fault or the laptop's fault or There's Carlton. And do we have oh we have a desktop? I'm not a menu, so I'm not sure. And we need to go uh oh you got it. Wow. Isn't it incredible someone here can use a computer?

10:45

Speaker 2: Okay, here we go.

10:53

Speaker 6: Okay, hi. My name is Ronnie. I'm the host and organizer of the Django Cologne meetup for close to seven years. Um I started using Django version 1. 4. Um I'm a core contributor with Dang It's a tiny thing in what in 0. 6. 0, so my wrap sheet. Um and uh this is a blog article um I wrote a couple of weeks ago. about a good side effect of um this AI thing we heard so many bad things about and actually um the readme of all our projects would be like A mess to be honest. There would be stuff in there, there would be helpful stuff in there, but mostly would be just a very long wall of text containing stuff that nobody actually reads because nobody likes to read wall of texts

11:38

Speaker 6: So um what we did what we did is or what I found out um that instead of Writing one huge README file that nobody wants to read, I created a couple of um folders in a docs uh in the in the repo and turned the README to Just this kind of an index. It would c had a claim, the project is about X, and everything else would be sorted in um this directories like coding patterns and contributions and how to get started and something like this. And the good benefit is that first it makes fun to write this because it's just 30 lines, 100 lines max.

12:23

Speaker 6: Second, it would be fun to read. And actually people would read it. And the best thing about it, it's a good thing the AI can understand it as well. So you can just say, hey, I'm writing unit tests, and here's my testing strategy. Please look at this file. And you don't waste all your tokens on 2,000 or 3,000 lines of README that contains maybe important stuff and maybe not. So um yeah, I'm doing this in all of our projects now. Um and I think it's very easy to do and it makes the world better for the project, for the AI, and at least for the June developers starting the project. So um if you're interested in reading this then I have to nope I can't move well

13:09

Speaker 6: let me see oh wait a minute Yes, there's a QR code. Great. So if you're interested, give it a read. Thank you. I leave this up for a second if somebody wants to take a photo.

13:30

Speaker 2: Thank you very much. I like how the slides work. So next we have John Gold. Are you ready, John? Where's John? John. Here he is, round of applause. John has a talk on how tech fraud has a hiring problem. Yeah yeah yeah yeah I think I've heard this one before John it's a good talk. It's very simple, you just plug it in, John. That's it. I think what we want to do, John, if you don't mind me intervening slightly,

14:19

Speaker 2: we'll just uh you've got eleven percent battery there, John. Right. Okay. Uh uh uh where are we going? Uh uh uh uh uh uh uh There we go. This is quite hard guys. Please have sympathy. I'm trying to use the mouse up there. Okay, ready?

14:47

Speaker 5: Yeah. Oh shit. Hi everybody. Right, so I'm John. I'm the founder of Foxy Talent, Quick Bio. I've been recruiting Python and Django developers since 2008. I'm an individual member of the Django Software Foundation. Foxy Talon has now donated over 20,000 US dollars to the DSF. Um and I'll cover the next stuff. Right, so tech hiring has got a fraud problem. I did a Small lightning talk on this in Dublin last year and it's just it's spiraled. There's much more that's coming um coming out of the woodwork. We're seeing it more prevalently across more regions. So I just want to quickly just show

15:33

Speaker 5: The problem how that's now affecting job seekers in um in real life. So yeah. Right. Um unfortunately like it's not edge cases. The in in Europe, scammers are using deep fake filters. uh across their face to um blag their way through uh technical interviews, through screening calls. Um using scripts to help them talk through. In the UK, fake profiles are showing up every pretty much in every ad response in every pipeline. And the UK in the US, all of these are happening as well. LinkedIn accounts of real people are being hacked, repurposed to look genuine as job seekers. So

16:18

Speaker 5: this is an example. I've blocked him out just in case he's real, but he's not The email at the bottom shows that the name at the top has been changed. It was just a spot and then you dig a bit deeper. Two weeks before the application, this profile was um inv you know clicking and in engaging in um Like life science in India, like posts and stuff all around that, and then two weeks later he's a developer at Nike in San Diego. So it's just it's a problem. Um This is a screen grab from a call that I did where I first came across the deep fake. This one on the left in the white was actually reported by the pragmatic engineer. He's got a whole report on there about the situation and how a startup in Europe has dealt with it.

17:06

Speaker 5: Again, sh wish they're edge cases, they're not, they're just common. Um but what that means is hiring teams now becoming very skeptical the um every manager, every recruiter immediately starting at a point of skepticism, looking for red flags, and then proof that somebody's real Which means that as a candidate, as a job seeker, you have to almost like go a little bit further to prove you're real, not just a good candidate for a job. Some of the things that It's really uncomfortable, but these are red flags that I look out for, but they they pretty much apply to real candidates, every real candidate I speak to as well. No photo Like are you a scammer or do you just don't like selfies or you prefer to have an avatar?

17:51

Speaker 5: Um a generic CV, what I mean by that is something that's been crafted by AI to help you look as relevant for the role as possible, or is it a scammer doing the same thing? Broken links on your CV, they should take you off to your LinkedIn, to your GitHub. or a hiding stuff, the broken links often are a sign of a scammer. Um a sparse GitHub, is it a fake profile? Is it one repo commit six months ago or are you just working on private stuff the whole time? Um and like is your LinkedIn account brand new? Are you a bot or have you only just got around to start the setting one up? One of these on its own, i i you know, you you you follow through, you think the best of people, two, three, four, five of them, you're like, this is a fake, I can't

18:41

Speaker 5: I can't take the risk of intro you know introducing them or putting them in front of a in front of a uh hiring manager. How to stand out, it's the opposite of what I just said. Add a photo or your online accounts. Make the occasional post about something that you're you're doing, you a real person is doing. Write your own CV in your own words. Don't optimize it for a role because it would just look like every other optimized CV for that role. Practice how you explain your reasons for looking for a new role so you can be human in an interview. Thanks. Uh right, leave a digital paper trail. So the thing that the easiest thing to do, it's sad we have to do this, but you've got something that can't be faked.

19:27

Speaker 5: You're a real person. You're here in Athens at DjangoCon. This year you're meeting people, speakers, organizers, other attendees, connect with them, leave a trail, take a picture here. Great venue. Alright, take a picture of the venue. Say what a great first day you're having. Sharing is proof of life It's the best defense now is to be undeniably real. Reals in this room. That's me. And then I wrote a blog post about this, and it should be That's how you can get to it.

20:00

Speaker 2: Thank you very much, John. Great talk. And uh you said uh

20:04

Speaker 5: ten percent battery left. Ten

20:05

Speaker 2: percent battery, that was good, yeah. I noticed you said uh be real get a photo here, is that why you did the talk Yeah, yeah.

20:11

Speaker 5: I asked Powerload to take a photo as well, so I'm definitely here.

20:14

Speaker 2: Okay, we have um Raffaella, right? We have Raffaella again. Uh and we're using my laptop, so now if anything goes wrong, it's definitely one hundred percent my fault. Um This is good practice for my uh my talk tomorrow actually. I'm actually doing my AV A V test right now. Okay, wait, wait. Does it work?

20:43

Speaker 4: Hello everyone, I'm Raphael again. Seems like I chose I don't know the uh that although there seems like a prophecy. Let's see at the end I'm still from Django Space and because ever seen uh Django Space or ever heard of it Check our website because we are really cool people. But for those who are not aware of the program Django Naspace is a mentorship program that helps people to start contributing to Django ecosystem and all mentors and session organizers are 100% volunteer. I joined Django

21:28

Speaker 4: Space as a Django at first, then I volunteered as a session organizer, and I applied for became an admin, and probably you guessed, I became an admin at Django Space. So I wanted to share with you something that I learned. First of all, communication challenges, because when uh when you have to deal with uh when when you uh when you want to work with volunteers There's lots of work uh with communication, for example, you you need to uh let people heard but not overwhelm that. Uh and it's uh really uh a need of a balance. And probably you could guess that if you're not a native speaker, it could be

22:14

Speaker 4: even a little bit harder Invisible work lot because uh when uh when people are um have tasks you also have uh in order to support other people you have to be prepared for even for them in order to support them. And maybe if they can uh if they cannot do it, uh you now uh me and b and became the backup plan. Um also we have lots of documentation for our um for our volunteers I use it when I when I did uh when I was a session organizer, I use it now. But now I also uh I also have ownership of that. I have to maintain it

23:02

Speaker 4: It's a decision has to be uh done the but with careful thoughts Sometimes even though you want to say yes, you have to say no. And because sometimes there's no time, or maybe there's not a not volunteer, or maybe you do want to do something by yourself But there's a need to have balance with your work life. There's also a question feeling of not feeling ready. Like you have to deal with the uncertainty, for example Am I communicate the things correctly?

23:50

Speaker 4: Was I clear enough? Am I the right person in the role? You have to deal with that, with the constant feeling. But the most important things that I discovered in this role, it was the how many people are happy and enthusiasm about this. this mentorship program for example people when when people uh share that uh has been accepted as jangonauts on social media or maybe they have another uh another role uh another work role thanks to Django Space. It's it's really it's really amazing. And if you think and if you stop uh for a moment and think about that everything that has been done

24:36

Speaker 4: it's just thanks to volunteer people and uh all the effort that is behind this this project is it's very um it's what uh gives me gives me more joy and with that's what kept me going. So thanks to all the volunteer and everyone who um who have put lots of effort in for Django space. Thank you

25:08

Speaker 2: , please. Can you take my laptop? Thank you very much. I think uh when you speak to people about Django, Django North Space is one of the really special things that people understand and recognize as uh quite different to everyone else. We have next uh Benjamin Bach. Bach Bach, sorry. And we have a talk here about, or sounds like an advertisement, about, Django Day in Copenhagen. Slides. You don't have slides? I do have slides. And if you want to reach them out. Can you

25:45

Speaker 7: H is HDMI better? Oh, USB C is fine. Okay. Yeah. Let's try it. And then here's your microphone. Thank you. Uh can you hold it for a second?

26:00

Speaker 2: It seems that uh it's often the case that we must move the slides onto the other slide and then try and figure out which slide the slides are on. Oh. Oh, okay. I I is it is anyone seeing this? I'm not really sure how that works. Um okay, d can we can we duplicate the window? Okay. Has someone enabled airplay somehow or you know like remote casting? I feel like something spooky is going on. I'm gonna step away now.

26:46

Speaker 2: If I move further away I have less blame. If you if you could uh fix it quickly, that would be uh great. No no pressure or anything, but um people are really excited to hear about Django Day in Copenhagen, aren't you? Oh come on I I I don't know anything about Django Day in Copenhagen, but raise your hands if you've been before Okay. And raise your hand if you really liked it. Okay. I'm not asking any o other questions, that's it. If you didn't like it, just keep it to yourself, okay? Do you want to

27:35

Speaker 7: Yeah. Okay, so I'm introducing an event in Copenhagen called Django Day Copenhagen and it's taking place once again. And uh my favorite sports star is uh Carlos Alcaraz. Um can I just have some help to full screen this? Uh

27:53

Speaker 2: I think it adds to the effect to be honest. I think this is quite a good

28:01

Speaker 7: full screen the wrong thing. Okay

28:08

Speaker 2: Yeah yeah I can hold two microphones. I can use two microphones at once. I've never had a problem talking about nothing. Um By the way, the attendance at my talk tomorrow is gonna be zero. They've heard all of my jokes. So I'm I'm gonna start presenting this lightning talk. Django Day Copenhagen 2026 is on October 2nd. Okay, we're ready. I think we can do it.

28:30

Speaker 7: Okay, let's uh start with the basics. So it's a day, it's about Django and it's in Copenhagen, but also we have a very nice uh party in the evening. So the thing takes place on a Friday, which gives also a little bit of uh extra possibility. for that party let's say um and um we 'd like people to come or to participate and uh One of the best ways of participating in this is by submitting a talk. But you can also attend by getting a ticket. Ticket sales are just almost ready. So let's see. We probably have them open uh tonight. Tomorrow and we stream everything for free. Okay, good. Um so

29:15

Speaker 7: uh I just wanted to talk a little bit about the the why of having a small event. So this is like an event where typically like sixty seven 70 people come. I think the venue has space for maybe 80 people. So this is actually like con you can consider it a little bit like a local event. And speakers they come from uh a little bit local but uh a lot of traveling speakers actually. Um and this is uh this is great for uh strengthening the local community. Um and um so people uh when we talk about local community that's also your local businesses. That's people that are using Django or maybe considering to use Django. They will see that there is a local event and this is like a booster. And

30:01

Speaker 7: another reason why we like small conferences is that it lowers the bar for a first-time speaker. Um so of course being on the big stage up here it's uh it's it's a big step and you can start by getting some experience from from a smaller event, but that also gives space to um not just uh first Time speakers, but also people who want to try out new ideas, things that like they're not quite sure that it's uh it's ready for the big stage yet. So uh you can come and do that at uh Django Day Copenhagen. In fact, we encourage that. Um And um uh yeah, so like uh maybe there's a lot of stuff going on in the world as such and uh maybe it's uh it's it's It's it's about uh time that we uh push some new energy into uh like uh small local things that um

30:48

Speaker 7: um that I have written and blogged about, that's why there is a QR code. So there's a a long elaboration uh about why we should do more of it. this and please copy the concept. So another QR code, but I'm sure you can remember the address there. That is where you get to submit your talk and get a ticket. Thank you very much.

31:12

Speaker 2: Thank you very much. Thank you. Do we have a uh Adrian Cossa? Is Adrian somewhere here? Right at the back. So we have uh Adrian is gonna talk about AI versus Prek? Prek! Uh the floor is linting. Okay, I have no idea what that could possibly be about, but Um but it uh we have to just put this up around the end. I don't like this bit where I wait for it to appear.

31:58

Speaker 2: I feel like I've got some trauma now. Does it appear this is what I mean. Oh. Oh. You you've made it worse. Uh it's getting better, maybe? Uh No available windows is quite a philosophical thing, isn't it? You don't need it. Great. Okay, round of applause please for Adrian.

32:46

Speaker 8: So as long as I have my slides, everything should be alright. Uh yes, so AI versus Prec. Uh so I'm a customer uh success engineer at Opera Credits and this is where I transitioned from Uh VS Code with uh auto-completion a bit assisted by AI to fully agentic uh coding. Uh vibe coding or maybe uh agentic engineering sounds a bit more professional, whatever. So yeah the problem when you when you you start to to use and abuse AI as you know is that also the quality uh might not be there

33:31

Speaker 8: and uh the more you the faster you you you ship also the faster the the tech the uh the tech depth is growing if you don't have certain uh hygiene I would say. So I started to to do something that we could call uh skills-based Um no yes like sorry I forgot. Anyway, skill skills skills based engineering first time uh uh giving a conference so um so the the idea is that any time i have to do at least twice i would say i write a skills for it yeah so that my agent can pick it pick it next time and I I don't have to to do it myself.

34:22

Speaker 8: But uh in the beginning it worked great but after some time I had a lot of skills and they also tend to grow And I noticed that the agents are not following the instructions at all because uh maybe there's a like context pollution uh or just it's it's Mm they just tend to to forget things. Even if you write like strict rules, this is mandatory, do it, they just don't do it. So what can you do? Uh maybe it is not solving the full problem and there are several ways to address this, but one way is to use pre-commit hooks so prec is actually uh like a rust implementation of uh of the original uh pre-commit framework uh it's faster and it's also uh uses

35:07

Speaker 8: uh uh UV in the background so why this is why it will be faster um but I just like to to use it uh for all my projects and um The idea is that with those hooks, pre-commit hooks you can set some like minimal uh level of quality Of course you will think about uh rough or static type checking. Currently I'm using uh TY but I promise that I will give uh Mantel a try. You can also use it to detect uh like secret leakage with a commit hook called uh GitLix.

35:53

Speaker 8: Or imagine you don't want to push uh certain terms to the code base. For example, if you do something open source but you use it also for a personal project or a company project You don't want like uh the name of a customer to be pushed in the code base by inadvertent, especially if you let AI write your skills. So you can use banned terms to prevent this. You can actually write your own custom hooks to do anything. Basically the approach uh that I try to to follow is that especially after I make some some big mistake and it impacts production and people shout at me The first thing that I will do, maybe after fixing the issue, is to write a commit so that it will never happen anymore.

36:41

Speaker 8: Um So it's a bit unfortunate because I had here the slides generated by AI and there's one slide that is saying you can start with rough TY. And after if the code base grows you can add some more commits on top of it. Don't do this at all, just start with all hooks as possible since the beginning. Because this is how you you manage to to uh to basically start with a good quality that will be maintained. Uh if you try to retroactively improve the code quality, uh it will work probably, but this is we this will be more work for you Yeah basically I have also a skill uh that I made by compiling a lot of different sources like the Django.

37:30

Speaker 8: uh official documentation and articles from uh people I I like to read about uh some here uh so this is why I I would have liked at least to to share maybe this but whatever I will post it in uh in the the lightning talk uh channel some links and also uh one projekt that uh that i uh yeah that i work on uh with a set of hooks So just if you are interested to see what things I do with it, uh just have a look. And uh beside that uh Thank you and enjoy

38:17

Speaker 2: So that was his first talk and it went wrong. He did it without slides from memory. I think that's incredible. Well very well done. Last lightning talk is uh David. Uh and also I've forgotten the name, but we've got a combined slot now. So uh we have uh David is talking about uh which PyCon? PyCon Portugal and then we have PyCon Greece and then if we have time we have EuroPython. Oh no. Has anyone seen this before? Anyone seen this scene before? That's a nice picture. And then press play, maybe?

39:03

Speaker 2: Slides? Please. Uh no. Not again. We don't put one to the other. Everything's under control. Yeah.

39:30

Speaker 6: This is the bomb part of the conference where other conferences try to sneak in and uh ask for participants. For those of you who have never been to Portugal, that's your chance. We started in 2022 during Django Khan Europe in Porto and we kept going. I'm a big fan of filling out maps. So in Portugal we are not repeating cities and this year it will be in Aveiro. Um the Here we have some running numbers. Uh it's a small conference, um, but we are trying to to growth. Um But apart from Portuguese people, we have people from all over the world, so please join us.

40:17

Speaker 6: We are still open for call for participation. You can still speak there. We always love to have volunteers and you can also apply for a grant. So Come meet an another city in Portugal. It's near Porto, so you can use uh Porto Airport and that's it

40:41

Speaker 2: Round of applause please, thank you. And uh I'm sorry. Pan pan fun We this guy's got two laptops. This might be a good plan. And then this goes around here. Why are they on different sides? I've got real severe anxiety now about adapters. Try try try slideshow and then play and maybe it'll work.

41:31

Speaker 2: By the you have it to the different things. I'm gonna be an expert in in this by by tomorrow. I'm not doing it tomorrow though, so Okay, a few clops please. Thank you.

41:51

Speaker 8: Hello. Hello, I'm Vanajotis, and this is a conference announcement talk. I'm going to talk to you about PyCon Greece. This is the second year of PyCon Greece that happens in Athens. This year it will happen on the twelfth and thirteenth of October.

42:08

Speaker 7: In the QR code you will find everything you need in our website and just FYI. We have already uh we just opened the call for proposals yesterday. It will be open until May 10th.

42:22

Speaker 8: Uh the finit applications also are open uh and it will be open the first round until uh june fourteenth. And uh also we will we're planning to open the early bird tickets uh soon, maybe next week. We're fixing some uh

42:36

Speaker 7: uh internal you know issues and we will be ready also for this

42:48

Speaker 2: Thank you very much. So the the next speaker is actually me. So I'm actually I'm canceling my lightning talk because I thought I'd have time during the lightning talk session to prepare my lightning talk. uh as it happens that didn't happen so there is no lightning talk. Uh but it was about EuroPython. I'll try and do one tomorrow. But I'm gonna do it like a Four second talk. Come to EuroPython. July Krakow. Okay? That's it. That's my lightning talk. So that is it for the first day of DjangoCon Europe 2026 in Athens. Thank you so much to everyone for coming. Thank you to all the speakers, all the volunteers, and especially thank you to the organizers of the conference.

43:34

Speaker 2: who uh have done this for some strange reason. I don't know why, but they've put so much work in and I think they deserve a lot of thanks. Tomorrow we have registration at nine, correct? Yeah, see this is why he's the organizer. Uh registration at nine and first talks at half nine. I look forward to seeing you all tomorrow. And if you don't have anything to do tonight, go on Zulip and message some people and organise something. go to the restaurant or or the purple, enjoy yourselves. Thank you very much. That's the end of the day. Thank you.

Conference

DjangoCon Europe

April 15 - 17, 2026

Athens, Greece

Note: We understand that names change, people change, and bodies change. We respect each individual's journey and privacy. If you have any concerns about a video or need us to remove content, please don't hesitate to contact us. We will handle your request with care and promptly address any issues.

More videos from DjangoCon Europe