 I hope you enjoyed this course. We've sure have enjoyed putting it on. I think it's been an amazing experience, especially working with all of these instructors here. Everyone just does a little bit and prepares their part and we show up and teach and work together and it's amazing. We have other events that come up. So we've talked a lot about the code refinery workshop. Maybe I can show that here. So we have lessons on a lot of version control and then other tools related to software. This is basically a logical next step to this workshop and many other ones. It's not Python specific. So before we've had this dream called research software hour, we basically go on Twitch and talk about some interesting topic. Although we need to figure out what the future of that will be given our current time constraints. And I know there's a lot of different things to figure out there. And who knows what else. There's this Linux shell event we've been talking about. We actually don't know if it will be online and open yet, but we're sort of thinking about that. How to stay in touch. So what we do is not just us talking to you all, but we would like the community to be involved in what we do also somehow. Code refinery was funded by the Nordic e-infrastructure collaboration for about five years. And now it's funding has run out and it's turning into a community project with a little bit more funding. But basically you should join, like you can join us and help us to put on these workshops. It doesn't matter what you know, just being around being a co-instructor, something we can find a way to do this. At Aalto University, if you're with us, then you can also join our community at skicomp.alto.feed. I think there's a community page there. We have a chat and daily help sessions where we can comment more on these kinds of things. There's Nordic RSE, which means Nordic Research Software Engineers. This is basically a group of people who work, how would you define? It's somewhere between a researcher and a software engineer. So scientists that do lots of development. And I think most people here consider themselves research software engineers to some degree. But if you feel that programming is your thing in science, then you could consider joining a research software engineer group and then network with other people that are like you. Let's see, how can we work together? Yeah, so we can, yeah, so we're here teaching things to you. You can help us by joining our community, giving us suggestions. You could even come be a co-instructor with us. So some of us as co-instructors haven't really done this before. So we basically co-teach in order to learn it ourselves. So this is always a possibility. As follow up, there is an after party in Zoom, which is in the bottom of HackMD. As soon as the stream ends, we'll all join there and then we can chat more. And at least I'd really like to hear more personal stories about how you found the course and how we can improve. Oh, we need feedback in the bottom of HackMD. Can someone add that while I'm talking? Please tell us what you think, one good thing, one thing to improve, any other comments. Yeah. And also maybe sometime in the next weeks we could have a discussion or presentation about how we put on the course, like what's the technology we're using behind it and how we actually get everything to work together. At least that would be announced on the Code Refinery Chat. So join there if you want to here. Also about how you can help us, if you like these courses, help us advertise them to more people so that we can increase our audience, get more instructors, get more partners joining. Our strategy for Code Refinery in the future is to make it a partnership of all of the different universities and like Alto and Oslo and KTH and so on, who are basically offering these courses to each other while using these best practices for teaching things either online or in person. Yeah, so if you'd like us tell your university staff about us and ask them to get in touch. Am I missing anything? I'm sure I am, but... Can I mention something, Richard? Yeah. So let's say you like this course and you would like to thank us in some way, like, you know, because we are not in person, like you were to give us a gift for example. The best thing you can do is go and use this material and try to contribute something back. Even if it's a small spelling mistakes, that is the way that you could show your appreciation and join maybe the next sessions that we're going to arrange as a helper, as a instructor. That is, you know, a gift that you would give us if you really think that you had to give something. Yeah, and the... Right now you can still ask questions on HackMD but it will become somewhat less active after the course ends. So there is a Zulip chat that has a help section. Should we paste the address to... I'll just paste an address directly to the help section. That is a good place to ask questions to discuss. So anything related to software development research, and this is a good way to get into the community to ask questions and to answer questions there. Yeah. There's a chat that's already there, so I'll just add the help section. Also to add to something that you can kind of give back, in general, spreading, yeah, spreading information about these courses, about the settings in general and potentially where you got information from and so on. Should we make the courses citable? Are they not? I'm not sure. There's actually a effort towards that now. So we should publish them on Zinodo and... Yeah, then we can add version tags. That's a progress. So working progress. And also I want to encourage everybody to... You can join us as a co-instructor. The best way to learn something is to teach it. And it's really fun to work with other people and discuss. It sounds a bit scary, but it's okay to be wrong and to show wrong things. There is really good pedagogy showing mistakes. I think it's don't work. These are often the best moments. Yeah, we had the question of, what's the best way to get into programming language? What I did with Julia is write an introduction to Julia and teach it with an expert. And I definitely did learn something. So, yeah, it really is... It helps you a lot and you learn a lot. And you don't have to be an expert in a topic to teach in a course. But I think one thing that helped you there quite a bit is you knew one language very well. You have a good foundation. And that's actually what I said earlier. If you have a good foundation, you can. But yeah, come and be a co-teacher in one of these lessons. And you will be paired with an expert. And you will be the person who is asking the questions. You get the most direct answers. Yeah, I think that this idea of mentoring is very important. Like, you don't learn by just reading things, but you learn by going and like sitting, having a desk next to an expert or having someone on call and then basically being able to ask them questions often. And that's how I've learned many things. A good example, someone to talk with. And then I go to the courses and reading stuff. Okay, should we... Yeah, I would want to add to that point, like, especially here in Finland, there's this tendency that if you're going to like a foreign language class, like Thomas can probably say about his Finnish language classes that in our schooling system, we often teach like the written rules, like how you're supposed to use the sentence, how you're supposed to like write what sort of like conjugation or declination or whatever you need in the language. And you learn the rules, but you never use the language necessarily or you use it way too little. And then in the end, it might be hard to speak the language or it might be hard to use the language in a real-world situation. And this I think applies to coding as well. Like I've read so many API pages of different things that I think I know something about, but I really can't say that I'm an expert on any of them because I haven't used them in real-world situations. So it's a good idea to like have the same kind of mindset to us in real-world languages that like you really need just need to use them. And like similarly to real-world languages, if you just like say, like if you speak to a native speaker and just try to say hello, they are, well, they are pleased that you're just trying. And similarly to coding, it's usually a good idea to just like just try and that will get you forward. Because like if you never code, if you never try the language, if you never try stuff, you will never learn it. You just, you learn it after you have used it enough times. The other thing that I would say with respect to that is taking examples, for example, from Stack Exchange or similar websites can help you a lot also understanding the language because what you learn in a course is commonly, yeah, basic things. And you might end up with knowing the basic structure of the language, but you don't need to know a lot of features that the language has. And you encounter code that you're thinking, what the heck is this doing? And on, for example, Stack Exchange, it's commonly a problem that is being posed and people supply answers in very different styles and using very different methods. And yeah, that can very easily teach you how the language is used in different situations. And that, I just had to think about that when I'm thinking about the Finnish course where you're being taught the written language and then people are just speaking in a completely different way. Yeah. So should we thank everyone for attending? Thank all the instructors for being here and see you in Zoom. Thanks a lot and thanks, Richard, for keeping us all together and many other people who are not visible here. Also, people make this happen. Yeah, there's many people in the background that you haven't seen here. We should also update the webpage to mention all the instructors. So yeah, we can do that in a bit. Okay, so... I mean, there's many people in the background. There's definitely also Richard doing a lot more than is visible. And Richard, do you want to show you set up on the course once? Maybe if I can find the right camera here. Let's hope Zoom pauses well. It detects my new camera. Zoom is... This is my recording studio here. Yeah, well, see you in Zoom then. Okay. I guess. Okay, please come by. Okay, bye, everyone. Bye. See you next time. Bye.