I'm very happy to welcome Dr. Heidi Serbel to this keynote. Today's sponsor of the day is Roche. Thank you very much for your support for the conference. And yeah, we are very happy to have Heidi as a keynote speaker. Heidi is a biostatistician. She studied in Munich and then came to Zurich for her PhD. She co-founded the Zurich R user group that is kind of at the origin of this year's edition of the youth R conference. She's an open science and reproducibility advocate. And she has recently been awarded the newcomer of the year MAI award from the German Informatics Society. She will tell you a bit more about her career in the keynote, so I will not tell you everything now. But she's now working at the Jörner Institute where she's working on advancing methods in teaching and research. And I will not talk any further, but leave the floor to you, Heidi. Thank you very much. Thank you so much, Dorothea. Do you want to add something? If you have questions during the keynote, please ask them in the Q&A. And we will happily get to them at the end of the keynote. Thank you very much. Perfect. Thank you so much. I'm going to start sharing my slides now. Someone just wanted to come in. Sorry. Yeah, so thanks so much for having me here. It's such a great honor to be speaking at this year's youth R. So my first youth R was in 2015 in Alborg in Denmark. And I looked at the keynote speakers there and it was like, wow, what amazing people. And it's incredible to be a part of such an esteemed group now. So thank you so much for inviting me to give this keynote. I'm going to talk today about research software engineers and what they do, what it means to be a research software engineer, what the troubles are, and all of this in the context of academia. You can follow me on Twitter. My Twitter handle is at Heidi Bayer. And as Dorothea said, I work now for the Yuna Institute, which is a company that deals with medical devices and certification of medical devices. And we're doing a lot of education and research now. And I'm also an independent researcher with ICDOR. So if you're an unconventional researcher, ICDOR might be a good home for you. So you should check it out. So my slides and everything are licensed under a CC by license. So you're welcome to reuse any of the things that I have in my slides, including my drawings. So let's see. Yeah, so as Dorothea mentioned, I'm going to talk a little bit about my own path before I dive into the topic because I think it tells a little bit about where I came from and why I'm interested in this topic and why I'm so passionate about these things that I'm talking about today. So I did my bachelor's and master's in Munich in statistics. So I actually learned R in my very first year of university and fell in love with it directly. My bachelor thesis already was an R package. So if you're interested in analyzing unexploded bombs, then the high-risk package is for you. Then after that, I went to Zurich. I did my PhD there under the supervision of Thorsten Hothon and Achim Zaylas, which many of you might know as one of the big people in R, one of the important people in R. They really gave me everything to pursue my passion in R in software and in open science. After that, I went to do a postdoc back in Munich in a medical informatics project. Then I got the chance to do a professorship for half a year. So in Germany, we have this thing where when a professor leaves, then they sometimes allow younger researchers to play a professor for half a year. So it was Professor Heidi for half a year then. And afterwards, I started two postdoc positions at the same time at LMU and at the Helmut Center in Munich, where I was already kind of a bit of an unconventional postdoc working mostly on open science and reproducible research with a focus on AI and medicine. And then I applied for a group leadership position at Helmut's AI, which I was very lucky to get. And I really thought that this was going to be my dream job. And then it turned out that it kind of wasn't my dream job, because I wasn't a real researcher anymore at the time. And I just figured I need to change something. And I need to tell people that, yeah, this is not my kind of not my identity anymore. And I'm going to talk a little bit more about that in a minute. And now I'm actually more on like the meta level. So I'm thinking a lot about how we can do science and education better and try to implement that in. Yeah, a kind of new way and with new ideas in a new setting as well. So this is where I'm at now and through all these things through all these many jobs that I had already in my short career. One or two things were always with me along the way and these were software and open science. So as I said, I already started using our during my bachelors. I got into open science because my first real research project during my masters turned out to be such a big mess. I had files flying out all over the place on my computer and I thought I need to do this better I need to become a better researcher. And that's how I got really into reproducible research and through that path I learned about this whole open science movement and the community behind it. And yeah I stuck with it since then. Why am I giving this talk. It's a little bit born out of this idea that I kind of was in paradise. And I had the dream job so I scored a group leadership position. I was really in a great place and I was still pretty I mean I'm still pretty young and being a group leader at that age was really a success and everyone thought oh Heidi's going to become a professor at some point. And so, at the same time I felt like really struggling and really like I was in this paradise, but somehow something was not right so this is here depicted by the snake strangling me. And I tried to figure out what it is and somehow it was that I wasn't fitting into this clear picture of what a researcher needs to be and what a researcher needs to do because I was doing a lot of things that wasn't exactly writing papers. Now, what does it have to do with RSE. First of all, let me talk a little bit what research software engineers actually are and what it means to be a research software engineer, because maybe in this community. The term is already a little bit known, but like in general people don't really know what a research software engineer or RSE actually is. So what do RSEs do. RSEs obviously develop software but they develop software that's specific to research so they need to not only be able to. Yeah, right software but they also really need to have an intricate understanding of the research field that they're working in. They generally code so that can also be analysis scripts and stuff like this. Sometimes they teach about software to researchers, they support research projects in terms of software. Yeah, they consult researchers with any kinds of software problems or I mean there's also specialized RSEs who work on very specific problems and help a lot of researchers with that. So let me go into a couple of personas to give you a bit more of a deep understanding what research software engineers are and what types of research software engineers are out there. Well let's think of one person she's a PhD student. She writes software as part of her research project, but her supervisor tells her hey you have to have like three papers at the end of your PhD or otherwise you're not going to get your PhD. So she would actually like to code more but she needs to think about her career and write papers. And then there's this guy and I assume that every institution has some a person like this, so he's the person that everyone goes to in case of problems so imagine you have an issue you don't know how to implement something and are, and he's the person that you can go to any time he's super kind and always willing to help, although of course it's not his job to do that. Then there's the researcher she works in a lab she needs software and other software skills to really do her research in the best way possible and she learns what she needs to do so but she doesn't do much more than that. There is a reproducibility guru he like is really into reproducible research and learns all about the software tools that he needs in order to make his work really really reproducible and also maybe helps other people to do so as well. And then there's the classical software person she's a trained software engineer, she's hired to work on software for a research project so imagine maybe an app for questionnaire or something like this. Eventually she decides to leave academia because companies value her skills more, and she can actually have a career and a great salary as well. And then there's me. I really liked research I really do, but I love, I really love and enjoy thinking about open science and reproducibility I love coding in our. And actually, as you see today, I get invited to talk about open science about reproducibility about research software engineering, and that much more than about my actual research so just FYI. My research has been on model based trees and random forests. So if you're interested, check out the party kit package. And, yeah, I, I use that for the context of personalized medicine and personalized treatment effect estimation, but people weren't as interested in my actual research then they were interested in the things I did on the side, the science work. So, I actually just left the classical academic career in order to be able to do these things that I enjoy doing so much. And it's kind of weird to go to a company in order to be able to pursue the passion of promoting good research practices. So, what I want to leave you with, and this is really important software and RSEs are everywhere in research nowadays. So there's almost no research project these days that has. Yeah, nothing to do with research software so let's think about biological research for example, software everywhere. Digital humanities is a field that's by definition digital and need software medical research psychological research or even one of my favorite projects that has been going on in recent years, the mosaic expedition where they sent a ship into the ice and drifted through the ice for earlier. There's a group, a team of RSEs in the background, just figuring out how all this data can be managed in the end. So this is really something where we see very clearly how research software engineers are so much needed for these kinds of projects that really, yeah, that are really visionary and think about how will this earth be in a few years and what is happening to an environment currently. So all the big questions that we're doing in research right now are dependent on research. And of course in research, but also in research software.  Because you're somewhat interested in research, I guess. And so I think most of the people who are listening right now are, in fact, research software engineers. And it's important for me that you think about that because if you identify as a research software engineer, then we'll manage to figure out all the problems that I'm going to talk about later in this talk. And now I want to do a little bit of an excursion and talk about my favorite topic which is open and reproducible research. And what that actually has to do with research software engineering, because I strongly think that these two things are super closely connected. And we cannot think good quality research nowadays without thinking about good quality software. And I do that a lot if I talk about open science. There's a couple of things that I usually say. So, for example, I tell people to make their code available and reusable for others. I tell people to publish preprints. I tell people to use version control. And in general, I tell people, well, why don't you just make everything available for everyone. And I am aware that this is not easy. So I'm always trying to be proactive and show also how to actually do all these things. And I also, I mean, I tell people that they don't have to do it all at once and of course they don't have to do it. But this is would be the perfect world if everyone would try to work openly. So, if I'm talking about these things and then of course I show them which tools I personally use, and which I would recommend and this is one of the slides that I sometimes show and we were not going to go into every detail here but I just wanted to show you that there's a lot of different tools that I'm using to make my work reproducible. There's a lot of, especially technical things that I am using in order to make my work reproducible. And this is why I'm showing you the full slide with all these words and not to like go into the depth of everything but to make you aware how technical reproducibility and, and, yeah, computational reproducibility at least really is. So, I talk about things like version control. I talk about things like virtual machines or Docker. I talk about make files. I talk about raw oxygen things like those and they're all like highly technical and what we get in the end are researchers that look like that. So, they're trying to do a good job, and they're trying to implement these things that I'm recommending. But let's be honest, not every researcher has the time and the background to learn all of these things and I personally think not everybody has to know everything and be able to do everything. So, yeah, the main point here being open science and reproducible research require tremendous software skills. Yeah, and somehow I think we need to figure out the way how we can use these modern reproducibility tools without getting completely frustrated right so we don't want to see researchers like that in this GIF better just like giving up saying I don't want to do this anymore. Let's just quit, quit it all entirely. So, what do we need? I think we need to work together we need to have teams of people who are able to do different things. And so I think in terms of software and reproducibility we need people who develop helpful tools. We need people who help research and finding and learning these good tools we need people who support researchers with computational reproducibility and support them in writing software. So if you're surprised, surprised, these people are called research software engineers. So I think research software engineers could help as parts of teams of research teams, but also as yeah teams of consultants that go into different research teams and help there. And this right now already in statistics so we have statistical consulting at universities where people can go to and ask for help with statistics. We have statisticians as part of medical research teams for example, and who do all or who help with with the statistical work. Why can't we do the same thing with software as well, because this seems to work. And we're already now seeing that, at least in the UK or in places where universities and research institutions are implementing this. So it really seems to work and I think that this is the way forward for for research is to allow for different kinds of people to be part of a research project. Let's get to the tricky part of us because, of course, the UK. There we see that a lot of this is already being implemented and research software engineers can have a career, although it's only getting started there as well. But in most places what we see is that research software engineers are hired on short term contracts.  And if they really want to focus on research software and not focus on writing papers all the time, then they also have no career path. And at the same time, these same people are not only highly skilled at software engineering, they're all so highly highly skilled in the specific research field that they're working in. So they're some of the most skilled people that we have in research. And of course, since software is so much needed in research, these people are very much needed for research project. So we have these two sides of shitty salaries, no security, no career path. And at the same time, they're really so much needed and should be valued so much more. And so I think one of the big questions that come with this is why are career paths and in particular academic career path so so stiff. So because right now you're having a career if you're good at writing papers, lots of papers if you're good at publishing in high impact journals, then you're well off, then you'll have a career, then you'll be professor at some point, and you'll get a permanent position. But what if you're interested in other things? What if you want to do a great job and promote research by writing good software? Of course you can write software papers as well but really should this be the path we have to go if couldn't research software by itself be a valuable output. And I think this is one of the major points that we have to address if we want to allow for careers for research software engineers and essentially also many other people who are super important for research. Let's think about data managers. Let's think about scientific journalists. Let's think about scientific managers. There's all kinds of people who are super, super important for academia for the scientific endeavor, but they're not as valued as people who just write papers all the time. And I'm not saying that writing papers is easier. Writing papers is not something that we want, right? Of course this is also one possible research output, but we need to think a bit more about like allowing for a different range of research outputs. Couldn't a podcast be a research output. Couldn't software be a research output. Couldn't data be a research output that we value as much as we value papers. So, going back to this image is academia really a paradise for everyone. And I think it's definitely a paradise for people who enjoy the things that we value highly in academia. But it's not as much a paradise for people who don't enjoy it as much. And for people who want to do a bit other things, have other kinds of research outputs. And this I think is a problem because right now we're like, okay, here's this t-shirt, this researcher t-shirt, and put it on one size fits all. But it's not the case. Not everyone is the same. Not everyone enjoys or is even good at this one task that we give researchers, right? And I also really, really think that it shouldn't be this way because it's great that we have people who write software. I think it's great to have people who are good at designing great websites for the public. I think it's great that there's people who produce videos or other kinds of research outputs that communicate what you do other than just papers. And I think this is really important. And we shouldn't think in this one size fits all way. So what would my optimal world look like? And I am aware that this may sound naive at first, but I really think that if we think would think about this a bit more and if we would support people who really have good ideas. Then I think an optimal world would look like that everyone gets to work on something that they're passionate about. And I think this might not be possible like entirely and fully and for every part of your work and I think that never will be the case. But in some sense, I think this can be possible. Now the question is, of course, how do we get there? And yeah, I really think that the best path towards this goal is by growing and building communities around topics where we need the big change. And luckily for us, there is already an RSE community and luckily this community has already reached many, many goals, at least in parts of the world. So where does the community come from? So the term RSE was actually coined in the UK in March 2012. And from there on, the movement in the UK started. So we see that for almost 10 years, research software engineers in the UK have been pushing for the goal of having careers for research software engineers for making software first class scientists in science with the slogan better software, better research, which makes total sense to I think everyone who's listening right now, but which is important to say again and again to everyone. In Germany, that was to my knowledge, the second community that started on like a country basis. The community was actually founded at an RSE conference in the UK in 2016. The association was founded in 2018. And we actually had our first conference in 2019, which was like such a great success and it felt like a start of something big. And I think we're going to grow something really nice out of this. Because RSE community is popping up now all over the world. And I put a link in here. So there's Australia, New Zealand, there's Belgium, there's the Netherlands, there's the Nordic countries, there's the US, who already have RSE communities. And you can found one in your country, wherever you are. Because there's so many RSEs out there. And I think a lot of the people who are listening right now are now thinking, oh, I'm an RSE as well, what can I do and feel free to, I don't know, discuss this in the slack or whatever, and just get together and form local chapters and local communities. Because I think this is the starting point of how we can achieve something and change research for the better in terms of research software. And now I also want to talk a little bit about what the R community can do, because obviously the R community consists of many, many research software engineers and these two communities, the RSE and the R community are very much overlapping in terms of what they want and what the goals are and also the people as well. And so I think the R community and the RSE community should work hand in hand. And for this, we had an incubator session actually on Tuesday at USAR, just about this topic, what can our community do and how duties to communities fit together. And here are the things that we came up with or at least a short summary of this. There will also be a blog post about the incubator and what we came up with, but here just a short summary, what we think the R community could do. First of all, obviously, be part of the RSE movement. We could do things like building an R community within the RSE community, so get people together who both are users and RSEs. We could host events together. We could give RSE talks at our conferences, like I'm doing now, and vice versa. So we can just work together as community, as one movement. And of course, we should talk about it. We should create awareness. So I wrote down these three words, talk, teach, try. So talk about the term tell people that RSE is a thing. And yeah, really, every time I talk about this, someone comes to me afterwards and says, oh, I just noticed I'm an RSE too. And this is really a nice feeling to have. And teach about research software, teach about how to make research reproducible, how to implement good research software, good research software practices, and so on. And maybe try it. Try to become a research software engineer if that's something that you want to do, although right now it may be still pretty hot depending on where you are. Another thing is of course, lobbying. And this is what I think we need to do a lot now is talk to the people who are in charge and tell them, hey, this is kind of important software is such an important part of research nowadays. We need to do something to improve research, and not just always waste money by having one, for example, one PhD student work on a software project and then this one PhD student leaves and a software project dies. And then five years later comes a new PhD student who writes the same thing over again. Right, this is just a waste of money, a waste of resources, a waste of time for everyone. So we need to talk to the people in charge we need to talk to the funders, we need to talk to the heads of institutes to to politicians and tell them, hey, this is important. This could really change and improve the way we do science. And actually, I've talked to a couple of heads of institutions in the Hamilton's Association recently, and they are quite aware. And I was really surprised how aware they are of how important research software is. And I do think that we have a pretty good shot at changing the way things are here because people are already noticing and they want digitization and everything so I think there's some something we can do. If you're in this position that you can hire people, you can consider hiring someone. So actually, I gave a talk about this, a similar topic once and afterwards I got a message of someone who's told me, well, I heard your talk and now I'm hiring an RSE. And I was like, such a great feeling for me. So, if you do so, tell me because this is going to be a nice outcome of this talk, if someone does. And then, of course, we need to think about how we evaluate people in science.  But maybe we need to think about, like, we can't only do these super simple measures because people are going to try to have a career and they're going to try to follow these simple measures. And it's not necessarily the best for science. Maybe we need to think about people having a portfolio rather than just a list of papers, a portfolio of projects, portfolio of research outputs in general. And then finally, we also talked about other things that we could do, like, maybe we could implement something like a podcast series called something like Meet the R Engineers. There could be books about research software engineering with R. Actually, in this, I looked into the notes of the session on the books and it was really nice how they came up with, like, not only one book idea, but several book ideas. And I think there's something coming. So stay tuned for books and podcasts on topic as well. And yeah, finally, there's so many other things that you can probably do that we didn't even come up with in these 45 minutes that we had this short time. But if you have any ideas of how we could improve the situation for software and science, then just go ahead and do it. There's nothing, nothing much, at least stopping you. And stay tuned for the blog post about the incubator outputs. Now I'm almost at the end of my talk, and there's a couple of things that I want to still mention. So this is more of an advertising end, but it's very much connected to the things that I've said before. So there's two initiatives that I want to mention in this context, which have helped me personally to figure out how to build community and how to deal with this whole idea of reproducibility, working on open projects and stuff like this and these projects are called Mozilla Open Leaders and The Touring Way. So let me first talk about Mozilla Open Leaders. This is a training program for people leading open projects. There's actually several folks now that go into specific directions, for example, open leaders in the life sciences and such. So we could maybe think about forking this idea of training leaders for something like research software groups or something like this. So this is one thing that I wanted to mention. I was trained through the training program, and I learned so much through it. And it's really a great initiative. The other thing that I want to mention is The Touring Way, which to the outside world seems like an online book. So it's an online book about reproducibility, collaboration, project design, ethics and so on. But really, it's much more than that. It's an entire community and it's a really cool community for people like us, right? So the whole thing is focused on data science. And a lot of the people who are involved are research software engineers, others are data scientists, others are ethicists who work in data science. So it's really a cool project that anyone can get involved in. And yeah, check it out. It's a really good book. If you want to learn about how to make your work reproducible, this is, I think, in my opinion, the number one resource. So that's why I wanted to mention this as well. And finally, I want to make two advertisements about things that I have done recently and that I will do recently, which are my two podcasts. The first podcast is called Open Science Stories. It's very short episodes. Each episode is between three and 10 minutes. And it's little stories by people and very personal stories, actually, by people about something related to open science. And it's, I think it's turned out really great. And everyone who created an episode, all the storytellers really did a great job. So if you're interested in open science and like just getting into it and trying to figure out what it actually means, I think Open Science Stories is for you. I'm actually, I've published the last episode of the first season this morning. And I'm actually currently looking for a new host because I think for this kind of podcast, it would be nice to rotate hosts every season to get a little bit of different ideas in to get a little bit of different kinds of people into the podcast. So if you're listening to this and you think, oh, this is a great idea. I would love to do something like this. Get in touch with me because you can become the co host. You can also do it together as a group and be co host together, whatever is fine for me. I would love for this to to go on and to move on with someone who loves the idea of the podcast. And then there's one other thing that I want to mention, which is a podcast that I'm starting now. I've just recorded the first interview and it's so this one is an interview podcast called reboot academia and I'm sorry it's going to be in German. So this is for the German speaking folks out there. But this is essentially about the topics or some of the topics that I've talked about today. So it's about how we can rethink the way we do education in universities and in research and rethink the way we do actually research. I'm currently just getting started, but you can follow me on my journey, creating the podcast and I'm creating a blog so the QR code here sends you right to YouTube to the playlist that is the blog. So blog is a video blog for those who don't know. And I'm just recording a couple of videos with my thoughts but also with the journey itself. So if you're interested in that, check it out and the podcast doesn't have a website yet because it's not there yet. But if you follow me on Twitter, I will let you know about it. And with this, my keynote is already getting to its end but I'm really looking forward to your question questions. And finally, I want to thank again the amazing team behind this conference. I've felt really, really informed and really well taken care of throughout this whole journey. As a keynote speaker, so this is very new for me to be in such a prominent role. And I know how much work it is to organize use are as I was in the team last year. So I think I really think you did an amazing job of organizing this and you can feel extremely proud and how professional everything is and how you're welcoming people and. I think it's amazing. Thank you. Well, well, thank you Heidi for this great talk. I have a couple of questions lined up we will see how far we get in the 15 minutes that are left. The first question, are there any funding bodies that have specific funding sources for RSEs? That's a very good question. And there definitely are. And I'm probably not aware of everything. So in Germany we had recently a funding call for actually maintenance of existing research project research software projects, which I think is a great idea. That was by the DFG. I know that there's other kinds of rather specific funding bodies that help with research software or focused on research software. I can look them up and post them in Slack because I don't have them on my mind right now but maybe others can also chime in and we can collect something in Slack. I think there was supposed to be a group also in the incubator but I don't think we had enough people on that session right. Yeah. Yeah, just join the Slack group. I think it's called HashKeySybal. And there we can continue the discussion on how to score funding in this direction. So I'll post the links that I have there because I don't have it in my mind right now. Excellent. Thanks. So yeah, please join this channel on the conference Slack also to continue the discussion after the keynote. I have another question, a bit from the other side. So in your opinion, what would you suggest to a funding agency that wants to support RSEs? Is there a need to shift incentives? What is the one thing that they should start with? That's a really good question and that's a really big question that I'm not sure I can answer like in a few words. A couple of thoughts on this is that we want to really fund, if we want to really fund software and support software projects, then we don't need to only think about kickstarting research or software projects, but we need to also think about long term maintenance and long term funding for these key projects that continue over years and years, right? Because maintenance is a big issue that we have, I think especially in research software, because it takes a lot of time, it's not very prestigious. And I mean, this is one thing where I think we should start. Definitely incentives. So if we give out money, lots of money to research projects in general, I think we should think about not only counting again how many papers came out of this research project, but also did the research project end up with a good software, with maybe even a software community, because community management and this whole thing is also super important and super time consuming. Yeah, these are things that I think we should start thinking about when we think about how we can we improve the funding situation for software and science. Yeah, these are just a couple of thoughts, but that's definitely not everything. Yeah, I could probably talk another hour about this. Thank you very much. So another question was where to draw the line between what a PhD or postdoc should do in terms of programming and where the help of an RSE should be requested. So, where do you draw this line? That's, I don't know if that's a question that I can answer. So, I think it depends on, first of all, is there actually anyone you can ask, because if there isn't then, well, what, what choice do you have. And also depends on you really. So I really enjoy getting like deeply into these technical things and like figuring it out reading books about good coding and like, I really enjoy doing that. And I did that a lot as a master's student as a PhD student. And that's how I got my skills in that direction. I also joined like courses. So I took a lot of courses at the Zurich R courses and stuff like this, because I just enjoyed it and I wanted to learn it for myself. So I think it depends a lot on you and what you feel capable of doing. I don't think I can answer that in like in general. If you feel lost, then probably then at least it's time to ask someone. Thank you. So another question was how do can we explain to people the difference between an RSE and a normal software engineer? Do you have any thoughts on that? Yeah, and I think that's really, really important because I know that universities have had the idea or recent projects have had the idea to just hire software engineers from a company. And so from what I've heard at least, this didn't go too well because they don't understand the way research works. So they don't understand, they don't have the knowledge they need about the research itself because every research topic is different and they're all super complex because that's why we do research about it. And the way research as an endeavor works is often very different to how software projects and companies work. And so I think the big, big difference between a research software engineer and a regular software engineer is the knowledge and the intricate understanding of the research project at hand. And also like how research in general works. So there has been a survey actually about research software engineers and they were asked what kind of degree they had. And I think almost everyone had at least a master's degree and most of them had a PhD. So they really understand research as well as they understand software. Thank you. Another question was so for maybe from when you're in a not so high level position. How do you advocate for IC? How can you convince your professor to go for that road? And maybe another question that is kind of linked as this is not an established field. How do you build yourself a career in research software engineering? Yeah, that is the big question. So this is really something that I have been struggling with myself because I'm not like maybe a classical RSE, but I'm also a person who's like, yeah, very much somewhere, definitely in research, but not the classical researcher. Right. And I've really been struggling in the past years with finding a place for myself because I was doing a postdoc.  But I, I'm kind of different than the others. And so that's how like, that's how my job interviews were like, I do this, this and this. I'm probably not going to write as many papers as the other postdocs. I hope this is okay with you.  I think if you work with someone who doesn't understand it at all, and I don't think you have much of a chance. But I, I always try to be as open as possible and just tell people where I'm at and what I want to do. This maybe also led to more job changes than other people have in, in this amount of time. But I've been always very lucky with the people I've been working with in the sense that they understood this issue for me and they, they enjoyed that I was being open about it. So I just try to talk about it a lot and be very open about my thoughts on this and advocating for research software engineering and stuff like this. Building your own career, when there is no career path in this area is definitely a huge risk. So I can't say it any other way. If you're in a country where RSE is not a career path that's already there, then if you go towards that route, it is a risk. That's, that's what it is. And in the end, I think the lucky position that we're in is people who are able to work with software able to work with data that this is also a skill that's useful in many areas. So maybe we're in the great position that this is a risk that we can take. So, but I don't want to say that, hey, just go for it. It's easy because it's not, you're going to have doubts and it's going to be crazy and you might not succeed. I don't know. You might not never get a permanent position at a university if you just focus on software depending on where you are. Yeah, thanks. So, another question was, if you have thoughts about RSE outside of academia, so like in the corporate world, in NGOs, in government agencies. Yeah, I'm kind of that now. So I switched to accompany the UN Institute, because there I was promised that I was going to be allowed to do the things that I wanted to do without the pressure of having to write papers but with the possibility to write papers. So there are definitely companies that can do that, where that can work. And I think their career paths are maybe a bit more flexible, although I'm going to be honest, just because I've worked at a company for a month now I'm not like, I don't understand the corporate world yet. So I'm probably not the best expert to talk about NGOs. Sure. I think, I mean, that's probably very similar just with a different spin. But if they're doing research, then software is going to be a topic for them, just as well as at other research research projects and research institutions. I hope that answers the question. Well, otherwise, feel free to come back to Heidi in the Slack afterwards. So we are almost at the end already. I think I would like to ask one question myself. So if someone thinks, well, this sounds really cool and I want to start advocating for RSE, but there is no local RSE group or etc. Is there any support that they can get and where? That's a very good question. So definitely, if you're here now, right now, and if you say, oh, I want to do this, I think start writing in the Slack actually, there might be someone else from your country who thinks the same right now. And otherwise, get in touch with the existing communities. So in the slides, and I posted the link to the slides also in Slack. In the slides, I have a link to the list of all the existing communities and I think especially the community in the UK is super knowledgeable and helpful in that sense. And they can maybe help you reach out to people. But all the communities are, I'm sure, super helpful and open because we all have the same goal. So just, yeah, there's also an RSE Slack, which you can find through the same website or, I mean, Twitter might work as well. Yeah, that's my recommendation for now. The hashtag that you can use for RSE on Twitter is RSENG, so NG in small letters, because I think RSE itself was already taken. So most people use the RSENG hashtag and you might find someone through Twitter as well. There's different routes, but I think these are probably decent ones. So thanks for the question. I think that was very good. Well, thank you very much. Thanks again, Heidi, for coming to give this keynote. I think there were some very important insights. And if your question was not answered now during the keynote, please reach out on Slack and ask again and continue the discussion there. We now have a 15 minute break and then the next sessions are starting. We have a session on data visualization and a session on our introduction. So please join us there. And thanks again, Heidi, for coming and thanks to all of you for coming to this keynote. Yeah, thank you.


Today, I want to address a serious issue within the Linux community, and that is the issue of this debate that people love to have between snaps, flatpacks, and app images. Because I think most of the community do not realize that snaps, flatpacks, and app images are actually not the same thing. They don't actually serve the same purpose. Yes, they're all three packaging formats available for Linux if, for whatever reason, their Linux distribution doesn't package a piece of software natively. It's not available in your distribution's repositories. Then you can go grab a snap or a flatback or an app image, but they don't actually do the same thing. What snaps do is different than what flatpacks do versus what app images do. And this is one of the things people don't understand, because I see these pointless debates, especially in places like Reddit and chat rooms and things like this, where the biggest one I see all the time is, why doesn't Canonical, the company behind Ubuntu, why don't they drop snaps and just adopt flatpacks? Because flatpacks are better. Everybody else is using flatpacks. Why doesn't Ubuntu and Canonical drop snaps and adopt flatpacks? Well, let's discuss that. For one, Ubuntu is a server distribution, primarily Canonical, the company behind Ubuntu, primarily makes their money in the server market with Ubuntu Server. And guess what? Of these three packaging formats, snaps, flatpacks, and app images, only one is actually built and designed to work with server software. And that's snappacks. So will Ubuntu ever drop snaps, which actually work on the server, to adopt flatpacks, which doesn't? No, absolutely not.  Another thing I don't think people realize, especially newer to Linux users that see all these people shilling for flatpack, is Ubuntu created snaps long before flatpack existed, right? It's the older packaging format. It's not like they created a new thing when flatpack already existed. They created snaps and then later Red Hat created flatpacks. So it's not like they're anti-flatpack like they decided to go a different route than flatpack. Flatpack wasn't around when Canonical created snappacks. Originally, they were called snappy packages. Before that, they were called click packages. And they were designed for Internet of Things devices, for mobile phones, and again, for the server, which again is primarily what Canonical is interested in. And that's why snaps, again, I just want people to understand snaps and flatpacks and app images, they do have real differences that never get addressed. And that's what I'm going to address today. First of all, let's talk about who created these packaging formats. Obviously Canonical created snap packages for Ubuntu. Red Hat created flatpack. And then App Image actually was created by an individual named Peter Simon. So there's no corporation behind it. It's not a corporate thing the way snaps and flatpacks have a corporation driving their development. App Image is more of a community-based project. One of the big selling points of all three of these package formats is the fact that they have support for sandboxing. Now, just because they have support for sandboxing, that doesn't mean sandboxing is mandatory. Because with snaps, you can have a snap that is not sandbox. That's not typically how Canonical likes you to package snaps. But it is possible to do that. Flatpack, though, it is mandatory that you sandbox your app. And with App Images, they don't really care. You can sandbox it if you want, or you don't have to. Another difference is the ability to run these programs without needing Brute or Sudo. So with snaps and flatpacks, you're going to need root permissions to actually install the snap or the flatpack. But after it's installed, any regular user can actually launch the package. With App Image, you don't need Brute or Sudo at all. Because App Images, you just download the App Image and you run it. You execute it. So you don't really, it's a little bit different. Again, there's these minor differences between these three packaging formats. One area of gripe is the native theme support with your GTK themes and your Q themes. Now technically, snaps, flatpacks, and App Images all have native theme support. But honestly, the native theme support in all three is a bit flaky. I would say Flatpack probably has the best theme integration, but it's not great.  I would say App Images are probably the worst of the three. One big change in recent years is that for a long time, snaps were the only one of these three package formats that actually had an online store, an app store where all the snaps are listed on a store and you can go find any snap package that exists. It was one of the reasons why, especially in the early years of all three of these package formats, snaps really had a lot more adoption than flatpacks and App Images. It's because it was just easier to figure out where all the snaps were. They're on this store called Snapcraft. I can just go search for a package, boom, hit the install button, and away I go where flatpacks and App Images really didn't have a central store, a central repository online where I could go search for all the flatpacks or all the App Images. But that's changed here in the last couple of years. Flatpack created FlatHub, so now they have their own Snapcraft kind of site called FlatHub where all the flatpacks are, right? And then App Image recently created a store as well called App Image Hub as well. So now all three of these packaging formats do have this online web store, app store presence. Let's talk about updates. So snaps and flatpacks and App Images all have support for automatic updates, meaning the packages will automatically update themselves. You don't really need to do anything. Now with snaps and flatpacks, you can turn off the updates if you don't want them. I will say out of the box, most App Images actually aren't set up to auto update, but App Image does have that capability if the person packaging the App Image wants it. One of the big complaints from the haters of snaps, flatpacks, and App Images is the size of these packages. And the reason these packages are a little bigger than native packages is because they contain a lot of dependencies, a lot of needed libraries. Of the three package formats, which one is the smallest in size, App Images tend to be a little smaller than flatpacks and snaps by comparison, but none of them are slim. All of them are going to be a little heavier than a native package. But that's just the nature of this thing. You can't bundle all the dependencies you need to have a self-contained application without it being bigger than a native package. That's just a trade-off that's always going to be there. One of the big drawbacks with snaps is the fact that some snap packages, not all, but some snap packages do have a noticeable lag in start time. They take a little longer to start up when you first open the program. As usually big programs, things like LibreOffice, for example, may take an extra second or two compared to the native package format of LibreOffice. But again, it's just a second or two, and it's not every program. I have a ton of snaps installed on my system. Most of them I never even think about start time because they pretty much are instant for the most part. It's mainly the bigger programs that is kind of noticeable. Another drawback with Snap is the Snapcraft Store and all the back-end stuff with Snap because snaps were the only one to have that central store in the beginning and Canonical owns it. It's all proprietary on the back-end. They haven't open sourced the Snap servers, now the snap packaging formats. When you create your own individual snaps, you can license that as whatever. It can be free and open sourced software, but just know especially the online stuff with the Snapcraft Store and all of that, all of that is proprietary software. Now let's talk about some of the drawbacks with Flatpak. My biggest complaints with Flatpak, and I have two. The biggest complaint I have with Flatpak is how you run a Flatpak, how you execute it because you can't just type name of a program in a terminal or a run launcher and it launched that program as a Flatpak. You have to do Flatpak, run, and then the name of a program, and the name of the program is going to be something like com.flathub.nameaprogram or whatever it happens to be.  It really makes, especially scripting with Flatpaks a little weird. The other big disadvantage of Flatpaks is, again, Flatpaks is not designed for the server, right, where snaps, you know, I can set up a NextCloud server. I actually have my own personal NextCloud server. I think I did a video one time installing NextCloud as a snap.  It's seriously one of the most amazing things ever. When you understand snaps on the server, like it clicks, like it really makes a lot of sense, and Flatpaks, unfortunately, doesn't have anything like that available. And some of the pros and cons with app images, I think one of the coolest thing with app images is they're essentially like a .exe file on Windows, like an executable on Windows, right. You just download a program, this app image, right, and then you just execute it. You don't, you don't insert all anything, right. It's its own self-contained ready-to-run program, and I love that, and it really is convenient, especially if you're going to keep multiple versions of the same program on the system. They're just a separate package, right, this separate executable that you keep. And if you want to go back to a previous version of a piece of software, for example, I keep multiple versions as an app image format of Kaden Live on my system, just in case, because sometimes I want to open older project files that I saved in an earlier version of Kaden Live, and app images just makes keeping some of these older pieces of software around a little easier. Really the biggest disadvantage of app image is lack of adoption, lack of programs available as app images. One of the things that Snap had in the early days was it had that Snapcraft store, and it had Canonical pushing it, and there's a ton of programs packaged as snaps. And here in the last couple of years, once Flatpak kind of got its act together, especially creating Flathub, Flatpaks have become rather popular here in the last couple of years especially. And pretty much there's plenty of Flatpaks. There's plenty of snaps, chances are you're going to find whatever popular program you're looking for packaged as either a Snap or Flatpak or both. That's not the case with app image. App image kind of lags behind in packaging because you need people to actually go and package these things, right? And corporations like Canonical can pay people to work on snaps. Red Hat can pay people to work on Flatpak, right? There's money behind this stuff. It's a big deal to those corporations where app image being a community project, unfortunately, again, it lags behind as far as just the number of packages that are available in the app image format. In the end though, for me, I use all three formats because sometimes I find pieces of software that's only available in a specific format. It's only available as a Snap or it's only available as a Flatpak or it's only available as an app image. And I don't care if I want the program, I'm going to install it in whatever package format because why wouldn't I? You know, I'm not going to not run a piece of software that I really need because for whatever reason, I have a problem with a package format, right? Some of you guys take these package format things seriously to the point where I've actually seen people online say they won't run a piece of software if it's only available as a Snap or they won't run a Flatpak or whatever it happens to be.  Ultimately, I think we, the Linux community, we just need to calm down a little bit. We need to lower the temperature, especially on these debates. Snaps versus Flatpaks and Snaps versus App Image or whatever it happens to be because those package formats are not even remotely the same thing as I've already demonstrated. Anybody that is starting one of these idiotic threads on Reddit, like Canonical needs to drop Snaps for Flatpaks.  Snaps work on the server. Ubuntu is a server operating system. Flatpaks don't. But I'd be enough when these people post these ridiculous threads on these Linux subreddits, they'll get like 2000 thumbs up, you know, these weird upvotes and everybody will, yeah, you tell Canonical, man. And I'm like, oh, they're not the same packaging format. They don't do the same things. That's all I wanted to say. Peace.


What's up everyone? Takedown here. Welcome back to another video since it is tax season. Today we're going to be talking about filing your taxes for your YouTube earnings. Let's get right into this. So for me personally, this summer of 2020 is whenever I started to get ads on the channel and started to make a small income. Of course, nothing to replace a full-time job, but it was something enough that I do have to report it for my taxes this year. This is going to be the first year that I have to claim taxes because the summer of 2020 is whenever I started to make income on YouTube and I have to claim it for my taxes this year. Now, I did not know anything about how to do this and what I was able to claim as obviously the income, which is easy to determine, but also what I can claim as expenses. Luckily, I'm in a few Facebook and Reddit groups for YouTube and a lot of people were very generous in helping me out on how to file my taxes this year when it comes to my YouTube earnings. The first thing I want to mention is I am a Canadian YouTuber, so I do have to file my taxes with the CRA. Now, depending on where you live and how you file your taxes, the forms and how you file your taxes might be different, but I believe the principles of what you can claim for your expenses should be the same. Here in Canada, any way that you make money online, you have to report it to CRA on your income tax because you would count as a small business. Even though you're an online business and even with YouTube, you count as a small business. Back in, I believe 2018, I might be wrong, but I believe it was 2018, CRA was making eBay and YouTube reports their Canadian users, all of the money that they paid out to them. So, CRA already knows how much you earned for eBay, YouTube and other online sites, so it's best that you report them whenever you file your taxes. Not doing so could land you in a lot of heat. One thing I found out is you can actually claim expenses for your business. For example, if you, for YouTube, purchased a camera, lights, tripod or any equipment including editing software or anything like that, that counts as expenses for your business. Anything that you also purchase to unbox or review for your channel also counts as expenses for your business, but you also have to keep in mind that there's a fine line between expenses for the business and expenses for your hobby. For example, if you purchased something to review on your channel and it was $50, but your channel got zero views, which means it made no money, that honestly can't be counted as a YouTube expense because it didn't actually occur for the business sign. It didn't make any money, so you didn't spend that $50 to make money, you just spent it to make a YouTube video and it didn't in turn make any money for the business side of things. Now, you can still claim those, but you also want to keep in mind that CRA may question some of your expenses if your expenses are higher than your income for multiple years. Here in Canada, I think the CRA is okay with three to four years of your business not making a profit and that is realistic because there is a lot of startup costs with any business, but you have to keep in mind that you can't claim every single thing when you fire taxes for YouTube. For example, for your YouTube, if from your start to your end you earned $1,000, but your expenses were closer to $5,000 if you purchased cameras, equipment, or things to unbox on your channel, CRA is eventually going to question that, whereas if your earnings were $1,000 but your expenses were about $1,200 to $1,500, that's more realistic and they would be more okay with that and likely not raise any red flags. The goal for any YouTuber is to make profit, so down the line you would want to make more profit than your expenses, but you have to keep in mind that with YouTube, they don't take taxes off of you, so expect, if you're on YouTube, expect some of your earnings to have to be paid back for taxes when tax season does come. So of course, I recommend claiming your YouTube earnings on your taxes so you don't get burned down the road. Now, of course, everybody's goal is to try to make more profit on YouTube and your goal with any business is to make more income than your expenses. That to me is common sense, but of course, you have to keep in mind your first few years, especially starting on a YouTube, you're going to be purchasing more things for not only quality of your videos, but also things for the business side of things and you can claim those as expenses, which is something I didn't realize prior to starting my taxes this year. Now for your taxes, when it comes to YouTube, it also depends on where you live. Certain areas have it where if you only earned a certain amount or less, you don't have to claim those taxes, whereas if you earn over that certain amount, you do have to claim those taxes. So you definitely want to look in your area and see what your regulations are whenever it comes to taxes of what you have to claim, but it's always better to claim your YouTube earnings, especially here in Canada, because YouTube, eBay and any other online sites do report those earnings to CRA. So CRA already knows that you earned that money the past year. If you guys have any other questions for how to do your taxes with YouTube earnings, let me know in the comments down below. I will help you guys out. I myself use simple tax, which is very easy.  For the industry code, you're going to put motion picture and video production. So now all you have to do is go in the income section and fill that out.  And then you have to go through your expenses. So easy ways to do this is to go through your channel for what you uploaded the past year, see what you purchased for videos to upload, and then also think about the equipment you used, any editing software that you purchased or anything like that. And you can claim those as expenses along with things like rent if you do rent an area, what percentage of your house is used for YouTube and stuff like that. You can claim that as well, which was very helpful. For me personally this year, I did have to owe, but that's because of COVID-19. Fortunately, once I put in my YouTube earnings, because my YouTube earnings, my expenses were about $300 more than my income, it actually saved me about $70 on my taxes, which was very, very helpful. So I'm definitely glad I did file my taxes and claim YouTube this year. I knew I had to anyways, but I'm glad I did that. So I highly recommend doing so, especially if your expenses are higher than your income, it might lower your taxes for the year. Now of course, down the line, if five years go by and your expenses are still way, way higher than your income, CRA may question that down the road. But you have to remember a business starting out is always going to not make profits for about three to four years and CRA expects that. So I hope you guys enjoyed this video and I hope you guys know a little bit more about filing your taxes and why it is important to claim everything for YouTube and why it is important to keep track of your expenses that you purchase for YouTube for the business side of things. So you can claim those as well because that could help you down the line. I'll see you guys in another video. If you guys will have any questions, let me know down below. I will try to help you out the best that I can, but you have to remember I am a Canadian YouTuber, so I can't help you with the American format, but it should basically be the same principles where your income and expenses keep track of that and you should be able to file it. Just the forms might be different than I use, which is simple tax. I'll see you guys in the next video. Please take care and peace.


So now that we've discussed the idea of doing a trinode restructuring with that abstract concept of giving making our x, y, and z turn into an a, b, c and then giving those things let's actually apply it to our double rotation of This 6, 7 insert 7 that we've done here So in that case as we just mentioned I do some kind of mapping I find out what my z is in that case Sorry, my a which happens to be the grand apparent. I find out what my Let me change colors there. I find out what my z was which was or my a was z I find out what my b was which was x and I find out what my c was which was y my parent So once again what I'm going to do with this information is I'm going to change it so that x Just to bring this up a little bit x Will become the new parent for z and y so like I said what we do is we take our structure. I Still have my 5 in the same spot. I still have my 2 in the same spot. However once again x is going to become the new parent so 7 shows up here then I Get my z and my y to become My children once again. We've already mapped it out as a and c are the children of b a is the left child right c is the right child so in our case 6 will become the left child of 7 and 8 will become the right child of 7 So once again, we've made our change. We've made our rotation. We're still in That insert 7 we still have not completed this so the question becomes What's my bf? What's my bot balance factor? Well for my 8 and 6 since their leaf nodes We know that those are going to be 0 to wasn't even touched so we don't even have to touch it 7 we see that it's balance factor it can go Down one node on the right it can go down one node on the left And it happens to have a balance factor of 0 meaning that Even though 5 you know 5 is technically also being looked at in this situation It can go well since you know why not Since it can go two nodes to the right and one node to the left it happens to have a balance factor of a 1 so while This tree is right heavy. It's not terribly impossible We have not broken the laws of physics just yet or the laws of our binary search tree of our AVL tree And everything is good to go


فشرف بل اشتغالي بالعلم ولا تبغي به ما عشت يا دادا دالا وياله من شراف عظيمي الثالثة التي تقوم بها هو because they're very so the author here broke the Hadith of the Prophet As-Salaamah which is من آذالي وليا anyone who harms my Awliya my allies فقد آذنتوا بالحرب and this person is in war with Allah صح؟ and the ulama of the Awliya here is both it's going to be mentioned soon إن شاء الله تعالى بأبي حنيفا شافعي that they are علماء علماء are people who know the Quran in the sunnah they're the ones who've memorized the Quran they know the book of Allah سبحانه وتعالى then the author broke the Hadith in صحيحين where the prophet says من صلاة الصبحة anyone who praises the congregation or subhan prayer فوفي ذمتي الله he's in war he's in the protection of Allah فلا يطلوبدكم الله بشيء من ذمتي that person is protected from evil إن شاء الله تعالى due to the fact that he is war because he's prayed in the congregation pray of Fajr yeah yeah the two great imams أو حنيفا and imam شافعي may Allah have mercy on them are reported to have said if the scholars are not friends of Allah then Allah has no friends so here the علماء are the only of Allah Allah's allies are the old علماء so if you open your tongue at the علماء and you speak against the scholars and you say things about them then you're in war with Allah who's gonna win in a war between you and Allah who Allah and you are gonna have a مبارسة الله is gonna destroy you سبحانه وتعالى نعم also إيمان أول قاسم even as a soccer may Allah have mercy on him said know my brother that the flesh of the scholars is poisonous to back bite in Islam is often referred to us to eat from the flesh of someone as it is referred to in the Quran and so to describe the flesh of scholars as being poisonous suggests that he who backbites them will do harm to himself through incurring incurring the wrath of Allah and Allah's custom of humiliating those who defame the scholars is unknown and that who so ever utters a word of disrespect against the scholars will be punished by Allah before his death with the death of his heart and Allah سبحانه وتعالى says so let those who go against his orders beware lest they be afflicted by a tribulation or be afflicted by a painful punishment the author here brought the statement of which he says in his كتاب في منصب الإيمان بالحسن الأشعري and this basically says a very powerful statement which is he says يقل الله و يقل المرضات may Allah give us to وفق and guide us to the straight path and give us the ability to follow that which pleases Allah and may Allah make us from those who are conscious of him and fear him the way he deserves to be feared and لعو العلمات يمس مومة that the flesh of the scholars is poisonous if you eat poison what's going to happen to you and meat that's poisonous what's going to happen to you you'll die if you eat the flesh a flesh that has poison on it a meat that has poison on it if you eat it you'll die so the flesh of the scholars is poisonous and backbiting we said is what eating the flesh of Allah and your brother so what you're doing is you're eating their flesh now and their flesh is poisonous isn't it what Allah said in the Quran that eating the flesh of the Muslim backbiting the Muslim is what is eating the flesh of your brother so you're eating this person's flesh and as the sheikh is saying is that their flesh is poisonous وعيدة الله and Allah's norms the way Allah deals with these people who open their tongues to the علماء is في هتك أستاري من تقصيه معه the way Allah destroys them and humiliates them is well known وأن من أطلق قليسانه في العلماء يبثنب anyone who opens his tongue unrestrictedly and then starts to speak about the honor of the scholars and their dignity and their reputation he makes takfir of them the scholars of dollars whatever he calls them that person should know who's opening his tongue with honor scholars to criticize them to slander them then what you need to know is that Allah is going to kill your heart before death comes to you your heart is going to die it's going to rot and a lot of these people who've opened their tongues to the علماء they spoke about the scholars have ended up apostating from Islam they left Islam because it became very light for them to speak about the the flesh of the scholars so the author of them brings امريه be cautious of those who are opposing Allah's command okay opposing Allah's command here means going against him by slandering the scholars what's going to happen to them and to see them fit now a child and a tribulation will afflict them or will you see them or a severe punishment will afflict them عبد الله أحمد بن حبل أحمد بن حبل انتصيبهم فتنة هي ميز the apostacy the apostacy is going to happen it's going to happen to them then the author says الباب الرابع في أداب معلم القرآن هذا الباب مع الباب بينه بعده هي مخصود الكتاب هو طويل منتشر و أنا أشير إلى مقاصده مختصرة في فصول ليسهل حفظه و الضبطه إن شاء الله تعالى فصل في خلاص المقرئ والقارئ أول ما يبغل المقرئ والقارئ أن يقصد بذلك وجه الله تعالى قال الله تعالى و ما أمروا إلا ليعبد الله مخلصين له الدين حنفاء و يقيم الصلاة و يؤتز زكاة و ذلك دين القيمة أي الملة المستقيمة و في الصحيحين عن رسول الله صلى الله عليه وسلم إنما الأعمال بالنيات و إنما لكل إمري إما لواه وهذا الحديث من أصول الإسلام و روينا عربنا عباس رضي الله تعالى بما قال إنما يحفظ الرجل على قدرنية و عن غيره إنما يُعطى الناس على قدرنيات و روينا عرل استاذئ بالقاسم القشيره رحمه الله تعالى قال الإخلاص إفراد و يعقف الطاعة بالقصد وهو أيريد بطاعته التقرب إلى الله و أيريد بطاعته التقرب إلى الله تعالى دون شيء آخر من تصنع لمخلوق أو اكتساب محمد أو اكتساب محمدة عند الناس أو محبة مدحم من الخلق أو معنى من المعانيس و يقال الإخلاص تصفية الفعل عن ملاحظة المخلوقين و عن حذيفة المرعش رحمه الله تعالى قال الإخلاص استواء و فعل العبد في الظاهر والباطن و عذ النون رحمه الله تعالى قال ثلاث من علامات الإخلاص استواء البدح والذم من العامة و نسيان العمل في العمل و اختضاء ثواب العمل في الآخرة و عن الفضيل رحمه الله تعالى قال ترك العمل لأجل الناس رياء والعمل لأجل الناس شرك والإخلاص أي عافيك الله تعالى منهما و عن السهل التستري رحمه الله تعالى قال نظر الكياس في تفسير فلم يجدوا غير هذا اي تكون حركته و سكونه في سره و على نيتيل لا يمازجه شيء لا نفس ولا هوا ولا دنيا و عن السر يرحمه الله تعالى قال لا تعمل للناس شيئا ولا تترك لهم شيئا ولا تعقل لهم شيئا ولا تكشف لهم شيئا و عن القشير و عن القشير قال أقل الصدق استواء السر والعنان و عن الحارث المحاسن رحمه الله تعالى قال الصادق هو الذي لا يمال لو خرج كل قدر الله في قلوب الخلق من أجل صلاح قلبه ولا يحب الطلاع الناس على متاقيل الزر بالحسن عمله ولا يكره الطلاع و لا يكره الطلاع الناس على سيئ من عمله فإنك راحته لذلك دليل على أنه يحب زيادة عندهم و ليس هذا من أخلاق الصديقي و عن غيره إذا طلبت الله تعالى بالصدق أعطاك مرآة تبصر فيها كل شيء أعطاك مرآة كل شيء من عجائب الدنيا والآخرة وأقاول السلف في هذا كثير وأقاول السلف من في هذا كثير تنشرنا إلى هذه الأحرف منها تنبيها على المطروب وقد ذكرت جملا ذلك مع شرحها في أول شرح المهدب و ضممت إليها من أداب المعلم والمتعلم والفقيه والمتفقه ما لا يستغني ما لا يستغني عن طالب علم والله أعلم نه لذلك المرآة here تخبرنا that the fourth chapter and the fifth chapter are the two longest chapters in the book they are the two longest chapters so if inshaAllah we succeed today to finish the fourth chapter then we're good inshaAllah if we don't we're in trouble the first thing in Cuba upon the teacher and student of the Quran is that they seek with the deeds the pleasure of the Lord Allah says and they were commanded not but they should worship they should worship Allah and worship none but Him alone abstaining from ascribing partners to Him and perform prayers and gives a care and that is the right religion meaning that it is the upright religion so the first thing the one who's reading the Quran you see the one who's reading on both of them the student and the teacher is the first thing that they need to come with is that they seek Allah's face they do this for Allah as Allah said in the ayah I have not commanded them except to worship Me alone with with sincerity so we were commanded every righteous deed that we do we do it with what with sincerity and we do it only for Allah in the two authentic books it is narrated that the Messenger of Allah when the scholars they say the two most authentic books they mean the what بخارية المسلم and this hadith is narrated from عمر من الخطاب رضي الله تعالى عنه these are both with intentions and every man shall be compensated according to his intentions so the actions that a person comes with is all based on what they intended and your reward is in accordance to your intention so every action that a person does even if it's good but they had no intention for it they don't get rewarded for it to get rewarded for that action you need to perfect your intention so it's coming and reading the Quran or coming to a lesson like this and sitting and not taking knowledge if you don't have an intention for it then you won't get rewarded so this hadith is one of the foundations of al-Islam one of the great principles of al-Islam now so if a person wants to memorize the Quran if a person wants to seek and gain knowledge a person will memorize in accordance to their intention and a memory of a person is connected to their intention and how dedicated and motivated you are if you are motivated and you are driven your memorization will be high you will be able to memorize the Quran and you are doing it with sincerity there is nothing they are going to stop at and if a person was doing it for somebody then it will stop if that person turns away from you you stop doing it if a person was doing something for the people and the people don't praise you anymore you stop doing it right but if you weren't doing it for the people you were doing it for Allah whether the people praise you for it whether the people acknowledge your efforts they learn too badly you don't really care because what is it you were doing it for الله سبحانه و تعالى and the one who is memorizing the Quran if he does it solely for Allah's sake his memory will be higher and this is a statement of him now best you need to memorize إنما يحفظ الرجل على قدر نيته a person will memorize in accordance to their intention in another way he said إنما يُعطى الناس على قدر نيته that the people are given knowledge in accordance to their intentions when Allah sees from your heart and he sees that you are sincere you are doing it for his sake that's when Allah is going to give you knowledge and what's the greatest knowledge to be given the Quran so if Allah sees from you sincerity that you are مخلص Allah will open doors for you Allah will give you secrets that no one else will know you will know underground tunnels in knowledge that no one has moved quick roads, shortcuts all of that will be open for you all because of what because your intention is good so you deserve that if your intention is not good you are reading one thing which is right in front of you you can't even memorize it all day you struggle to memorize it now in accordance with the sincerity of their intentions all of these statements and much more you can find it in the جامع لأخلاق الراوي وآداب السامع قطيم البغدادي جامع لأخلاق الراوي وآداب السامع and if Allah gives us time who should go through that book شخبك ربوزيت سامرائز so if we can go through the summary of شخبك ربوزيت that would be good it talks about the etiquettes of the one who is carrying the narrations and he's passing on the narration so this is this book what does it talk about the one who is carrying the قرآن right خطيم البغدادي isn't that what we need here we are talking about the etiquettes and the one who is carrying the قرآن and I think we should do خطيم البغدادي on the one who is narrating and the one who has been narrated to and the one who has been passed on to the student of the Quran right so I think that should be the second book if we were to do something to do the word أستاد is used here أستاد means professor teacher a verse that teaches the people أبل قاسم القشيري هو روتك الكتابة الرسالة and he is from the he is from the صوفية أبل قاسم القشيري is from the صوفيز and he is a رسالة that he authored is the book that أبي حمد الغزالي رحمه الله in his كتابة حيعلوه ديلي وقته that book حيعلوه ديلي باية أبي حمد الغزالي is basically works on أبي القاسم القشيري's كتابه his رسالة رسالة القشيرية that will mean hedge published it that will mean hedge published that will mean hedge the owners of that will mean hedge are شافعي صنطية نقشبندية in the published in house but they bring out nice شافعي books published them very well and they are the ones who published just about every مدهب شافعي book نهاية المطلب في دراية المدهب بمعاني الجويني أيها طرعي they published it they done the best publication for that this book that we are reading right now that is in front of us which is مدهب شافعي is the best publication out there اتبعي they work very hard they work very hard on the books and they bring it out محقق very well organized very well written if you stand over the original نصخ خطية and you compare you really find mistakes just so far while I was reading I came across one mistake that they did it's meant to be عبدالله من عمرب العاص they wrote يقلم and this could probably be a mistake which is خطى مطبعي the publishing mistake where you come across it كفاية الأخيار which is مثل أبي شجع they done it خياع علوم الدين by أبحمد الغزالي they also published it على كل حال رسالة القوشيرية is the rsala that ألمام أبحمد الغزالي he is speaking about and talking about and he is working on in his كتاب حياع علوم الدين so he are back in the days of صوفية were not the same by the way they were not all the same as sheikh al-Islam Tamey mentioned from the Sufis it was from the Sufis it was from the Sufis it was from the Sufis it was from the Sufis it was from the Sufis the Sufis they went through phrases they went through phrases they changed as time went by the ones before they were aesthetic they left this world and they were towards the Akhira they were Zuhad and they were more about they were more about living a simple life in this world just to be aesthetic just to be a person of this dunya they were ones who used to they used to honor the cultural evidence about junaid one of the statements that was one of the statements that was transmitted from him was that he said I sometimes hear a person say a benefit and I don't write it I would hold and I say to that person what witness do you have that goes in accordance to this benefit that you mentioned are you with me but as time went by the Sufis changed especially when the time of when Abu Hamid al-Ghazali came what he did was he emerged the Sufiya with Achaariya Achaariya and Sufiya emerged to gods one another back in the days Achaara and the Sufiya were two different things they were two entities after Abu Hamid al-Ghazali onwards you'd rarely find an Achaari except he's a Sufi he's one of the one of them or wherever it may be he is a but he's or he's a maturi are you with me so then they adopted things which were you know doing intercession through the righteous people they started to adopt these things these were not common amongst the early generation of the Sufiya they didn't have that stuff they never fell into this major shirk statements that you find the later Sufiya fall into and then after as time went on they started to pass on beliefs that this world that we're in today their awliya played a role in its building that they helped Allah with the spreading of the Samaa and the spreading of this earth and etc statements which were very very dangerous like Bursini what he said in his statement you know you know that Muhammad this world that we're in today is from your generosity the other one who gave it to us it's part of your generosity and also from your knowledge is what's written on the Lo'hu al-Bahfud what's written on the Lo'hu al-Bahfud is from the knowledge which you know are you with me and where the Sufiya took this from was the Shi'a they connected themselves too much with the Tashay'u are you with their brothers and so it entered on to them are you with me brothers so the name Sufiya they say that the Sufiya comes from Ahl al-Sufa the people that used to live in the process of misjid Abu Huraira and the likes of him who used to live in the misjid but the strongest opinion Ibn Taymiyyah says that no Sufiya came from that they used to wear Suf that's the kind of clothes that they used to wear Suf which is cotton back in those days cotton was looked down at it wasn't one of the best clothes so they used to wear unappealing clothing they weren't attractive there was Zahideen then they started to introduce dancing and music and now which they call now which so many people don't understand but call and their Shi'a the Shi'a came from the Sufiya they're the ones who brought it that this is a spiritual uplifted for them that when they sing and they dance it's something you won't understand or it's a spiritual uplifted so they sing they dance they started to adopt these concepts as well it started to creep into them so they would dance and now if you see them they go in circles they swell and whatnot this is ibadah for them and and vikrs that are really strange like instead of saying Allah they say Allah Allah they take the name of her and they go fast to saying all day and that's a zikr for them all of those were things that they started to adopt and things that they started to do so sheikh al-islam ibn taimiya took after them write it so that at this time there was a taif a group called the rafi'a group who used to claim that they could walk through fire they wouldn't burn them they used to claim these stuff and show the people that this is the kind of people they are so ibn taimiya took it to every level with them he debated with them rationality he destroyed them when nothing would work and they still were stubborn on their belief he said how about this we all go into the fire together let's get ready ibn taimiya will also go into the fire with you guys but with condition he knew that they used to wear they used to put on some things which when they went into the fire it wouldn't really burn them inflammatory stuff which they would put on so they won't burn them so he said i'll give you vinegar ibn taimiya said you have to show with vinegar that will get rid of everything we all go into the fire and we'll see who it burns so ibn taimiya exposed them with every different levels and every different angles when they refused to go into the fire he said how about this just put the خل on your finger and put it into the fire just a finger they refused to just a finger burn your finger i'll do it with you they got exposed for what they were upon so he started to adopt this belief which is that there's a level which you reach it's called certainty which once you reach that level you don't watch for Allah anymore صلاة is not wajib on you زكات is not wajib on you all the كاليف شرقية the jurisprudence rulings the things that were wajib at the محرمات are not haram for you so you see some of the sufiya leaders you see that they marry their own daughters they marry their own parents common no haram حرمة عليكم أمهاتكم none of that is haram for them anymore because they have reached a level called يقين they would drink khamar they would do things that were when they are asked why they won't pray صلاة they won't pay zakat they won't even go to the ka'bah and some of them even claim while they're sitting at that particular place they'll say to you i went to the ka'bah and i came back i just visited the ka'bah i saw a man in the ka'bah he was doing tawaf around the ka'bah if you go back to your don't go far go to Somalia you see people like that who believe those things i saw a guy one time a large amount of women were with him this guy got an entourage of women like he's got all the 30 women all running after him Somalia all of them are running after him and they all call him Abu dad he's got boys they're entourage again another 30 40 entourage follow him the women he marries the way he deals with everything no one's ever seen him pray صلاة he does not pray صلاة they all call him dad they respect him if you ever say anything about him you'll be killed you'll be murdered on the spot everything that's happened he's in that village he's got everything on he's got everything on control this is just one thousands of them are like that around the country go travel to Pakistan and India and countries like that you guys are on youtube don't worry your stuff is on youtube the guy gets covered with some things so youtube they put a big cloth over him and he's doing this you guys always take a step further he starts shaking he starts shaking the cloth they say he's going to the caba he's doing the offer on the caba and he's just sitting there he reminds me of what's it called teleportation what's it called what's it called transmission wasn't the one i'm sure anyways that's what it is the man goes to the caba comes back i wouldn't even be shocked if it's true that he does do that because شاياطين work with these people they work with شاياطين i wouldn't be shocked if it's actually something that he's really finding out through working with the شاياطين who's gone there who's not the point is this is the things that they adopted so they don't know about they made a clear on them they made what they made تقفير on them so books have been written they became very common around the muslim world in africa places in africa like in sudan they became very common they became very are you in Nigeria gala subcontinent Asia america well western countries they're very weak their influence is very weak they got strength they do things for the people they take leadership positions where through that they can influence the people now professor sincerity is the single out in terms of directing all acts of obedience to him when you're obeying when you're intending you all do it for who's sake that is one should seek to become closer to Allah through obedience to him and not see compensation from any of his creation or their praise or love or any other objective he also said when you do something you don't wait for people to praise you some people they want to get recognition for every single thing which they do they want praise that's what they want if they get praise they feel like what they did was good they get criticized what they think what they did was wrong that's not the case it's not the case you don't care about what people have to say and what people think and how they perceive things what is important for you as a Muslim is what have you done it for Allah's sake the reason is because you're never going to reach if you please one person you're under another if you're under another you please another so your goal should not be pleasing the people a lot of people it has tired them they've become tired of trying to please the people but they got nowhere your goal should not be to please the people and to even let that be in your mind the people rather they like sometimes was bad for them they like what's bad for them what's not even good for them so how can I try to please you if I please you it would mean that I would have to entertain for you what I know that's bad for you right who likes to wake up right now pray Fajr in the Masjid's first line قلي little dude are you there who likes to pray Piamoled who likes to fast every monday on Thursday this is acts of obedience who don't like to do so you as an individual don't dismiss what's good for the people because you know they don't like it it is correct to say that sincerity is to purify one's actions from seeking the observation of others you purify from your actions you cleanse from your actions عن ملاحبة المخلوقين the observation of the creation the poet when he say الله يصف القلب من يرادة سواه فحضر يا فطيب that you intend everything for Allah's sake and you cleanse from it you get rid of you get rid of it being for anyone other than Allah's sake سبحانه وتعالى و لذلك إخلاص is one of the hardest thing a person works with والله is a very hard act because within one lecture within one talk of yours your intentions is changing consistently سلافو هادن أمة what did they say و كنا نجدد we will renew our intentions in one sit so many times so many times so it's not like when you start you're praying you started for the sake of Allah you're praying for the sake of Allah and from the corner of your eye you see somebody who you respect bang the intention changes are you with me you weren't doing it for anybody other than Allah when you stood up but now look what happened to you so you see your arms start opening up you start holding your hand properly you start praying properly all of this is now that your intention is swaying away from you you need to fight and get it back so that's why now أليفا ألمر عاشي ألمر عاشي may Allah have mercy on him once said sincerity is the balance between the outward actions and words and aspects sincerity of one's deeds you know what is sincerity sincerity is when your personal life your internal affairs behind closed doors and outside in public you're the same that's sincerity that's what he said أليفا ألمر عاشي he said that the person's actions are the same في الضاهر والباطن privately and in public