 Hello everyone, my name is Rostov Prokop, I came here to tell you something about my internship and tell you something about the path I went through. So I'm a high school student and I've been on the internship for about a year now. So I think I have something to talk about. So the internship, I found out there are more types of internship. Redhead has high school internship and then college internship. College internship is for college students, they can also get paid. High school internship, they are more of a learning experience for the high school students. So about picking the internship. When picking the internship, one should consider a few things. First of all, I'd like to say why should anyone even consider picking an internship? Why should a student consider it? Why should a developer who will have an intern consider it? For a student, it is a great experience in my opinion or a great way to learn something from the pros and to get some knowledge from the professional field. And for the developer, it is an option on how to pass the experience, which is hard to get generally in school, sort of make your own little kid programmer and teach him your ways. So next question, what you should ask yourself before even applying is what do I want to do or what do I want to do considering my experience? In my case, I didn't have any. So when I got sent the list of the internships, I didn't understand 90% of it. I remember there was some stuff like C kernel, something, something. I didn't understand the language it was in, but I didn't understand much more. So I went with a pretty topic that seemed easy, which was towards Ruby packaging. I was like, hey, Ruby, I heard about it a bit. Packaging, I know the Linux distributions have some packages. Okay, seems simple enough. So, okay, let's say that you picked what you want to do. And now you maybe want to do the interview as a developer. So the student comes to the interview, and the interview is stressing. Even if you are 20 years old, 30 years old, you can expect the one you're interviewing to be stressed. So for me, this was first interview with large, serious company, even though it was the high school internship position, but still. So this is something for the developer to take into account that the student will just be nervous. That will just happen. So next, the actual internship. Here, firstly, I would like to go through some, I guess we could call it bad stuff or fears. First thing is what about the mentor or the guy that will have you? Will he be good? Will he consider you not knowing a thing? Will he be prepared? Is he a people person? This thing is in my opinion important because essentially, if you are a high school student, then this was the first, it is the first most of the time experience in the Linux or even open source world, which also shaped my opinion on the whole thing. So also, how will he operate with some stuff, which I will mention a bit later. Okay, the learning process. Okay, first of all, there will be tons of new stuff. It will get really overwhelming at first. For me, I didn't understand anything for about a month. So it was hard to kind of gain some solid ground under my feet because I didn't even mostly understand what comments should I be using, what libraries. Okay, I should go here, but is this the right way to go about it? But this will go away with time and it isn't something to be afraid of since also, mostly when you also ask the mentor, they are mostly nice and will explain it. Maybe for the fifth time, I hope they will still have the nerves. So more for the developer or even the students. The students should ask the terminology as it comes, which I didn't do and that's why it got so overwhelming because there will be a ton of stuff. Linux, Fedora, Fed package, this Git, Git, just two tons of stuff and it is hard to explain it in one session. So which is why it is important for the developer or ask the developer to have something ready for the student, some guides, books, articles that are on the internet profile be free and maybe even open source. This could explain a lot of stuff in which cannot be explained in the short time that is given on the sessions, which for me is once a week about one to two hours, which really is not enough time to explain everything. Also, it is good if the internet is given options in what could be done. I was given the option later on when we went a bit out of the scope of the initial internship, which I will be talking about now. So it went a bit like this. We finished the main package, which was some documentation tool. The developer went, okay, you want to continue? Yeah, I want to continue, but on what? Well, the coding has this idea and this was another half of the year of the internship, which is, I think, a positive that I was given the option to continue. Okay, I think I covered the bad stuff enough. So now I'd like to introduce some good moments or bright wiles, I'd say. So it got names of the outcomes, but ice cream. You may be saying, what the hell is ice cream doing there? Well, when it's summer in Red Hat Day, sometimes they have ice cream and when you get asked to have free ice cream, why the hell not? But you get to contribute to the open source yourself, work on your own library or even learn from the pros how it is done and it can really make it all easier. Just having the professional person explaining stuff to you, not having to search it on your own, which you might even get to some unreliable stuff, something that will give you bad basics. So this is about what I think is a bit about it. About to summarize, the intern is going to be stressed from the start. I was and a lot, which is why I'm mentioning it so much and there really wasn't much to be afraid of in the end. One thing that is important is to somehow take into account that you are a high school intern. As a high school intern, I didn't know everything or maybe interns all around just don't have the 10 years of experience. So it is important to not expect that much from them and it also is good to have articles, books prepared and the main goal of the internship in my opinion is for the intern to learn some stuff in general open source even if it doesn't have to be much. That is about everything I have prepared for this presentation. Thank you for your attention and you can find me on Twitter, GitHub and GitHub under this tag. Any questions you might have? Yes? I was told that the documentation team needed some tool for them to write the documentation which was ASCII Binder and it is written in Ruby and it was needed to be packaged into Fedora which was... From the start, yes, later on we moved to script which is now the outcome of the script can be seen on the Fedora developer portal. There is a lot of stuff to do still. Any other questions? Yes? Okay, so just to repeat for recording, the question was if my mentor did some regular checkups or if he would do it would help. So my mentor didn't do any regular checkups since it is sometimes hard for me to organize the time schedule so it is harder than all of that. But it could help if they reach out, hey, how are you doing with the package? Do you need some help? I don't know, once a month. It may be could have helped. It is not that bad of an idea. My opinion. Okay, so anyone else? Yeah, I was going to ask about Balak. Okay. I'm not the best of a student in high school. I'm a good technical student. I like to learn programming and stuff. So just sometimes I just... Some days, or maybe weeks last week, or this week too, the grades were closing up and there were like six tests a week. So I just said, hey, I can do not much in this time span. I can try to. Yes? I teach in my school. English, I think it is called... Well, the question was, what about the IT in my school? Well, the thing is that I am attending general high school, general knowledge, chemistry, physics, almost everything. But the IT's first, second grade was just, okay, this is presentation, this is how you do presentation, this is how you work with work. Not much in this grade. We got to pick some more technical stuff like Java programming, but I wouldn't much compare it to the Red Hat because the level for me is just so different. Maybe even because the focus is different. Meanwhile at the Red Hat, we started with Git, we started with Ruby, okay, this is the language. The school, we are just going slowly with the language and it is not that hard of a subject. Git was introduced actually by someone from Red Hat. Even the teacher took notes. It's not a technical school, so the IT won't have that much of a quality. Okay, so this was, I think, about how the subject is limited. As you said, the subject has limitations. They don't introduce the stuff I got introduced to. For example, the paradigms. I got introduced to functional object oriented. We got somehow into the object oriented, but it was just general because Java is subject oriented and so it would be weird to not mention. A lot of stuff I think is missing to a lot of students because not even how to structure the code is going to make some trouble. He just comes to someone and, okay, you maybe want to put that into a standalone method. It may be better. Meanwhile at Mind and Tribule, it was like, it is better if you put it there because if you may come, I don't know, tennis earlier, or for the overall readability of the program. So at the Red Hat for me, it is really much more of a quality. Anyone else? Yes. Of course, we are planning to study IT. 100% I plan to continue in this area. Great. Was the internship fun? For me, yes. I was myself motivated for the overall subject of programming and all that. Okay, so was it fun or did it keep me busy? Well, it was fun for me. It was fun for me to learn new stuff and I came to something I couldn't go on in one day. I was still motivated the second day to have some time with the problem and to learn more about it. So for me, yes, it was fun. Okay. About the learnings, or did you explain what to focus on? Because sometimes the condition is quite large. Do you have the same feeling I would have? Do I really need to read all of this? This question was about the learning process and handing me over the whole code documentation was problematic. Well, I maybe didn't explain this that well if the question got there. Since we have session once a week for hour or two, we go, we sit, and okay, this is what you should be working on now. The mentor took a look, he skimmed over the package, and okay, this is this, this is this, okay, it might not cause that much trouble. I more got the documentation as the reference point to have something to search in if I get lost and if I get ultimately lost, I can still ask the mentor later. Okay. Okay, is this all? Seems like it, so thank you all for coming and have a great the rest of the day or day.