on the cloud. Okay, we should be recording right now. So I'll get started. So hi everybody, welcome to the Jenkins in Google Summer of Code webinar. This is for Google Summer of Code 2023. So this webinar is to help address the question, how do I get started with Jenkins in GSOC?  So my name is Alyssa Tong, and I'm an org admin for GSOC. Along on this webinar with me are Jean-Marc Mason, also an org admin. Bruno is also Bruno Verrachten, sorry Bruno, is also org admin. Chris Stern is our org admin as well as a mentor. And then Marc Waite is a mentor for GSOC. So next slide please. Yes, thank you. So some housekeeping notes. So we are recording this session and I'll make the recording available within discourse and Gitter sometime later today. So for Q&A, feel free to put it into the chat window. We will answer them as we go along. And if we have time at the end of the webinar, we will open it up to Q&A as well. So for questions that, you know, that may come up after the event, feel free to put it into the Gitter or discourse channel and then we will get to them, you know, as we see them. And of course the Code of Conduct applies here as well. So basically what it means is be kind to one another. So next slide Jean-Marc. So this is what we're going to talk about. You can quickly go through it Alyssa. Yeah. So in this session, we will cover what it means to participate in GSOC. And as I mentioned earlier, what you could expect and what is expected of you. We'll quickly go over what is GSOC, Jenkins and GSOC, and some important timeline that you need to remember and stick with because Google Summer of Code, they're very adamant about sticking with the date that's been given. And we do the same as well. So we have to follow those dates and those deadlines. And then as I mentioned, like before, Q&A will open it up at the end. But if you have questions during our presentation, just feel free to put it into the chat window. And one of the org admin or mentors will answer them. Great. So well, welcome everybody joining the call or listening after this live session. And basically, so you want to participate in Google Summer of Code short GSOC. Well, that's a good idea. And it's a great decision that you're making. So with this adventure, you will learn a lot on technical fields about open source. And you will do that while being coached by people. So it's a great way to learn and get experience. It's also an incredible opportunity to have an impact by your work, which you can have with open source very easily. But here you have really a great opportunity that your work will be useful and will change something. Participating to Google Summer of Code is also a nice way to get some pocket money. So Google has big pockets. And they want to teach people and to promote the ways of open source and open source. And we're very thankful for them to sponsor these kind of events. And participating to it is a nice way to get some money. And who knows, by yourself, a new laptop or whatever you need for your studies or for your starting career. And talking about career, participating to Google Summer of Code is also a great way to add a prestigious line in your resume. So there are many, many reasons why people are interested to participate in GSOC. So what is GSOC in a nutshell? GSOC is this. It's a great adventure. You will see great things. You will do great things together. And this picture for me really summarizes everything. You will get to places where you didn't think that you would get to. And like Alpine Adventures or Himalaya for people in India, which is there, this can only be achieved as a team together. Generally, you have a guide that brings you to explore these incredible sceneries and participate to these adventures. There are pitfalls. It's not always sunny as on these pictures. It's tough. You'll have to walk. Sometimes the feet will hurt. It will be cold, damp. And this is part of the adventure. This is why people like mountain climbing. I want to warn everybody that wants to participate to Google Summer of Code. The Jenkins team has only a limited or finite coaching capacity for Google Summer of Code. That means there are only a limited number of slots available. And not everybody will be selected. So the selection process is already part of the schooling of the adventure. It's the first big hurdle to win. So only the strongest proposal will be selected. And on the criteria, what are the projects that are the more likely to be successful that will have the best and useful contribution to the Jenkins project and the best return of mentoring and investment. So we need to find a balance in all that. The other important thing is that you need to know this is a long and important effort. It starts with a proposal. It will take several weeks. You need to be involved. You need to do your work there. It's exactly like climbing a summit. It takes a lot of effort to get there. And you need to get prepared for that. And this is the presentation we have now and the kind of advice that I would like to share with you. In order to reach the summits that we've seen in previous pictures, where you prepare. You get in shape. You lose an extra kilos, which I maybe should do myself. To do that, you build muscles. You build your technical expertise in order to do that. And then there will be the selection process for that. So a couple of words. What is GSOC? How does it work? Where is the front? Where is the tail? And where does it start? So the first important thing to do is read the available documentation. There are a lot of explanations around. Don't hesitate to read it once or twice and then ask the questions. How to do. We built over the years. It's the seventh year that we're participating to that initiative. Very proudly. We built up a lot of references, useful references for contributors. Word contributor means in the new definition of the program before it was limited only to students. People that were graduates or doing a master somewhere. Now it's also open for young professionals. So these were the word contributors. Have a look to the projects that were presented last year. Look how they were documented. Listen to the presentations. They succeeded. It worked with them. Get inspiration. Learn from the people that were before you. Google has also some very good pages and good readings on how it goes. What is a project idea? What is the role of mentors? What is expected? A lot of document. Take the time to read it. And we'll have other opportunities during the process where we can discuss together in where we're available to answer questions. The only thing we would like is that you have read and you know the theory of the program. So how does it work? So we're currently in the very initial phase. Google announced a couple of weeks ago. Yes, we're going to do Google Summer of Code 2023. So very initial and we're starting. This is the moment where you can build if you're interested to participate with the Jenkins community in Google Summer of Code, you can build the Jenkins muscle. How do you do that? You do that by understanding the Jenkins product, experimenting, reading, start your own Jenkins instance. And Chris will give you some tips and advice afterwards. But you also learn how the ecosystem works, how the community, how do we communicate? And there's one strong point I want to make available or are you aware of, I'm sorry, is that the purpose of the initiative of Google is to learn how open source works. It's different of how companies work. A lot of things that are shared, but open source has one principle that you need to remember is that everything is done in the open. You share. That means that when you're going to work on an idea, when you're going to work on your code, you're not going to do it in your corner, in your den somewhere and only show it at the end of the process. Here the process is that everything that you're going to do, everything that you're going to build, that you're going to learn is written down somewhere, shared, that everybody in the community, there are many time zones involved, there are different skills involved, but everything is open. So you're going to write and prepare a project proposal, all that is done in the open and you ask the community, what do you think of that idea? Nobody has a comment about that? Okay, then we go on, but at least you have described your idea and you requested for comment. And so I'll come back later in the explanation. So this is how the community works.  So this is something that, and this is now the right moment in December and January to learn these kind of things. Nothing to really worry about, nothing really with deadlines or so, you can enjoy the end of the end of year period, depending on the region of the world where you are festivals are different. January, February, you're going to start studying more deeply and choosing a project idea. So project ideas are currently being built, discussed, and are available for review. Start reading them, start understanding them. So I'm just going to switch quickly. No, this is not what I wanted to do. There it is. So this is the Jenkins IO website, is the main Jenkins, and you go in sub projects, Google Summer of Code in Jenkins. This is the main page of our project of our initiative where you have a lot of explanation. This is the GSOC home page and we'll update it regularly. This is where you have a direction to all the various documentations. This is the section that you should look for in start reading. We have some dedicated guidelines, good readings, a couple of books also that are mentioned on the Google portal. Have a look there and you can look, for instance, everything that's available here, what the communication channels are, office hours are going to talk later. These are here the current lists of projects we're working on. I just walk here. So the first status of project ideas are the ones being discussed. That means somebody woke up in the morning suddenly and I have an idea. And he writes it down, people discuss us, but what do you mean? What would be the outcome and so on? And so it starts to crystallize. Currently we don't have any projects anymore that are in this very early stage. These are the projects that are in draft mode. These are ideas. We have a rough idea what it could be. Not all have mentors assigned to. When you click here on it, which one can I take? I'm going to take this one here. So you have details on what is the background, what are the skills required, what is the difficulty, what are the outcomes and a lot of details. This is the first stage. Study them and try to understand it. We're going to organize the second half of January, one or several sessions where the mentors will present each project idea in more detail and you will be able to ask questions and know what you mean. I understand it that way. Is it in line? I have this novel idea. Everything is done in the open. Everybody here is the same. So we discourage any one-to-one discussion during the whole process. So you can already start to look so you know what to explore. So you can focus your learning process. So this is what's going to happen the first part of the year, January and February. In March, February and March, this is where you have chosen a project and you're going to build your proposal. Now we're going to do something at that moment very unnatural, especially unnatural compared to what you've been taught at school or so. The first principle at school, you don't cheat. You don't look what your neighbor is doing and you protect your work that somebody is not going to cheat on you, but this is not the way we work. It's the common effort that will make the product and the world better by working together and sharing all the ideas. You may start an idea and somebody at a certain point will add ideas to yours and yours will get better or somebody else will come and will compete with yours and add other things and at the end we're going to decide which one is the strongest idea which has the best chances to reach the goals that we want to achieve with the program. So that means that we very strongly encourage you to publish your drafts and make them available to everybody, meaning that the mentors are going to read your drafts and going to ask questions here. I don't understand this. What do you really intend to do there? Can you make that more precise? The community, that means that all the people that are either users or contributing to Jenkins will also ask questions or tell you here, this has been proven to be a bad solution. You're going to burn your fingers with that. Try this method or try this goal or these kind of things. So it will be a very weird process for you, but believe me, it's a very rich process and it will make your draft, your proposal, stronger. Yes, somebody can come and pick your idea. It may be faster than you, but it's part of the game. So you need to be the best you need to learn and we're there to help you and we're there to help everybody the same way. So there is a little bit of what's English word for that, but natural selection of idea. It's tough, but this is the way it works and this is why we don't want to privilege this person or that person by giving him insight. So this is something you really need to understand. We're going to explain that further. So we'll organize regularly during that period what we call office hours. That means that we're going to organize a meeting every week. We're trying to look to have the correct time zone to have it friendly for the biggest, for the majority of the participants. I see from the names here that will be more on the Asian side, but we'll organize a meeting. That meeting is just where here I'm there and what are your questions, what are your concerns, what are your doubts? How can we advise you to move ahead? And this will be the backbone for you to progress and move along on this adventure and learning how to move ahead. So mentors will be there, org admins will be there to help you. April 4th is the moment where the dice are rolling. This is where you must have submitted your proposal. So this is the goal of the first stretch of your GSOC adventure. Why do I say the dice are rolling? It's because you have no influence anymore. You've done all your work, you put your heart in it and now you need to wait. What will happen in that period is that the org admin and mentors will read in details all your proposals, will reflect on them and will rank them and will build a proposal with a number of slots that we're requesting from Google and providing them evidence of what is the coaching capacity we have. And so Google and our organization will come with a proposal and say these are the number of slots that we request. These are the projects that we want to run this year and these are the people we select in these projects. And this will be announced May 4th and this is where it really starts. So all that is a preparation and you will realize there's a lot of work involved to get up to there. From May 4th, this is far but in a nutshell what will happen is that during a period we call it the bonding period. I find it a funny word but you will first learn to know your mentors and the mentors will learn who you are, how you work, you will set up a work framework, how are you going to work together, you're going to work out the architecture, what you're going to do. So set up the framework. And then about mid-May, well it depends because we have an elapsed period for the complete period. Then the actual work will start and how it's done will really depend from project and mentor teams and how you get organized will also depend on your holidays or if you have mid-term exams or this is then left to the freedom of every project. The organ men's will be there like a fatherly figure saying that everything goes well and that no fighting in that we get the goals achieved. There are two milestones, two important milestones that you need to know but we'll give details later is that somewhere during the summer we're going to do a mid-term presentation and evaluation where did you reach, what did you achieve, what are the things that you can show and brag about. And then somewhere in September we'll have the end presentations and also presentation of the deliverables and we'll do a wrap up. So this is the timeline. I realize I have been in a lot of details and I've eaten a lot of time so I apologize for that. I wanted to give enough details about that. Now to the more technical part and I give the word to Chris if you can give more details on the technical part and how to build the Jenkins muscle. Okay, sure. So I'm going to talk a bit about tech stack we're using at Jenkins. So most of the projects are in Java, some in Kotlin and for website it's mostly in Java services as in Ruby. Some projects have been in bash so it all depends on the requirements. And for the web development of Jenkins.io which is a project idea we have for this year for our main website we use ASCII.org. There seem many project ideas involve proof of concept and documentation such as the website we've done I just talked about and also some Android and OS projects. Many of the projects involve tooling or development tools. So it's a good idea to read up on these and do some research and make a good post on the next page. Okay, so how to prepare? First thing first we're just to do research on the project idea you're interested in. That's important because you need to have a context and we don't normally give out too much about the context. So you have to be original and be able to come up with some solid ideas about what it's necessary to make a successful project. And two, do ask and tell any questions on IRC such as Gitter. This is because it will help us to differentiate to tell who is more likely to be able to successfully complete the projects and will choose the contributors accordingly. And three, interact with the community. So don't just think that it's all about what we saw. A large part of the application has to do with the interaction as well. So do do engage yourself with any conversations you might find interesting or you might find rather than to your project idea. And four, develop your proposal with the community. So like Jean-Marc just said, develop the proposal with us. So ask questions, share your proposal, policy with us. If you have any doubts or questions, do ask. Five, show us what you can do by submitting pull requests, patches, fixes, impactful contributions. So I think I've heard from some other organizations that they do consider pull requests as a must before they can accept an application. But I don't think that's the case for Jenkins, but we do appreciate any pull requests submitted as part of the application process. It's a good sign for success, a good indication for success. Yeah, yeah, true. Okay. So next, so it's to remember. Remember to check Google's program timeline, which is allowing to given and to adhere to it, because like we have very, very strict timelines and we don't normally like give grace periods, even if you have very legitimate reasons to be late for something. So GSoc contributes to application period begins on March 20th at 6pm UTC. So that's, I think that's about March 21st Indian time or Asian time. And GSoc Contributor application deadline, it's on April 4th, same 6pm UTC. So that's April 5th, Asian time, except GSoc Contributor projects were announced on May 4th, same time, 6pm UTC. So don't be late, be on time and be prepared. Yeah, that's important. I'm going to pick up here, Chris, or you can jump in afterwards. Here are some resources. At this point, I just would like to pull into the conversation last year's participants. So we have Hushikash, if I can see correctly, I'm not monitoring chat. So Hushikash quickly, well, not quickly, but take your time. But what would you like to share with this year's candidate for GSoc? So the first question is, what did GSoc bring to you as an experience? And what worked well? And you would have done better if you had known or what is your experience. So can you share a little bit your experience of last year? So yeah, so I feel communication is a key for a successful project. Initially, I was a very shy person, you know, I didn't know what kind of questions to ask. I was worried what people would think about me. If I asked some silly questions, I was very anxious to share my ideas. I didn't know where to get started. The Jenkins code base is really big. There are so many files, you don't know where to get started. But Jenkins community did make it easy for us. It was a very comfortable journey. I didn't know how those three months just passed. But then it was a very smooth journey. I did face a lot of challenges. But in the end, yeah, you have to just get started, explore the code base, be very active in the community, and take the help of all the people in the community to create a very strong proposal. That's sound advice. Thank you for your comments and advice that I really cashed. And it comes also to my experience. And having seen you travel on this path and your climb on the mountain and reach the summit, one of the key elements is how do you communicate how do you efficiently ask questions? How do you explain what you intend to do to ask for advice, direction? It's like mountain climbing. I don't know if you're familiar with it. For me, it tells us something. In order to reach that, you need to communicate with your teammates. You need to explain what you want to do and ask for feedback. So this is key. It's a hurdle. Pushy Cash had some issues in the beginning. It was, I remember, very shy in the beginning. And who am I to dare ask to people like Mark Waits or these knowledgeable people? I'm just no. You're an important person. You come with your experience. You come with your heart in that adventure. You're worth that we as a community take the time to help you. But we need to get that discussion going. We need to get that. So this is the most important advice. Efficient communication. Don't assume that the person you're talking to is sitting near your desk and sees what is your on screen. It doesn't work. What doesn't work or what did you intend to do? What are you trying to do? See these kind of things. Don't assume. This is what I feel a very most important lesson in this complete adventure in one of the keystones of open source. So thank you, Rakesh, to have stressed that point. And now I've eaten most of the time here because we're now listening to your question. And so you can practice the first lesson being don't be shy. Ask questions. We're there to help you. The first question was from Aditya, if I pronounce it correctly. It was, can I contribute on these draft project ideas from now? Yes. Yes. Yes. Yes. Yes. Yes. Yes. Yes. Yes. Go ahead. Mark, how can we do that at this stage? So there are two different ways to contribute and then I will give the word to Mark who isn't as his own experience than maybe Chris Kim chime in. The first way to contribute and clarify is to submit a pull request on the project proposal. And this will be then reviewed by the team. This is not the most efficient way to do it. If you have lightweight ideas, questions, queries, you can use community.jenkins.io which is the discourse where you can start here. I don't understand this work, this work. Where should I look for it? But nothing refrains you to really start giving structure. And if you have ideas, you can really start contributing on the idea for that. Create Google Doc document. So we're sponsored by Google. So everything uses Google tools which work well for that purpose. Create a Google Doc document. Good idea to use the template. That's available. Generally, these kind of contribution, these kind of working is done in a later phase because now the project ideas are still very fuzzy. But here, if you already understood it and you come with novel ideas in it, go for it. You've seen what Mark reaction on that. So to summarize, can we, yes, yes, yes, three or four times yes, how discuss on community or Gitter, but community is better for that. You can update the proposal that's on jenkins.io, submit the pull request, and even start creating your document, make it public, and announce it on the Google channel on community.jenkins.io. Mark, was I, do we have things to add? Do you have other advice or? No, I think you did great. The answer for me is, can you contribute to project ideas? Absolutely. You can do it by getting involved in conversations on Gitter Chat. You can do it by getting involved in conversations on community.jenkins.io. You can do it by getting involved in conversations on the Jenkins developer mailing list. You can get involved with the project idea in the advanced way that John Mark said, of submitting pull requests to the project idea to propose refinement for it. I think that for me is a later stage, but just being involved in the conversations about this idea, helping clarify, because inevitably, if you have a question about a project idea that's listed there, others have the same question and they're too timid to ask. So you be the bold one, you ask the question and accept that people will give you an answer. Chris, do you want to add something? Oh, Hushikash, anyone? I had one point I wanted to ask. I wanted to just add, don't get dejected if your question is unanswered immediately. It takes time for the community to answer your questions, but I'm pretty sure someone or the other will answer your question. That's a very wise and very true comment, Hushikash. Thank you for sharing that. Yeah, we're working around the clock around different times on market. Yeah, so we sleep. It's a very good point that we sleep. And I actually sleep at different times that other people sleep at. India is almost 12 hours away from me, right? And therefore the time of day for you, for Hushikash, for instance, is usually exactly opposite from my time on the planet. Welcome to a worldwide project and the complexities that come with being in a worldwide project. One of them is we're not always awake. The other is many of us have jobs in addition to being contributors and we want to be sure that we do all the things. So ask your questions. Also, don't be shy if it takes a while to answer your question to refresh it. Hey, did anyone have this? Can anyone help me? Sometimes a question that's asked is challenging enough that it actually requires some research from us and from one of the people who would respond. And that research may be non-trivial. So if you ask a really hard question, be extra patient because sometimes really hard questions require really good investigation. But we also have the holidays that's that's approaching. So expect some delay there as well. Very good comment. Yeah. Are there other questions? Mark, can people turn unmute themselves to ask questions or is it? If they'd prefer to ask questions verbally, they certainly can. They've been given the permission to unmute themselves. Vandit, let's take you to its question first. He says he usually takes four or five hours of research and development and starting on an issue. Should he be speeding things up? None of us are worried about how fast or slow you proceed. Truly, none of us are worried about your pace. That's up to you, what time you have available and what you can do. So work at a speed that's comfortable to you. I spend a lot of time in debuggers. I spend a lot of time writing automated tests. I spend a lot of time interactive testing, none of which is actually writing new source code, and that's okay. Vandit had the question, if he gets stuck somewhere while working on a patch, is it silly to ask for a review? Not only is it not silly, it's encouraged, highly encouraged. The best form of ask a question is usually submit a poll request with your idea of how you think you're going to do it that shows you've done the work to make your poll request compile, that you've understood enough to think about the tests for it, and you've submitted it. Now, it may be that you say, hey, I'm submitting this with a failing test. I don't know how to make this test work. That's okay, great. That's a good way to ask a question, because I can look at the source code or others, Bruno or John Mark can look at the source code or Chris can look at the source code and say, hey, your source code is making this mistake. That's a much easier answer than, oh, it broke. If it broke is all you tell us, we're going to say, well, fix it. And that's not helpful to you and not helpful to us. Okay, I think that's one more question from Pranav. We have PR, should I submit, should they be good first issues or some advanced issues? I like that question. So submit a poll request, it can be either a good first issue or something more advanced, whatever, whatever helps you build the skill. What John Mark described it as is building, developing your muscles for contribution. And part of that is you develop a skill, the skill to phrase your poll requests well, to understand what the expectations are from reviewers as you submit a poll request. Oh, you didn't, you ignored the checklist. No, don't ignore checklists. Oh, you forgot to add tests. No, don't, don't forget to add tests. Please add tests. It's good work to add tests. Oh, you forgot to interactively test it. And we'll be sure you test interactively. Those are all part of the process of submitting good poll requests. And there's still you can develop. Go ahead, John Mark. Right, no, it's building your muscle is building the skills and it's a way of working. And just remember, if you're still studying, these skills will be very useful to you when you start your working career. So it's a great opportunity, even in the selection process, everything that you learned in the selection process will be useful for you in your, in your studies and a future working career. So it's worthwhile to do. And if you're not selected, next year will be there and you make a stronger proposal because you've learned a lot of things. So it's worthwhile to invest, even if you believe that you don't have a chance, which I personally don't believe. Speaking of selection, John Mark, Sorab is asking on which basis do you select students? Oh, now, to be honest, it depends on where the moon is standing, what is the height of the water and so that's not true. So I'm making a joke. So the selection process uses several criterias. And if I remember well, these were written down last year, I will make sure that we have guidelines for that. In a nutshell, the, and I'll go back to where I wrote it down. So here only strongest proposal will be selected, which are the projects that have the best chances project and contributor have a best chance of having a successful outcome. That means that you've shown that you have the communication skills that you understood problem that you're able to explain what you want to do and that you've shown that you have the right stuff to bring it to the end because we have three months to do that. I'm sure and convinced that everybody will succeed. It's only that some people will need more time and more help to do that. And others, it will be quicker. We need to select. So it's, it's, it's competitive. Other criteria is, is the project useful to the Jenkins project, to the Jenkins community? Because you can come with your own project idea. We've been selective. We, we worked out some proposals for you to work on. These are, these are good. These are useful. But some are more useful than, than others. For instance, I know I'm not going to give hints there, but try to put yourself at the place of, of users of the community. Oh, that, that will be useful for people. And this is how I will make it more useful. Don't forget to explain that. Third criteria is, and there we will be assessing your skills as a contributor. Where will we have the best return on the mentoring investment? If we have two equivalent projects and two equivalent proposals, if one project will require an involvement of the mentors of, let's say, 10 or 15 hours a week, and on the other side, we have a contributor who we assume that he's self-sufficient, that he knows, so we don't need to explain, for instance, what is a unit test? Or, or he can solve simple problems. We'll prefer to select this contributor because we then, with the mentorship, a capital that we have, we can go further and go farther in the, in the project. Did I answer the question? Well, I think so. Some people were also asking about building the Jenkins muscle, and Mark's suggestion was to use improved plugin tutorial for Jenkins plugin. And I still have lots of things to learn about Jenkins, but this part helped me quite a lot. And there was a previous suggestion from Mark, which is go ahead and try Jenkins on your own. Use Jenkins to build a project that would be useful for you, that what I do on a daily basis to progress on my knowledge of Jenkins. So yes, go ahead with the improve a plugin tutorial, install Jenkins on whatever machine you have, be it your laptop, Mac, Windows, Raspberry Pi, whatever, even the Oracle free chair, it works just about everywhere. So go ahead and try that so that you will build the two kinds of muscles, some muscles for improve a plugin tutorial and the muscles of using Jenkins on a daily basis. So to give more weight to what Bruno was describing, I have, I like the concept of healthy self interest. Healthy self interest in this case is a way of saying, do something that is interesting to you and use Jenkins to help you do it. So if you have an assignment at university that is write some Java program or write some C sharp program or write some Python or some NP some node JS, whatever. You've got some assignment, install a Jenkins controller and let it help you build that thing. You learn it helps a little bit. And you've now used what you already know. Oh, I knew how to build this project for university work or for school work or for whatever. And you learn something about Jenkins in the process that exercise of using Jenkins to do something that matters to you helps you and will help prepare you to contribute to Jenkins. Well, I just opened the chat. I've seen a question from it about joining discourse and Gitter. I agree with Bruno, but they're complimentary. So they're two different ways. So you don't have to. But it's good to have a foot in both. So depends how much time you have. Are there other questions? I see there have been quite some activity in the in the chat. So don't be shy. So while you're thinking in fumbling to find the unmute button, I see that Nittish has unmuted himself. You have a question? Either Nittish has a communication problem. Hi, everyone. Okay, I wanted to ask if I wanted to ask if I'm not on the discourse channel. Should I need to join because I'm only on the Gitter channel, because I find it more active and easy to use. Do I have to join the discourse one too? As I say, good question. So thank you, Vanit. They're complimentary. There are different ways of communicating. I would recommend the following. So connect and register to discourse. So the community.jankins.io. They're interesting announcements that are made there. Connect to it. Look if it works for you. If it doesn't work for you, just leave it alone. So and continue using Gitter. Did that answer your question? Yes, Mark. Thank you. No problem. Well, here I have the same problem pronouncing correctly first name. I hope at the end of this G-Soc adventure to learn or I need to come to India and have a crash course and pronouncing first words. Yes, I'll be eagerly waiting for it. This is what I fear. It's too many things to discover over there. Don't tempt me. Great. Are there other questions? I want to be respectful on people's time. It's probably already late. I had a question. I want to know that since we have different time zones. So I was thinking if I want to ask a question on Gitter, should I ask them like around this time, like what the current time is going on, or should I later on in my morning? So currently I'm working as a professional right now. So I have time in the morning or late in the midnight around midnight. So I can work and ask my questions during this time around this time or after seven to eight hours. So when you guys will be able to answer my questions, right? If I ask me questions right now around this time or after six to seven hours. I love your question. It's a great question. So the short answer to that experiment is how it works and what works better. The problem they exposed here is a typical problem of when working on open source and also in professional career when you're working in big companies. And one of the purposes of this here is to learn asynchronous communication. The whole communication process is key. Different ways to communicate. One is synchronous. This is what we have now. We have a meeting, but you have to stay late in the evening or people like Alyssa need to wake up in unruly times very early for her or I need to work and so. But you can exchange a lot of information synchronously in a meeting or in a chat where you have immediate interaction and where you have rewards. On the other side, you will have different type of answers and very often better answers. If you really go into the asynchronous way of working, it has other requirements, but you reach a bigger crowd of people that way. That means that you're going to reflect on how you ask your question and you're going to receive an answer several hours after. So it's really about mastering the different communication channels. Now to be precise in answering your question before giving the word back to you with it, the majority of interactions here is asynchronous. And Mark and Alyssa have emphasized that in the period we're getting in, I'll be visiting my grandchildren will be off. That means that we will not be able physically to reply immediately because either we're sleeping or I will be playing with the kids or and I need to sneak out to get a laptop to answer you. So we'll enter these kind of periods where this but in your project, once it's starting to be efficient, having synchronous communication moments will be useful. So you really need to learn and master the two ways of communicating and depending and we'll make the two types available to you. Did that answer your question with it? Yes, I got it now. I won't be thinking much of it. Should I answer? Should I question? Put the question on later in my night at my time or in the morning because generally you might you might also might be having holidays, so it won't guarantee answer to me. I'll take care of it and I'll also make sure to master both the ways of communication as usual. Thank you. Here, try it out. You will learn. You will learn how it goes and but don't expect an immediate answer as Hoshi Cash also mentioned that.  Just leave, let time to answer the asynchronous way of doing it. Are there other questions? We're two minutes overboard but Alissa is going to frown at me and say I talk too much but I think we have time for one more question, Alissa. Sure. Okay, one last question. Oh, then we answered all. So, I'll leave a couple of seconds. Mic open. Hi, John. Go ahead. Is there anything specific we need to know about Jenkins Chira? Anything different? Because I use Chira in my professional environment. I know how it works but is there anything different to know or is it... Yeah, just explore it. Try it. People will kindly say, oh, you shouldn't do it that way. Not all the features are available on it. It's not a super duper version. It's free. It's donated so we don't have all the gadgets on it. So, Mark, do you want to add something to that? So, if you need to submit an issue report, please review the how to report an issue instructions that are on Jenkins.io. If you have a bug report and it is inadequately described, you're doing yourself and the maintainers who might view your bug report a disservice. So, but that's the same that you would get in any use of any bug tracker, right? Write good bug reports. The permissions are generally pretty open on the Jenkins Chira and it's intentionally so. So, you can make comments anywhere. You can assign bugs to yourself at any time. You just need an account. Once you've logged in, you can assign things and you can work on them. Don't be shy about doing that and don't be shy about unassigning it if you decided, I don't want to work on that anymore. It's okay. Okay, thanks a lot. Thanks a lot, John. So, we'll slowly have to wrap up. So, I'm personally very happy to meet you and to start this journey together with all of you. Remember, I'm sorry to be first there. I will not answer requests to do one-on-one discussion. There is only one exception to that. I explain it another time. It's not the purpose here. So, I will not accept these. Ask your questions publicly so that everybody can learn from your question and you will learn from the questions that others are asking. The next step now is good luck and bon courage. I don't know how you say that in English, but be strong in building your Jenkins muscle and will organize another interactive synchronous meeting somewhere in the middle of January where we'll go more in details on the project ideas, give explanations and answer any questions on them. Stay tuned on Gitter and on the GSOC channel on Gitter and on Confluence on community.Jenkins.io and Twitter for announcement when this will happen. Thank you very much for your participation. Thank you very much for your interest, your questions. I'm thrilled. It's probably most of the org admins to see you here and to be part of that adventure. I'm looking forward to that. Thank you. So, we can end the call here, I believe. Yeah. Thanks, Jean-Marc. Thanks, everybody, for participating. Thank you. Bye-bye, everybody.


Hi, my name is Daryl Ford, Chief Information Officer here at Roger Williams University. Thank you for tuning in to our first video information technology newsletter. During this brief video, we'll feature three segments I'm sure you're enjoying. On the first segment, we'll talk with students about their experience with technology on campus. The second segment is our Roger Williams University Faculty Spotlight, where you'll hear about new and innovative ways faculty are using technology on campus. The third segment will feature a Roger Williams University staff member, whose contributions are making a real difference in the university community. For more information about technology services on campus, check out our new information technology website at it.rw.edu. Where you'll find information about services available to you as a student, faculty, or staff member, including information about the R-Cloud, computer support, wireless, and much more. Thank you for watching. I quite a bit put on the School of Engineering platforms and the Gobelli School of Business platforms. They've been extremely helpful for a lot of different applications that we might not have access to on our computers personally, so it's great to have that interface available. My technology experience has been good overall at Roger Williams. I've always been able to connect to the Wi-Fi wherever I am on campus, and the computer access in my classes, and then the library have been really beneficial to my time here. MediaTek is very efficient in fixing or any problem that I've gone there with. It has been very efficient. I thought that my hard drive was going to just completely die on me, and they ended up saving everything. I was really worried about my pictures from abroad being gone, and they ended up just saving everything, so I was really, really grateful. Technology is fantastic in the classroom. Whether I'm using it in terms of a hybrid class where I'm meeting with the students and then having them do stuff for me online, or if there are true online courses, I love the technology, especially in my field, because the technology allows a certain level of granularity that you really can't get without the technology. What do I mean by that? When I have a language course, if I only have 50 minutes or 90 minutes for a given class, I can only cover so much material, and if somebody has a question, I need typically to answer that question, and that kills time from doing other things I may want to do in the classroom. When I have the options of using video or using an online format, students can go into that video or into that online format and repeat the material, or they can look at other material more in depth. So the equipment that I use for teaching courses online or courses that are hybrid courses really varies every semester. It's evolutionary. Right now what I'm using is a program called Camtasia, and I'm also using that in conjunction with a piece of hardware called LiveScribe. So the Camtasia is great because it actually allows you to record screens on your computer and mix it with video. So I can put a camera on. Very often I get support right from IT for the cameras. They'll even come into the classroom and film the courses for me, and then I can add later into it a screen so that the students online can actually see me lecturing, and they can see the material that I'm lecturing about. The LiveScribe is actually a notebook where you write material into the notebook and it saves it as a PDF on your computer. So I can take notes or I can give class lectures and send them out to the students, whether they're in a class like a hybrid format or an online format. Moving forward with technology in the classroom, I want to see, and I'm always looking for ways of creating more interactivity between the students and the faculty, especially when they're sitting at their desk in their apartment or in their dorm in front of a computer. Right now we're doing a great job offering lectures to students that are online within video or having them respond back and forth with the faculty member, but what we don't have is that right at the moment interactivity that you do get in the classroom. And I think that is the area moving forward that I want to pursue. Customer service to me is walking into a situation with open ears, paying very close attention to the details, coming up with a solution, and applying that solution to the situation. It is our goal here to become more proactive in maintaining the technology on campus. And it's not like we don't like hearing from the university community, but we feel that the best customer service call is one that's never made.


Hey, make sure to keep the one meter distance. Remember to wash your hands often and please stay home if you're feeling unwell. Stand close to the bottle to recive and to back.


What is the best programming language to start if you want to start with Lightning Network? You know, George, that answer is actually pretty flexible because Lightning Network nodes have now been implemented in a number of different languages. The two most prominent are LND by the Lightning Labs company, which is implemented in Go. Go is a language created by Google. I've recently played a bit with Go. I did some very, very minor pull requests for LND. It's a fairly easy language to learn and it keeps you rather disciplined and is easy to collaborate with. So that's one language you could learn. Similarly, C Lightning is written in C and is, which is a very robust language, but is also a fairly low-level language, low-level meaning closer to the hardware on your computer, which makes it very efficient, but also a bit unforgiving when it comes to certain types of bugs. However, and this is where it gets really interesting, C Lightning has a series of plug-in capabilities that allow you to plug in directly to both the processing pipeline of the peer-to-peer network as well as the event-driven engine that allows you to process messages as they're going through the state machine and react to events on the Lightning network. The plugins can be written in Python and that makes it very, very easy to jump in with a language like Python, which is one of my favorite languages and probably the one I'm most comfortable with. So there are some suggestions there. You could start with writing some plugins for the C Lightning system in Python, or you could learn a bit of Go and read the source code of LND. Join me on Patreon.


Thank you guys for showing around and obviously that's not so many of you I Won't give a big speech. I won't tell you how good we are how Fancy we are how much? Positions we are what are all the nice things that you can have when you join our company Etc. Etc. Etc. I don't I mean at data centers Whatever it is that the we usually do when we do a recruiting speech and I Think it's most important for you to understand that today We are in a great shortage of engineers have data stuff data science Okay, it's the big thing today, but for you when you you go look for a job basically You won't have a problem finding one, right? We are like the new The new public sector in some in some sense I don't know about the other countries, but in France when you get in there you basically have a life a lifetime job and Tech is basically becoming what this this today so Instead what I like about this fact is that we have You don't go into an interview anymore, right when you when you go and we speak to someone we have This has set a sort of equity between us and and equity is good Because this is not anymore an interview. It's more like a matchmaking, right? It's just like a love affair in the sense You go on and you discuss with the people that you will see and some of them You will Bound you will bind pretty well some not that much and in the end It's good because You will spend most of your time with these people Be it physically or remotely I Don't think many of the other guys will say that they don't do remote as well So it's becoming a granted fact whether it's a bit in France or a bit in Your own country because and we are a French company, okay? It doesn't matter that that much in the end is What kind of relationship are we going to build and are you gonna build with us and? That's what you should look for actually, I think This is the equity that This shortage has brought us I hope it stays not the shortage obviously because it's a it has some bad effects as well and Just like recruiters were behaving like kings now we can see also recruitees behaving like princess So this is not always a good thing as well so just Be yourself and try to find out what kind of company you will Be able to remain yourself in Okay, when you join a company The first thing that we usually tend to do is to renounce because we have We think that we have to fit in Then we start renouncing some of the things that we stand for and this is not matchmaking You don't renounce yourself when you find your love partner for life, right? So at some point I'm not saying that you will spend your life in you in the company that you will choose maybe not but maybe the intention should be and when it is Then just try to be yourself and try to find out if the people in front of you are being themselves as well And if that matches and if the line of work that they do looks pretty good and interesting to you Go ahead then you have your principle then you have to talk about what is your salary blah blah Maybe it's the first thing that you is important for you and it's good for you Maybe it's not and maybe the recruiter will ask about you will ask you for DC at first Maybe not I don't know But this tells something about you and it tells something about the recruiter as well So it's not about I don't think it's in my opinion. That's not about What are all the fancy things that this company can can can offer to you I will have to get rid of this But instead please try to be Yourself and make it a matchmaking Okay, I think usually at the end of the session we have open questions. So This is still the case it will be interesting. So Put yourself in this position. Don't be a princess and we are not kings We are here to meet each other. You are not here to be interviewed So the way you are You are discussing with us or the people that you will meet tells a lot about Them as it tells about you That's pretty much it Okay, okay, so this is the actual photo of the booth we are over there We are French company based everywhere in the world blah remote blah and that's fine Okay Our core our core is data also we work with data and we make sense out of data so if this is something that Attracts you in some way you can come have a chat we have a fun quiz going on where you can win those fur Snakes and it's pretty fun. You have to team with each other this year every year We we improve the game. So it's the five fifth year that we are sponsoring Europe. I don't know. We are very pleased to do so. So Just come have a chat and see if you can match make. All right Thank you very much. I was hoping just to have our website Okay, there's no slides Okay, and can I just ask very quickly how many people had heard of smarkets before Europe, Python? Okay, of course Phil so Firstly, my name is Emma. I'm smarkets lead recruiter both myself and my colleague Phil have come from London where we're headquartered We're sponsoring Europe Python for the first time. Hopefully like long may that continue I really hope that we can get our brand awareness out there and actually meet some great people and that more people will have heard of us We're a relatively young company in many ways technically. We're 10 years old But the growth only really started about four years ago and things have really taken off since then I will explain what we do But I think it would be nice to give like a very quick kind of like suppose history ish of the company We were founded in London Which makes me really happy to work for a company where you're headquartered in in Europe Our founder is American. He's a former software engineer, and we were actually we were founded by two software engineers What we do is we basically provide an exchange where people can trade Against each other on the outcome of events We operate like a stock exchange yet. We're easy to use and we started thinking that by Operating in the betting industry we could change an industry which had traditionally ripped people off and not provided a lot of Transparency so up until recently we had the lowest commission on the market things are more competitive now Which is partly why we're here. We've built a great product, but now we're kind of focusing more on marketing I suppose in reverse to a lot of startups that look at marketing and kind of building their brand first We thought right we'll make our product and then we're now continuing to scale it and we're also launching a new product in the US so things are It's quite exciting at the moment because sports betting is being legalized in the US It's just gonna mean lots of growth for us. So we're building an office there And but we're mainly hiring in in Los Angeles and in London I think I'm not going to tell you too much from a deep technical perspective because my background is is in recruitment, but There are two things that makes but smart. It's a special business and one that is quite unconventional One of those things is that we've adopted a style of management, which is built on foundations of trust It's initially called teal. That was where we started now We've kind of evaluated what that means and as we've scaled we've had to scale what we mean by self-management But what it means to us is allowing people the freedom to make decisions that impact them and decisions that actually May not directly impact them. So an example is our town halls where our CEO Stand up and answer questions in front of the company and give updates on like our new product in LA And just any questions that people ask and there is a very kind of healthy debate and people are free to ask any types of questions There's no kind of fear of looking like I suppose upwards in the company and not feeling like you're allowed to To ask questions and be involved in things that do matter It also means that the teams get to Have the freedom to make a lot of decisions It doesn't mean that you're free to do anything you want You have to be responsible and work on the things that the company needs you to work on but it does mean that Compared to any company that I've worked for there. It's flatter in terms of organizational structure and it means that People come to work and they're accountable for themselves and I think that's the best way you can be So we give you the freedom to actually be creative And we give people time to contribute to things like open source obviously we've sent a bunch of our engineers here And we we want people to like invest in themselves And so we don't have a I suppose Specified time that you can go to conferences. We trust you to make decisions that are responsible The other thing is that we publish all of our salaries internally and In recruiting and I've been doing recruiting for the best part of 10 years It is often about who can negotiate the best and your bargaining power At markets that does constrain us in some ways because when we hire people that come from industries Which traditionally pay more because we are operating in the fintech space We do compete with with banks and we look for candidates that come from great companies And we often have to explain to people that we have a very fair process when it comes to pay We don't pay people over the odds because they're better at negotiating and some people we've lost a few candidates because they're like well You know, I'm not really interested in that But actually for me personally this is a step in the right direction for fair pay in all the ways that you can think about What fair fair pay means? We also have a process of salary review Which is that you put yourself forward for a salary review going back to the self-management thing That's you know, basically deems you to be responsible for what you've achieved So you and your team know what you've done and we don't have managers that can actually play favorites and give people You know a higher salary because they have a better relationship with a line manager So it's not you know These are all things that I think are in step in the right direction for for companies because to mention to go back To the point that that numberly made it is a two-way street And I think that two of the things that we've decided to do which are different kind of show that we we want it to be like that Like I mentioned, we are mainly hiring in London and LA We're looking for software engineers of all different levels of experience So markets is a great place to come at the start of your career because we have a very very high bar when it comes to hiring people from great companies and great academic backgrounds and then the more experience you are and More companies you've worked in you'll really feel like myself the lack of bureaucracy That you might get in other companies So there's there's a lot of things that we're working on like how we scale what self-management means As we grow because we're bigger than we've ever been before and we we're growing year on year So these are all interesting things to come and be a part of But we we hire smart people who we can drop into any team and who'll be successful As we grow we're hiring one or two more specialist people on the likes of data engineering infrastructure We do our own market making as well. So if you're interested in Those types of challenges relating to financial technology, but not working in a company where we have a finance culture Then you should definitely come and talk to us We did build an escape room for people to come and try we thought about doing something a bit different So for those of you hopefully some of you have participated in it We actually didn't get a go our employees all the slots went but do come and talk to us We've got some good swag and some nice people so you can kind of you can just see what we're about and if it's for you Hi, my name is Dmitri. I'm team leader of pie charm. I work for JetBrains. Do you know who knows about JetBrains? Like JetBrains is a company who makes tools for software developers. We are kind of focused on that area and The company is 18 years old already and we have a very big expertise in this field we make a lot of tools and We have an office in a nice city in Germany called Munich near the Bavarian Alps and What is working for JetBrains like we are the company who works Who makes products for software developers and our strengths is that like we Are software developers ourselves who make products for people like us So in JetBrains everybody calls like our say or right right code on the daily basis So we don't have managers who just like draw charts and Make meetings so everybody write code writes code and we have no bureaucracy at all. We are very flat Organization we have flexible hours We try to endorse Their a new project so we have 20% projects whatever position you have you can spend your time on contributed to open source or making whatever product you want and That is very appreciated and we have a lot of perks in the office and We attend a lot of conferences and we make internal constant conferences as well and Who we are looking for we are hiring Currently for Pitcharm team. We are looking for software developers Pitcharm is written in Java and Kotlin. So you will have to work with JVM, but if you don't know JVM Java Kotlin right now, but your your knowledge of Python is where it's very You know Python very good. So and you want to learn Kotlin or Java. So you're very welcome also, we are looking for people on Positions that are very close to development because as we are working with software developer even support engineers and key engineers They are actually write code and they have to understand the frameworks and a lot of technologies And we're looking for support engineers, for example if you Love this development the software if you love writing code, but you want to Talk to people more to solve different problems That is the position you might be interested in and if you also like software development But you want to learn a lot of technologies a lot of setups a lot of frameworks key engineers position for you because Working as a key engineer for Pitcharm means that you need to learn like everything You need to learn all the ways docker can be set up all the web frameworks that I that exist and so and so on If you want to know details, I won't talk a lot Here if you want to know details, please come to our booth and I will answer all the questions and explain Everything you like to learn. Thank you Presentation Thanks, yes, sorry for that Hello everybody, I am Abraham. I am sorry the recruiter for the R&D office in Paris So I will talk to you about that a dog. So what we do what we are basically Do you know what that a dog is? somebody knows You know and you know Okay, cool.  So we have an agent that collects all the traces matrix logs we provide dashboards and All the visualization so you can have a full view of all the stacks of your system You can set up other things. It's pretty customizable and Now we are growing pretty fast We are like 600 we double the size from last year. We are on the same trend for next year With a lot of technical challenges We manage like 40 minutes data points per second We manage several petabytes on the history So for that we we are hiring New people in every team actually So here are the the the positions we have mostly on the backhand side So Since we are in all of Brighton, so I guess a lot of you people use Brighton Actually, we Use Python more on the open source Side so on the APM side. So the application performance management monitoring To all the libraries we inject to Collect the traces on Python applications We use also Python For the agent the core agent that collect the metrics And for the other positions, it's mostly go Java for the back end Kafka Scala Spark For all the data engineering stuff And from the front end we use mostly react and D3 But since we are technology agnostic There is no no problem if you have no skills on on Technologies outside Python Because what we are looking for is people that have experience with large-scale Environments and Have the right mindset to to adapt quickly on other technologies. So That's what we are looking for now. Here are all the technologies we use So that's a lot So yeah, you can if you want some more information about us I think it's better to come to our booth. You can have a demo You can talk to myself or our engineers to have more information on On our stack and in the company What I want to add also about the culture of data dog is that We are growing pretty fast we are 600 now a 700 Sorry for that and We still keep this tight of mindset so give space for our engineers to to to to to take initiatives Make them feel have an impact to Because we have Distribute teams between Paris and New York. So the second R&D Center We have small feature teams Like five to six people and Pragmatisms also is really important for us. So trying to be the most efficient Taking the the right decision and putting aside all the accessory stuff So everybody has the same goal and work in a really collaborative way inside the R&D even outside the R&D so with recruitment with marketing and It's pretty great to have this kind of alignment because you You know that if you need help if you have an idea that is great that can bring value to the company processes tools You will always have the support To two of your management and of other teams. So yeah, that's why I wanted to add Thank you very much Next Hello guys, my name is here can adjust and I'm working for TV dot com in community team So that means I am not a recruiter. We left them at home this year of Europe, right? and Do you know what kivicom does? anybody Yeah, so we are online travel agency and we are All of flight ticket search engine So that means and we are unique in the way that we are combining all the flight tickets and all the airlines Which even those which don't cooperating with each other? So for example, we sir or in air So that means that if you would like to travel from Prague to Porto for example, the direct flight It will be really expensive But we've processed huge amount of data So we know that if you if you will travel first from Prague To Milan and then from Milan to Porto. It will be three times cheaper so that we that's what we are doing like trying to give you the best solution for your travel and for this we are using all huge amount of data we are processing it and That's why we need developers. We are but we are working like on 95% on Python and Only for some features we are using C++. So that means we of course hiring Python developers and We are based right now in Czech Republic in Bernou and Prague, but But also we have offices in Barcelona split Bratislava or right now. We opened also in Zagreb and I will be quick. Why should you visit our booth today? We prepared special Python quiz You can see the QR code over here and if you will solve it we we are organizing tonight Social event and party So if you will solve it, right? We will send you the invitation for the party. There will be free drinks and free food so feel free to join us and You can just talk with our guys who are working at givey.com also Like with me and we will tell you more about this and also you can win 300 euro voucher over there. So see you at our booth. Thanks So thank you everyone for attending. We know it's really difficult to compete with the other cool sessions So we appreciate it a lot. Thank you. So let me let me introduce Maria. We're talent manager My name is Ivan. I'm the VP of engineering. So we are on track and let's go to the point Okay, so first of all we just turned in we were receiving a lot of questions but there was like a question who was Consistently And so any guess about what could be the question technology one I don't know our company Can you guess someone? Oh? Yeah, so unexpectedly it's this one, right? Do you know what I mean?   Like okay, so everyone someone know what it is. Yeah So raise your hands. No Yeah, yeah, so yeah, basically it's this really useful gadget Okay, so Let me explain really quickly. What is our business? So basically our business is to make these people happy these people are the truck drivers, okay? So how we do this is by moving pallets From our shippers so our clients are just the companies. We need to move loads from one point to another So we have a platform and marketplace that make this much easier for shippers and the truck drivers this is basically our our business and We have two goals. So first of all make the freight transfer more efficient end-to-end process from the First activity to the last one and for sure build one of the best engineering and power teams in the world Okay, so regarding the team We are 120 people and we have 24 nationalities. We have a sponsorship program. So Of course, we are hiding so of those people the 40% of They are from tech and produce like basically we are a technological You know, this is like a cliché, but we are Product oriented company like for real like our engineers for example here. There is an example Dimitri Who is from? Modiva he is a backing engineer He's optimizing he's working on optimizing the roots and the first thing that he did is participating in the whole Product development process. So he was spending one day with one of our drivers and Of course, we celebrate Success, this is a picture like of last week. Congratulations guys for the payment it was a big project and We learned a Really awesome feature Who is gonna have a great impact? So we were celebrating that of course we celebrate me takes deliberate, you know, like we learn about everything here some Pictures of the reto that we have we're really a giant like we take the things that they are not working We iterate and we change things.  This is the picture from the last one and We were killing zombies in a VR and It was really fun. Okay. So why Madrid we are based in Madrid. I didn't see that a we have an awesome office in the city center and Why my date is because it's the new Tech hub It's a really nice city. There are a lot of the startups On track is one of them, but cavify We have a spot at home and It's really nice We have the best weather. That's why we are giving away glasses like no no rain You don't need to be a worry about like the weather is awesome the whole year and You know one thing that when it comes to Spain There are a lot of engineers who said, oh, yeah, but you know Salaries whatever no as we are having more startups. This is changing. So we don't pay peanuts We want to be on the best team. So we pay accordingly and In a spain people are nice very open. So you are not gonna feel like an outsider So if you visit my great and you can think us we will show we will show you around And you can visit our offices. Yeah, sorry. We are out of time. That's 10 seconds because I feel I need to at least put the text Stack so now we are here. So more or less All is well-known. So Python that Django do flask or whatever On the client side, we have native applications and react and reduce but and and all things like sensible tableau and digital ocean, but We want to this is just one step. We want to be there We are working hard to be in something like this. This is working progress So and for sure we are hiding especially back in a full stack engineer That's it. Thank you very much. Thank you Thanks for coming and this is Yelp and I'm getting a full stack engineer at Yelp and Let me tell you a little bit more about our company So our business is very simple. We want to connect people with great local businesses There is one important question that we want to solve guess what it is What's for dinner? So that's like one of the things that we started with you can look up a business profile. They're very useful information For example business hours, especially people's reviews, you know, whether they recommend this place or not videos and Photos for you to decide what's for dinner and that's a very important thing that I keep on thinking about So if you're not someone who is planning ahead and look at web You can also download our mobile app and it basically shows you a map and you can just find out What kind of places you want to go and for me Scottish is probably the thing because I've never been to Edinburgh before So that's a little bit more about our product and now let's talk about the traffic so we actually have a lot of people visiting our website and also mobile app every month and Some things that I want to highlight here is the impact that you will have at Yelp So every time you push code into production, these are the people that you're impacting And it's not just these people because in Hamburg. We're also working with business owner So you're also impacting the lives of business owners who are looking to find consumers to go to their restaurants or their businesses So that's the first thing I want to highlight at the same time is the amount of learning opportunities. So we have Over 500 developers now. We're getting a becoming a really big company here Just imagine the things that you can learn from the people all over all over the world We have offices in London in Hamburg in San Francisco If you want new know like more of a new tech stack or something There's always someone who's better at than you than at these kind of things So you can learn from them on these kind of things and another thing I want to highlight Is the responsibility So like I think you mentioned the term of like tag and not at no stick So here we also feel the same So if you're good enough to get a job and basically you can just learn everything at the job And basically I was entrusted with the responsibility to lead a front-end team to start a react project Even though before I didn't really have this experience So I'm really grateful to have the responsibility and the opportunity to learn at Yelp And we're about offices. We have a lovely office in Hamburg That's where I work and also London and we have different focuses So in Hamburg we focus more in development and product teams and in London It's more about operations infrastructure and security teams So specifically who are we looking for all of you in Hamburg? We want to focus on web So that's basically Python and JavaScript and also back end at Yelp We're a Python store. So there are plenty of opportunities and challenges for you to deal with imagine the data that we have and also university and graduates Interns product managers and data science in London we're looking for people and distributed systems as our a and also security and Just want to go through this list real quick what we offer. We have a really international and diverse environment Let me think about you know in our office. We have people from Russia from Hong Kong That's me from China and there are people from From France Italy to Jordan Egypt like it's really everywhere from the world in the US But don't worry if you're international because we'll help with visa sponsorship and also relocation We have regular hackathons. Unfortunately. We are missing one right now because we're at Euro Python So that's you know next time hopefully it's another week You can do really fun things from Indian cooking to building a new app video game I don't know there are a lot of things that people do and also learning groups that people can just present on things that they're passionate about for example, we had a learning group on skydiving on Serving other things you can think of flexible hours and meeting three Thursday that we're really at here too Our equity and pension plan that's competitive Transportation and wellness stipend so you really need that wellness stipend to get your gym because we also have free snacks All our drinks and free foods and I mean it So one thing that actually brings me to work every day at Yelp is the people So one thing that I think we do well is our open environment and also being inclusive That's one thing I'm really proud of working at Yelp and another thing is our great mentorship program Say if you're a new hire or maybe an intern coming in there will be a mentor that get assigned to you So this person is not only the person who is teaching you about technical stuff or walking you through the text This person also helps you integrate with the office environment helping you get settled in Hamburg Or also we have our relocation plan that can get you an apartment or if you're a little bit more ambitious a house in Hamburg or London so If you want to know more about what we work on on the technical side, we actually have four talks during Euro Python The first two I think it's already passed so you can look it up online There are two with type annotations with Stefan He's right here and also production alive saying your ML code with Laura's so looking forward to see you there These are our meat social media channels that you can look up and also will be at the booth So hope to see you there. Thank you Okay, thanks to everyone. I'm afraid we've actually ran out of time. So I'm not gonna have time for the Q&A That's mostly due to the technical issues at the beginning. So sorry about that But I encourage everyone to go and speak to the sponsors at their booths and See what they've got to offer ask your questions there and yeah, thanks everyone for sharing


Different management layers and relative performance are the two other issues that a designer can face while designing an incentive system for a given corporate firm. Top management has the capability of impacting share prices in the stock market directly, but unit managers and other business level managers cannot do this. We know that everyone in a corporate firm wants to acquire stock options, but pure of them are willing to stitch from cash bonuses to stock options. In fact, managers like to tie their performance measures with the object that is under their direct control and in exercising their performance, these managers can exceed the expectations. Also another problem in switching from cash bonuses to stock option is that manager cannot spare their human capital from the firm value, so they want to remain on cash bonuses. Middle level managers receive salary plus bonuses, but bonus can be an effective tool only if it is linked with the ranking. This means that the promotion is the differentiator that can be a tool for this purpose because through promotion there is a direct increase in cash salary of a manager. So far as the frontline managers are concerned, any incentive in their pay can only increase a productivity gain for themselves. As a conclusion, we can see that implies performance can be better linked with the value drivers under their own control. The next issue is the relevant performance. In this regard, two phenomena can be discussed regarding the responsibility of the managers. Second phenomena is that managers have full responsibility for all managerial actions they take in order to maximize the shareholders' wealth. This phenomena says that managers can carefully and cautiously take decisions to mitigate risk on the behalf of the owners. This means that managers have given the authority to take decisions to mitigate risk on the behalf of the shareholders. Therefore, managers cannot escape from any responsibility in this regard. The other phenomena says that as a manager is supposed to develop a comparative advantages in the industry in which the manager's firm is working, the manager let's say is not supposed to develop skills on financial hedging. Therefore, in this phenomena, the conclusion is that for certain risks, a manager cannot perform better. Therefore, he cannot be held fully responsible for the actions he takes. Some performance criteria may yield higher compensation in a depressed economy because if a manager performs well individually for his company, then the shareholders will see variations in the stock prices in the stock market. And as a result, this positive variation may enhance the value of the shareholders' wealth. And on the other hand, this relative performance criteria may not well in an economy that is going on prosperously. Finally, we can say that a firm's performance is easily measurable once some external factors are removed from this performance measure and those are the factors that are beyond the control of the management.


that got me a $500 sale versus a $100 sale or something like that we're saying did I make a sale or did I not make a sale success being defined in this case if we made the sale non-success if we did not if you're talking about a coin flipping situation then we will have heads or tails so the question is in a coin flipping situation did the success would be defined as either heads or tails whichever you want to choose non-success would be the other for the probability of quote success which is going to be represented by P is the same for each outcome so when you talk about a coin flipping situation then if it's a fair coin the probability of success 50% each coin flip if you're talking about a sales call situation or a coin that is not fair for example then you could the sales call you can have the probability of success for each call is usually much lower if you're especially if you're cold calling for sales you might only have like a 10% or even lower probability of making a sale on any particular call but that 10% were imagining would be constant for each of the calls so if these conditions are met then you could have a binomial type of distribution and we can use this equation we're not going to go into the equation in too much detail here because I don't want to be too intimidated by the equation because the idea would be that once the equation has been figured out to give us the curve of a binomial distribution then we can apply that if we find that that being applicable in our actual real-life situation then we can apply that using our excel functions and our excel graphs and if you wanted to type this in of course you can go to the insert and you can go into the equation and then you can make an ink equation we've seen in prior presentation so I won't do the whole thing again here but just know any Microsoft product you can kind of type in a mathematical equation this way and that way you can you can represent that equation in in excel so so so or any any Microsoft product so it's a kind of a new nice tool to have so let's go on over and approximate some data so we're going to have the number is going to be in and then we've got P is going to be the percent of of likelihood P is the same for each outcome which which is the the the probability of success for each outcome so let's imagine what we want to do now is plot out the binomial distribution and make a graph from it and see how the graph changes if we change the variables such as N and P as we do this it might be useful to envision a scenario so let's imagine that we have that sales call scenario where N represents the number of calls and P represents the probability of success success in this case being that we made a sale on the sales call failure being that we don't have a sale on the sales call so if I was to plot this out we're going to say that X is on the left so X is going to be zero through five notice that this sequence that we're putting into excel I could put a zero in a one and then use the fill handle a copy it down to five or just type in five but if we use this sequence function we could say equals sequence and then the number of rows is going to be this number five plus one because I actually want to add a zero and then comma comma to the starting point of zero the reason this sequence function is useful is because sometimes it's faster if you have a whole lot of columns and also you can change the number of rows automatically now by changing this end so if I change this end this will change automatically so that's kind of a useful tool sometimes to use within excel the pfx is going to be out