 All right. As you're arriving, why don't you pop into the chat where you are connected from? There's no way you are right now. Get a sense of where everyone's spread over the world. Louisiana, let me bring this over here so I can actually see. The lines are fat. I swim from Louisiana, Mario from Zaragoza, Hortano from Singapore. We've got India, India, Illinois, India, India, India, Poland, New Jersey, Rhode Island. Wow. Look at all of these places. Kenya. Wow. This is a pretty international audience. Thank you everybody for joining. All right. We'll give it just a second and then we'll get crack in and start talking about building amazing sessions. All right. Actually, while we're waiting as well, why don't you pop into the chat, which projects you've been working on? Let's do that. I'm going to bring it over here so I can read again, which projects that we've been working on as part of your mentoring. Linux kernel, PCI subsystems, CNCF, COBOL programming course, plug-in system for tremor. Wow. Look at all this stuff. This is amazing. Falco adapter for the CNCF Kubernetes blockchain integration, Hyperledger, Hyperledger, tremor, Solang solidarity compiler, RISC-5, litmus chaos. This is great. All right, folks. Why don't we get started? Hello, everyone. My name is Jono Bacon. I've been in the open source community since 1998, which is about 200 years ago. I've spent many, many years working with the Linux Foundation. The team reached out to me the other day and said, hey, we've been running this incredible group of mentors and they're going to be presenting what they've been doing and we'd love to do some speaker training. And they said, would I be interested in helping out? So happy to help. My background is that I used to lead community for Canonical for the Ubuntu project. I led community at GitHub and XPrize and I'm a consultant. I work with lots of different companies, including the Linux Foundation, where I help people to build communities. My area of specialism is around open source and developer communities. Okay. I've been speaking at conferences for probably about 20 years now. I've been keynoted over 100 conferences. So I've spent a lot of time screwing up presentations. I've spent a lot of time doing things wrong so I can learn how to present effectively. And what I'm going to share with you in this session is going to be a recommended structure for how you can put together one of these five to 10 minutes summaries of what you've been doing in a way that's really crisp and clear and easy to read. I'm going to go through this structure. It's going to be very, very practical. And then I'm going to also give you an example. I'm going to share an example with you so you can see it. And then we're also going to talk a little bit about slide design and how to deliver it effectively. All right. That sounds good. Thumbs up, thumbs down. Let me open up the chat. I want to try and make this as interactive and as interesting as possible. Let me open this up so I can see what's going on. And then what we'll do is we'll have some Q&A at the end so we can do that as well. Perfect. All right. So let's get started. So what I'm going to do is I'm going to switch over to the whiteboard and we're going to first of all break the structure down of what a good session looks like. You see, when you're presenting any kind of information, whether you are presenting a 35, 40 minute presentation, an hour long presentation, whether you're doing a five or 10 minute summary, this is all about presenting information to your audience in a way that's quick and easy. There are a lot of people who go out there and speak at conferences or elsewhere, and they tend to ramble. And part of the reason why they ramble is because they don't have any structure. They don't have any organization. So what we want to do is we want to figure out what is all the information we want to get down and structure it and break our session up. So five to 10 minutes is not a lot of time, but it's incredible how much you can squeeze into that amount of time. So let me first of all break down the four pieces that we're going to cover in one of these sessions and then I'll talk about each of them. All right. Okay, so let me go up here. So the first section we're going to focus on is going to be introductions. Okay. Now generally you want this to be about a minute long. Right. Most people when they see you speak won't know who you are, and they won't know what project you've been working on. So the goal here is to briefly introduce yourself and talk a little bit about why you apply to the program and then to introduce the project that you worked on and that you worked on essentially what it does. Okay, so, like I say what I've done here is I present I've created kind of a sample deck if you will. Now this is not particularly, this is not designed you'll probably want to add your own flair to it. Okay, but the first thing we do before we even get into the introductions is we want to give one out of cover slide and just you want to pick a title for your session that's going to be interesting. So the example that I'm providing here is imagine somebody works in the react project so react is a JavaScript framework for building user interfaces, right so imagine somebody's going to work on that for 30 days. So I picked this title from zero to react in 30 days to think of a title that's going to really grab your audience. Now when you're thinking about this title, make sure that it evokes some kind of curiosity you want somebody to read this and think, Oh, what does that right so from zero to react in 30 days suggests that someone went from knowing nothing about react to contribute to react in 30 days, and this evokes some curiosity about what that journey might look like. Okay, then you also want to put down your name and your email address. Now, one of the things you'll notice about my slides is that they're very, very simple. One of the problems with a lot of people who present is that they tend to over complicate their slides they put too much information on the slide and you want to completely avoid that. Most of my slides when I presented conferences for example, have no more than maybe 10 words or just one picture. If you're presenting, you're going to be talking through the information, you don't, you don't just want to read things up a slide, because people get bored. Also, people can't listen and read at the same time it's overly complicated. Okay. So, the first thing we're going to do is going to provide a short introduction. Right. Now, this is obviously not a picture of me. This is David Hasselhoff. But put a picture of yourself on there. And I'd like to recommend you provide a picture of you and a kind of a fun setting, right, it might be a picture of you doing your hobby or hanging out with a friend. Or if you met somebody in the social community, let's say you met someone like Linus Torvalds or Jim Zemin or whoever it might be. Let's put a picture of you on there. And very, very briefly, no more than 10 or 15 seconds, talk about you and your background. Talk a little bit about about, you know, you might want to talk about what school you went to, or what got you into open source, and talk about why you decided to apply and joining the mentoring project. Okay. Now this has to be really short. People don't want a minute or two minutes of you rambling on about yourself. No offense, but no one's interested. They just want to get the sense of who you are. Okay, so, you know, we've allocated, you know, we've allocated here one minute to this session to this to the section. So, no more than kind of 10 or 15 seconds to just introduce yourself. And then what you do is you provide a quick overview of the project and what you set out to achieve in the project. So here you can see on the left we've got about the project react, a library for building powerful user JavaScript, right so very, very simple one line summary because the people watching this mentoring session may not be familiar with the project that you're working. Okay. And then you want to set out with your goals. Now these are the things that you at the beginning of your mentoring program, what you set out to achieve in that meant in that piece of the mentoring. Okay, so you can see here. For example, I've got three, three goals to understand the internals of the project to optimize the error handing elements of the code and to submit over five pull requests to get accepted. Now, when you create this session this five or 10 minute mentoring summary is going to be a brilliant thing you can show to potential employers if you're early in your career. You can open source you will work for a certain company. This five or 10 minute session is not only going to be a great summary of how you went what you did in the mentoring program. But it's going to be a great way of showing how you present information. So again you can see here in the slide design we've got a title at the top. And in my slides, we've got two columns of information about the project and then my goals, not a lot of text on the screen, just very simple overview. Okay, so just to recap, pick an interesting curiosity curiosity of a vote in title for your fear session. Very brief introduction of who you are, and then a quick overview of the project and your goals. Okay, so that's the first step that we step into. Okay, that should take no more than about a minute. Okay, and this aligns everybody with what you're about to present for the rest of the session. All right, let's move back to the, to the board. And now let's put on our second section. Okay. And this is where we talk about skills. Okay. Now, this is essentially where you're going to introduce what you were tasked with in the project and you're going to share three key skills that that you gain based upon really measurable outcomes. Okay, so I'm going to put over here. Let's let me use a different pen, hang on. A blue pen. Okay. So we're going to put here. Three skills. Okay. So that's what you want to focus on. Okay. Now, this is where we kind of get to the crux of what you learned in the, in the mentoring program and I'm going to switch back over to my slides here. And here is an example of what I'm talking about. Okay, I've broken it down into three different slides. Okay, now this is one of the techniques I like to approach with any kind of presenting is that you break your information down and you reveal it to your audience. So if you put all of these things on one slide, it's going to be overwhelming, it's going to be too difficult to understand. So you can see here, what I did is for the first one, first of all, we've got the title at the top, again, consistent. And then we've got how the internal react code works. So that's the skill that you developed in this example, we can see that we've got an image on the right. And then we've got a summary of what was kind of covered by that skill. So how the internal react code works, three bullet points, code structure and organization, coding standards and requirements, unit tests and coverage. And you'd walk through that, you know, you'd say something like, you know, so one of the first things I learned while I was going through the mentoring was how the internal react code works. You know, I couldn't go and create pull request for the react project if I didn't understand how the code works. So in doing this, what I did is I understood the code structure in the organization, how everything fit together, how the classes and the methods were working. I understood what the react code work, what the react project requires when it comes to coding standards and requirements and then also testing the fundamental part of this way, understood how the unit tests and coverage work. Okay. And then like I say you put it, you put a, you put an image on the, on the right now, but I didn't cut, which I should have cut it here. I'll go back to the board is that's what this down is this is going to be three minutes long. Okay. So you want to cover about a minute for each of these different, each of these different slides. Okay. Now, if it's not a hunt, if it's not a minute, it's fine if it's less don't go over a minute we need to keep everything within 10 minutes within hours within our section. But what you want to do is just summarize what you did don't go into exhaustive levels of detail and ideally your image here will be relevant to what you're talking about if it's not 100% relevant. That's fine like you can see here for the one I'm going to get to about contributed production code. I just took a picture of get that's fine. If you're wondering where you can go and get images from Google images search is a great place it's very stock photo libraries that are out there. If you use an image you should probably put some attribution at the bottom, but just go and and visualize what you would do. So as you can see again the slide design is really really simple it's really clear. We talk about what we did how the internal react code works and then we talk about the elements within that. So, you know, that's the first skill, and we want to present three skills so the second skill that I've got here. I'm creating error codes understood and tested core errors with a script created six new error codes tested and contributed created docs that were reviewed by the team tested errors and production. Now what you want to do when creating these bullet points is you ideally want to share as much measurable as many measurable achievements as possible. So I created six new error codes says very specifically this is what I did within this error codes project. Okay, the problem with a lot of people who present summaries or something like this mentoring summary is they tend to share general things like spent time with the project you know, join Slack, you know they share these kind of just general things and that doesn't get specific to the outcomes and what your audience wants to hear here is what were the outcomes of your mentoring experience what would what was the result of it. Okay, so try to try to list in these bullet points where you can measurable things. Now, everything is going to be measurable right understood and tested for errors with a script is measurable. Okay. If we go back to this one. You know understanding coding standards and requirements isn't measurable right that was just something you have to do. So generally try to focus on measurable things but if you can that's fine. What you definitely want to do is have measurable things that you achieved in each of these different examples. Again, you can see the image here is just a general kind of photo or a general image of an error code. I try to find something specific to react and I couldn't. Again, this image here. This third one is just to get up octo cap so that the skill here contributed production code to react core. You can see here some specifics contribute 12 pull requests that seven more than my goal so if I go back to my goal here. Remember here to submit over five pull requests that get accepted. Okay, so here we contributed 12 pull requests learned code submission review pro pro. Let's fix this. See, this is the other thing you should do proof read your slides, which I didn't do responded to feedback fix my branches and improve all contributions merchant of the core. Now this one's really important all contributions merchant for the core because that's basically saying anything any code that was submitted was reviewed by the project and it passed all the quality requirements and went in. So at this point in the in in our structure, you can see what we've done in literally four minutes we've said we've about curiosity. Okay. Introduced ourselves introduced the project and what we set out to do, and then shared the three major skills that we developed in the mentoring program someone was to log off at this point. And now they would have most of the information that they set out to, to, to, to understand from you. Okay, so this. This is great with delivered real value in four minutes. Okay. Now, mentoring isn't just about what you get out. It's not just about accomplishing a certain set of skills, but mentoring really is about the experience you know I know my friends at the Linux Foundation people like sure and the rest of the team have really a lot of time, focusing and perfecting how mentoring works and it really is a world, world class mentoring program I, when I was starting out my career, never had the benefit of any structured mentoring, you know I was kind of figuring out myself, but I met people in my career who became mentors to me. And while those people taught me amazing skills and helped me with my career. And while I got something very practical out of it. The real value to me was the experience of being mentored it was about building that relationship with your mentor, and it was about the surprising things that you learn from going through that mentoring experience and this is where we get into our third section. Okay, now as I'm walking through this if you've got any questions be sure to get them into the chat we're going to be covering them at the end I want to make sure that we cover absolutely everything you that's on your mind as we go through this. So, the third section here is the experience. Now this again is going to be three minutes long. Okay. So this is taken as up to seven minutes in our session. Now, what we want to do here is we want to cover only use the blue pen for this again. Three surprises. Okay. So what I love in any kind of presentation session is they love when a speaker is vulnerable. When they say, I don't have all the answers and I didn't have all the answers. And these were things that were surprising and exciting to me. And going through a mentoring program. And you're going to experience things that are going to be surprising to you right there's going to be I'm sure every one of you and feel free to put this into the chat. Like I'm sure every one of you experienced things that you weren't expecting. So what we want to do in this third section is we want to talk a little bit about how we worked with our mentor. And then what we want to do is to share the surprise because that's going to keep the viewer of your session interested as you're continuing through this because if you think about it as we go back to this. We perform the introductions, we walk through our free skills at this point they could conceivably log off or stop paying attention. But now what we're going to do is want to say, I want now want to talk about how I learned and some really surprising elements that kind of came out. So if I go back to the deck. So you got to your third skill at this point in your session you say. So these were made, you know, you were two or three children you say. Now, as you can tell I took a lot away from this and I really appreciate the Linux foundation for providing me with this with these benefits right, but mentoring is not just about these skills mentoring is about the experience and I had a really wonderful experience I want to talk a little bit about that. I want to share some things that really surprised me about my mentoring experience. When you say that that is going to peak somebody's curiosity and to keep them watching. And when you're presenting, you know, part of the reason why I'm doing the speaker training is not just for the mentoring but it's when you go out to conferences and present or when you do keynotes in the future or whatever. You're always having those little moments where you will vote somebody's curiosity will keep somebody will keep the attention of your audience captured and present. Okay. So let's, let's, let's first of all talk about about your mentor. So again what I've done is I've broken this into into two different sections. You can see my slides here are very consistent so the top my mentoring experience. On the left you talk about your mentor. This is obviously not a mentor this is Betty white who sadly passed away recently so you know, Betty we love you. So I put here Betty white has been a core contributor react for many years she wrote most of the internals which is hilarious. So your mentor, just a single paragraph that summarizes their role in the project and a picture of them. Make sure you ask them for permission before you put a picture in there. Some people don't want their images in presentation so you want to respect their privacy, and then you summarize here with bullet points. So basically what the mentoring look like so discussed and agreed on my goals, weekly mentoring calls better review my pull request before I submitted them guidance with interpersonal elements of the open source community and overall guidance on career goals. So you can see here in the how we work together section. We're talking about not just the specifics in terms of the project but we're also talking about elements around it like career direction and interpersonal like the community element. It's about code, right it's about how you work with other people and how you build code or how you participate in the project. So what this slide does is it presents your mentor, and it presents the result of the mentoring experience now this slide is a Q, the you want to go back to to the board. Okay. And what you want to do is here, you want to provide thanks. Okay, this is really important. People really appreciate appreciative people. Right. And, you know, mentoring takes a lot of work on behalf of the mentors you want to make sure that when you're on the slide that you thank your mentor. Okay, just talk about how there's such an awesome person say I really, you know, I had a great experience I really appreciate the time. I really enjoyed it a lot. I was able to ask and get great answers to my questions. It was just a really great experience. Okay, so this is the queue. All right. Now what we do is we move on to the three surprises. Now if you remember earlier on I talked about revealing information. So we've got three surprises. Right. And we've got that in the headline of the slide. So you can see that there's no content in this slide because what we're going to do is we're going to present each of these different surprises one by one. Okay. And I present this very in a very easy way now you could go back to this kind of structure if you want with an image, or you could just have text. I'm using text here just to mix it up you see how my slide design is kind of varying a little bit. Okay. So first surprise, the technical guidance was very helpful. Right. So at this point in the session I would say something like, you know, and I was expecting the mentor to be helpful with some elements of how I participate in the project but just the depth, and just how broad Betty's support was really I didn't realize how deep her experience was, and they should be helping with so many different elements of how I was contributing to the project. Okay, so you talk about this a little bit now, given the fact that this whole section. Okay, this whole section is three minutes long. And we've got, you know, we've got this slide which is introducing your mentor, you want each of these different surprises to probably last about 40 seconds. Okay, so we've got enough time to cover everything to talk about each of the different surprises of the examples here that I've got technical guidance was very helpful. I needed more guidance on navigating the community. So you could say, you know, Betty was, you know, I've never worked with an outsource community had a lot of anxiety around that I didn't really know what to do. I was worried I was going to put my foot in my mouth I was worried that was going to frustrate people was going to ruin my mentoring experience because of this. And so I provided amazing guidance for how to deal with this and how to react to some of the feedback that I was getting. Again, you want to be vulnerable you want to share where you didn't know something where you lack the experience because here's a really critical thing. If you're earlier on in your career or you've not presented very much to an audience. A lot of people and especially people in underrepresented groups will experience will have elements of kind of imposter syndrome and imposter syndrome is where you feel like you're, you're in a kind of a community or a business or whatever. And you're not. Everybody seems to think you're good, but you're secretly not very good and you haven't been found out yet. This is a very, very common psychological trait that impacts a lot of different people. Like I say it's common in underrepresented groups I've experienced a whole bunch of my life. And the problem with imposter syndrome is it can make people be reluctant in sharing where they aren't great or where they did lack of experience. Okay, but what I've learned in my in my career is that when you share that vulnerability when you say, you know I didn't realize that I lack these skills or I was scared about something I was nervous about something a lot of anxiety about something, or I went and did something I completely screwed it up. And when you share that kind of vulnerability, people respect that right because they can identify with it because we're all vulnerable. We're all anxious in our own ways, especially right now with COVID going around. Okay, so don't worry about, you know, being vulnerable and then somehow that reflects poorly on you or it doesn't make you look very good. That's not going to happen. Okay, when you share your vulnerability and you share how somebody helped you or how you crossed it or you battle that vulnerability. It's a really powerful story. The great stories in the world are where somebody is weak and then they become stronger. Right. That's that's that I mean that's every great movie has got that behind it. Okay, so when you're going through and sharing these surprises, share your vulnerability, share how you didn't know things share how you worried or your anxious about things and how you're meant to play an amazing role in doing so. So the third surprise I got here was you know really helpful career guys. Okay. You know, Betty was really helpful and helped me to figure out like what I wanted to do I wasn't sure whether want to be a front end engineer or back end engineer what I want to work in DevOps or whether wanted to be a developer evangelist, but I had some really amazing conversations with Betty and it's just surprising I wasn't expecting to get career guidance out of this. Okay. So I'm just going to go back and recap real quick. What we've what we've done through and then we're going to get into our fourth section and then we'll talk a little bit about delivery and slide design and then we'll do some Q&A. Okay. So the first thing minute first minute is introductions, let me go back to the beginning of my slides. So this is where we, we have an exciting title for your session. You introduce yourself, and then an overview of the project and your goals that you set out to achieve in that particular project. Okay. Second section here. This is three minutes long is where you covered the skills. All right. So this is where you covered the three different skills that you that you learned as you went through the mentoring experience. Again, break them down simple slides and overview the skill, some bullets that present what you learned within that skill, and then an image that visualizes the slide. Okay. The third section here is about the experience that you went through as you were mentored. Okay, again, three minutes long. Make sure that you apply plenty of thanks here. Okay. So this is where we talk about our mentor, and then how you work for the mentor to summarize the experience, and then you walk through your three different surprises. Okay. All right. All good. Yeah, pop into the chat. If we're good, let me, I haven't been looking at the chat because I've been looking at the rest of this but let me just load up the chat and make sure I can see. Hang on. Let me just take a quick look. Okay, sounds good to me. Thank you, Mario. All good. Great. All right, so let me just touch this in this question from a new show. I want to understand how do I balance personal versus technical information I present in my presentation, especially in the second section skills. All right, so for me, a new skirt, the, the balance of personal and technical. They're all part of you, they all make you who you are right you are a technical person and you have the elements of your personality. I don't think you need to have a clear breakdown between either of them. The thing about this, about this, this mentoring summary, is that people want to hear the story, they want to hear a summary of what you took away from it, and your experience of working with your mentor. So, I don't think you need to present too much technical information in the sense of, I don't need to talk about, you know, provides metrics of, I wrote this many lines of code I worked on these particular modules within the project I anything like that. So, what are the overall outcomes, how, you know, how many pull requests were submitted or, you know, whatever you did within your project, talk about the things that you achieved, but really focus on the experience and talk about what you took away from it is what I would recommend. Okay. Great stuff. All right, I'm going to get rid of the chat and then what we're going to do, move on to our fourth section. All right, thank you everybody for your attention. Our fourth section here. And our final section is on aspirations. Okay. So this is going to be two minutes long. See, as you can see we got one minute, four minutes, seven minutes, and then nine minutes. Okay. This is going to be a camera right five, six, seven, eight, nine. Yeah. Wow, I can do maths everyone. Check it out. So as we've been through all of this right you've introduced yourself and the project you've entered you've shared the skills you've talked about the experience. You'd imagine at that point you've basically taken away everything you needed to take away right you've shared everything you needed to share. So there's one really important piece that's missing. And that is what is your dream for the future. Okay, so this is where you talk about your big dreams. You know. So when people go into any kind of mentoring program. They're just doing it to be mental. They're doing it because they've got a bigger vision of the future. And you might not necessarily know exactly what you want to do in the future. Most people don't I had absolutely zero idea what I want to do when I started out my career. They just kind of happened, you know, as I bumbled my way through my life. So what you want to do in this final section is to share. What you're dreaming about right now, right where you want to get to. And the reason why this is important is because there may be people who watch your summary of this. Right. And I would recommend you share. I don't know if this is I'm assuming this is okay. So I might get into trouble with the next foundation that this is not okay but I'm assuming this is okay. But when you present this, and you've got a video recording of your presentation. You want to share this on LinkedIn, you want to share this on your social media want to share this with the world. And it's these aspirations here where if somebody watched your session here and they were impressed with what you did, and how you presented. And they can somehow help you with your big dreams. This is where opportunity gets connected it. All right. So let me go to my slides. And this literally can be just one slide. Okay. So here, my dreams for the future. So just summarize what you want to do here. So my example here is I want to work for stuff. I want to work for a company that is building open source that is building interest in technology. I want to learn more about client side frameworks. It was fun working on react, but do I want to work in other frameworks. I want to get more involved in the react project another project. And I want to speak at the open source of it. Right. So we can see here, I want to go and work at a particular place. Start up. You might even want to have specific companies you want to list. I wouldn't recommend listing specific companies because let's say you said, I want to go and work at Red Hat. But then canonical or Google are interested in you. You don't want to eliminate Red Hat because they may not have a job that's available for you. But these other companies that we'd love to work at also might have positions for you. You can see here that we've got more about learning about the technology, client side frameworks. We've got a open source component to this get more involved in react and other projects and then there's a speaking element speaking at the open source summit. So this is, I think the most fun part, right. And what I would recommend you do is this, right. Go to go grab a beverage of your choice could be coffee, could be tea, could be water, it could be gin, beer, wine, whatever. Go and grab a beverage of your choice and grab a piece of paper or two pieces of paper and a pencil and just sit down and just think about what you want to do in the future and just write everything down no one's going to see these pieces of paper. Think about all the companies you'd like to work at think about the projects that you'd like to work on think about, you know, would you like to speak at conferences would you like to keynote at conferences. Would you like to be on advisory boards, would you like to invest in companies, would you like to be working in venture capital, who are the people in open source that you'd like to meet would you like to meet would you like to meet Greg Crow Harmon, Jim Zemlin, whoever it might be, right. The one right all of these things that on pieces of paper. And then from all of these things that you've written down, pick three or four aspirations that summarize everything that you're interested in. You know, and this could be, I want to work for these kinds of companies or I'd like to speak or I'd like to start a podcast I'd like to start a YouTube channel. Think about all these different elements and write them down and then summarize them, and then put them on this slide. Okay. And now what we've got, if you, if you look at this we've got 12 slides, and about 10 minutes to present. So this is one of the reasons why I've broken it down into these time sections. But what we've done is we've got a title that about curiosity, we introduced ourselves, we introduced the project and what we set out to achieve we talked about the three different skills that we learned in our mentoring. We talked about who our mentor was and how we work together. We share the three surprises that we took from our experience, and then we share our vision of the future. Okay. And that's it. That's what I would recommend. I'm more than happy to share this, this, this Google Doc with everybody, but one thing I would recommend is don't just, don't just take my Google Doc and just change the text okay make it your own make it give you add your own personality into it. So I want to talk before we get into questions and we'll get questions in just a second I want to talk a little bit about about slide design and delivery. Okay. Now, one of the things that you really want to focus on is to focus on simplicity and clarity in your slides. There are far too many people out there who cram as much as they can into slices diagrams and overlapping circles. And some people see it as a badge of honor that you're somehow more experienced if you've got more stuff on your slides and that is complete and utter nonsense. Okay. The people who suck at presenting put too much information on their slides because we can't read it you can't listen to someone and read all of that stuff at one time. You know, like if I show you my other screen that I'm looking at. Okay, so this is my screen with my with my slides on. Okay, but this is my note screen. Look at all that information so people will put that kind of stuff on on on their presentation and that's it's silly. Okay, so you can't read all of that stuff. Okay, so focus on simplicity and clarity if you look at the slides that I've been putting here there's not a lot on here. Right. Okay. Now, the other thing that you want to you want to focus on is to avoid lots of text but for the text that you do have to use really simple and easy to read fonts if I go back to my slide so you can see that the heading up here is this big bold kind of fun this is this is baby's I think baby's no you can see that my main font here. This is Gil sans something that I like to use, but this is a very readable font I'm not using calligraphy or anything like that because people can't read it. Okay, when people are looking at your slides, they've got to be able to look at it and be able to soak up that information really really quickly. Okay. Now you definitely want to include like visual cues. So you can see how I've used images here. If you use videos, and you may want to put videos in your slides to kind of demo something. So let's say you're talking about something. Let's say you're talking about the things that you learned right we go back to our skills. And one thing you could do, if we have how the internal react code works you could have a little video that's, you know, 10 seconds long that shows that, but I generally wouldn't recommend that because then people are watching the video and they're trying to pay attention to the video while listening to you speak at the same time. And again people can't do both of these things they can't. Read or watch and listen at the same time. Alright, definitely make sure that you reveal information in phases, like we did with this. Okay. And what I do. This is probably the wrong way of doing it. But what I do is I just go and write everything down. Right. And then I just put a white square over it. And then you can see that the white square just covers the bits that I haven't got to yet. Okay. Simple way of doing it. You want to generally avoid all animation like all presentation software has the ability to animate things and to have slide transitions. And most of it sucks. It just doesn't look very good and it's distracting don't have things sliding, you know, people often have been sliding in and coming down and stuff like that. It looks cheap it looks like you're using that to try and garner someone's attention, you know, keeping things simple is better if you're going to have any kind of animation just have faith, where something will fade in. I like to use faith to fade in, you know, like what we're talking about these things. So I like to have fades for each of these. So you'd show this and then each of these, each of these would fade it. Okay. And then generally avoid sound sound can add value to a presenter I've seen people put like background music and presentations. One of the reasons why I would avoid sound one is that it's a distraction. It doesn't have anything generally. But the second reason is that then you've got to figure out how to make sure that sound is working with zoom or however you're presenting online, and sound is just complicated. You know, sometimes, sometimes it just doesn't work. Okay. Now, let me show you another. This is like a, this is like a general presentation that I do. Let me show you a couple of examples here. So this is actually a full presentation. This is not like a summary, you know, I introduced myself. I like to put this in there just a little bit of fun to break the ice about how I pronounce my name. You can see here this is where I tell the story of how I got involved in open source and these are just full images, right. Here you can see where I talk about the value inside a community, the value of the value that you can get from building great communities. There's lots of services of Seth goading. So again, I'm not going to go through this entire presentation but you can see this is a reveal, but you can see how I just keep things really simple. They're very visual. Not a lot on each of these different slides you can see again how this reveals I talked to each of these different things as they get presented. Okay. You can use lots of bright flashy colors, you know, black text on the white background it's clear and it's simple and easy to read. Okay. Whoops. And then as you're speaking, well actually before I go on. The final thing is on the on the on the speaker on the slide design side of things you may be thinking which kind of software do I use so these Google slides PowerPoint keynote Libre office. Well, I like to use Google slides while it's simpler and it doesn't offer as many features as something like PowerPoint. The fact that you can use it for me it's completely free you can use it from any computer. And it means that you don't have to move files around is one of the reasons why I love it. Okay, and you have all of this big library of presentation slide presentations that are just online. And frankly, the features that it provides are more than enough to live a great presentation so everything I do is in Google slides. And now in terms of delivery, a couple of very quick things I want to come and then we'll get on to questions. The first thing is to speak clearly and don't rush. Okay. If you're speaking a million miles an hour. It's going to be difficult for people to understand you. It's especially difficult if you speak quickly and you've got an accent, right. So, you know, I saw from the beginning of the session where people from all over the world. So you definitely want to speak clearly because you're probably going to have an international audience as well this is something that I to this day struggle with I tend to speak very quickly, and my apologies if I've spoken to quickly today. Okay, now what you also want to do, especially if you're new to presenting is to create speaker notes. Okay, so if I go to my screen here, you can see here at the bottom in Google slides, I can add speaker notes. Okay, just down here. Now, what this will do is this will be some notes that only you can see when you're presenting. And that can be useful for indicating the kind of things that you want to, that you want to talk about in each particular slide. Now the thing about speaker notes is don't write out a script. Don't read a script. It sucks when people read scripts. Okay, nobody. I really enjoyed this particular part of my mentoring experience because I talked to my mentor on Mondays Wednesdays. It's obvious when people are reading from the script. So just put speaker notes in there when I've done speaking notes I literally have just bullet points. What I personally prefer is that you don't actually create speaker notes and what you do is that you have just the right information on the slides like we've got here. Right, you can see here we've just got the right pieces and this becomes my cue this becomes my speaker notes. All right. And then finally just be excited, right you went through this awesome mentoring experience you've learned these new things this is the most amazing element of being a human being to two of the most amazing elements of being a human being. One is love is falling in love with people, your partner your kids, the friends. The second most amazing thing about being human, the second most amazing thing about being human is learning and growing and like, you know, feeding your brain all of these cool things and you just had both of these things right now built a great experience with your mentor which is love, and you learn some amazing things to be excited when you when you share this, you know you'll have noticed that as I'm speaking. I'm speaking in a monotonal voice and saying, as I'm speaking, you will not you will have noticed that I'm not speaking in a monotonal voice, right because that'd be boring. You know I'm using lots of different ways of speaking and using hand gestures, my voice is going up and down varying in terms of volume sound like a weirdo now, but it will keep your audience. And then final. And most importantly practice, you've got five or 10 minutes, just practice practice practice practice practice practice in the mirror practice in front of your family in front of your significant other in front of your friends. Just practice get some feedback. And when you ask for feedback, say to somebody, tell me what's not good about it right when you ask for feedback in anything. What could you can I present to you and you can give me some feedback, everybody will always say yes. But if you don't give your audience you're the person commissioned to be critical, they won't give you any critical feedback. And what we want from our feedback is criticism, we want them to say that slides a bit complicated, you spoke a bit too quickly, you know those kinds of things are really important. Okay. Alrighty. That's it. Why don't we do some questions. And we'll see, well, let's see if we've got some questions. The, let me grab the old chat. All right. Hans has any suggestion for dressing for clothes. I think you should just dress to be you. You know, I mean what I generally would recommend here is to is smart casual right so you can see here for this session I'm sorry shirts right. I think if you wear a t shirt that's that's fine. So long as it's somewhat smart. And you know like, when I'm not on a camera I wear heavy metal t shirts because I'm really into metal. I have a band called Baron Carter. And so I think so long as you're smart. I think that's that's fine. Is it appropriate to provide links that's a great, great idea Sharon yep definitely provide links in your, in your sessions because if you share the slides with people then they can click on the links. Is it okay to use them Lucas is okay to use emojis in the presentation. But yeah, I think so so long as they're relevant. And I think it's fine. Don't use too many emojis. People who abuse emojis are annoying. All right. Yeah, I'm by the way I'm going to butcher some of your names. And I'm sorry, if I if I do so. Laxia, how often should we add memes to our presentation. I think memes can be fun. The key thing about memes is making sure that people understand. So you generally want to focus on memes that are broadly understood like one of the reasons why I picked Betty white and David Hasselhoff in my slides because most people probably know who they are. And even then they're kind of Western celebrities so people outside of the West might not be familiar with them. I wouldn't overuse memes because it can make your session look a little bit childish and cheap. So I use them sparingly. But they, they can be fun. All right, get your questions in. I'm just going through the chat log to see if there's anything that I didn't cover. Let's have a look. All right. Thanks a lot for the session. I already have a couple of things that I would like to improve my slides from Shri Anshu. Thank you Shri Anshu. By the way, I have loads of presentations that I've done online on YouTube. So if you want to see kind of some of the things that I'm talking about if you do a search for my name on YouTube we will find them. Mario, won't the presentations in the event be too repetitive if everyone follows the same structure? Yeah, this is a good point Mario. So think of this structure as a general set of guidelines. So, you know, I would recommend you break everything down into the introduction skill, like you know what we've covered here, introduction skills, experience and aspirations. This is the content that you want to include in your session. And then what you present it could be different. You might want to for example, go through the introductions first and then cover the experience and talk a little bit about about what you did and then cover the skills. You know, right, you might want to talk about introductions generally will always come first, then you might want to talk about your mentor and what your experience then you might want to talk about the project and then you might want to share the skills that you developed and then the surprises that you developed from it. So we're always going to have introductions at the front and aspirations at the end. But this bit in the middle. I think you can you can mix and match this also don't feel like you have to only present three skills you might want to present five skills. I wouldn't present more than five and I wouldn't present fewer than two. You might want to present, you know, for surprises. But the reason why I'm suggesting this breakdown here is that it gives you a set of things you need to do that that makes it easier to put together your session. All right, let's see what else we've got. Another thing as well is a great way to personalize your session is going to be to make your slides look unique to you right so when we look at, you know, let me move this channel away. If you look at my slides here they're very, you know they're very simple, right those black text in the white background, but you want you know use colors and design and make it uniquely yours that's going to make your presentation pop and stand out. Let me have a look at this. But great, great question, Mario. Shubham, I was planning to also discuss how I got accepted into the program should we do that. And I was thinking I could do that to my introduction. Shubham this is a great idea. But you know when we talk at this kind of gets back to Mario's point as well when we talk about the structure. Don't feel completely limited to it you might want to add after your introductions, after your introduction or part of your introduction like why did you apply, you know like why was this mentoring program interesting to you, you could talk about your the elation that you experienced as you went through it, right, you know, I'll give you an I'll give you an example if I go back to my slides here. The beginning of this presentation which I was showing you earlier on what I did to introduce it this is about how to build communities. I introduced myself clarified how you say my name and then I said you know when I grew up in northern England, which was quite a boring place everybody said this people don't know that maybe it's like we did back in the good old days, and it was this kind of sign that community was dying, but then we've seen Wikipedia open source the maker revolution we've seen crowdfunding we've seen all these other great examples of you know good example being Fitbit and all these great things that you can do within the Fitbit community. Right. So what I do is I introduce the session, telling the story and that's another great way in which you could kind of introduce it you could this introduction here could tell your story about how you got involved in it so again, think of these four areas is kind of like the chapters of your book, but what you put in each of the chapters should be unique to you. Okay. Let's go back to the questions. Purin Jay, should we go into the technicalities of our project if the project needs a lot of background knowledge to understand. I wouldn't go into too much technicality because I don't think it's going to be necessary and share enough technicality for your audience to understand what the project is and what it's doing, you know, so in my example today when I talked about react. I just said it's, it's a JavaScript framework for building user interfaces, right. In my example today. The mentoring was learning how to write code and then merging that code and then contributing code into that project. And so I could explain that without a huge amount of technicality. If you are working on let's say a low level kernel module, you might need to explain a little bit more about what it is, but just share the minimum amount of information necessary to help your audience understand what the project is because if you think about this what you're doing is we're saying, here is a project so you set in the context of that's the context the environment you're talking about in the story. Then you're saying, I didn't have these skills. And then I came in and I developed these skills and these were the achievements that I, that I, that I accomplished in this particular mentoring program. So you need to explain what the project is to be able to set the context. So, again, get your questions in. We've got a couple of minutes left hand just curious how did you combine your two cameras the camera that shows you and the ceiling camera that shows the whiteboard was that a functionality and zoom. Ah, good question. So I'm using something called OBS. It's open source project that you can use to create kind of a studio environment. Okay. So what I've got is this thing I'm going to zoom out this little thing here is called a stream deck. And what this does is it talks to OBS. And what I've got is a camera up there, which is a logic, Logitech Brio webcam, it's plugged into my computer. And then I've got my camera over there that you can see. And then in OBS what I've done is I've got this is my normal camera view. I've got a zoomed in view. Right. And then I've got a button here which goes to the overhead view. Right. And then you see how you can see this kind of like me overlaid on the top and you've got like these little animated dots in the background. I'm doing all about an OBS. Okay. And that's how it works. It's pretty cool. Oh, and by the way, OBS has got something called a virtual camera that you can then take the output of OBS, and you can, you can put it into into zoom right so if I minimize this. I'll show you what I'm talking about. Okay, so this. This is OBS here. And then you can see how it's it's this is my zoom session and you can see how this view here looks a bit weird because it's all zooming out is visible in zoom. All right. I'm so sorry if that's even butchering your name. Thanks for this extremely amazing session. Thank you so much. Can we add a live demo of our project in between. I think doing a quick if you've got a demo that's no longer than maybe a minute minute and a half two minutes. Absolutely people love demos if you built something. Let's say part of your mentoring program was to build a feature. Having, you know what I would recommend is is as part of when you go through the skills piece and showcasing showing off, you know, let's say skill number three is that I built the thing right this is my accomplishment and then demoing it I think will be brilliant. I would recommend if you do if you want to do a demo is that you pre record it you can use screen recording software. It's available on Linux Mac windows, and what you do is you create a video remove the sound and then you walk through what you were doing. Okay. That's going to be the best thing I wouldn't recommend doing the demo live and sharing your screen, because you may have technical issues when you're presenting, you know that if you create the demo video, then you're good to go. So you remove the sound. And then what you do is as you're going through the demo you talk through the demo as the video is playing. Okay. Let me see. Shubham. This is going to be our final question. What's a good way to end the session I was thinking about ending it would would love to interact with you and my relevant things should that's a great great idea. I should have honestly, this is an oversight on my on my part should have added a slight miss. Yeah, just add rabbit the session. Thank you audience say thank you so much for watching my session today. Make sure you thank your mentor. Again, thank you Betty for all the amazing guidance you provided. Thank the Linux Foundation, thank you to the Linux Foundation for running this amazing mentoring programs is phenomenal. And I would have a slide at the end that's got your, your, if you've got a website, and then your contact link like certainly put your email address on there. Okay. You might even want to if you if you're using a social media service like Twitter or Instagram or whatever, put your links on there as well. That's how I do it. Alrighty. And then final question, Han, I'm sure if I missed that part do you recommend we have maybe a minute for questions and answers. I probably would skip that I don't think you've got enough time five to 10 minutes. All right, my friends, thank you so much for joining me today. I hope this was useful. And if you've got any questions, feel free to reach out to me my door is nailed open. It's john at johnobacon.com. You can send me an email and we'll wrap it up today. Thank you. All the best with your sessions. I'm looking forward to seeing it.