 Nearly 3ว Zhenlamon 2010 Dear möglich citizens, we respect the😏 the enforcement of our customers who are Close your independence weiterhin. 2017, in Crete, Greece, now joining us on stage, our CEO, our founder, Sid Sibrandi. Thanks everyone. It's amazing to see this room full of people. Thanks everyone for coming. I know that the isn't always easy, especially like to welcome all the significant others in the audience today. You're very welcome. Thanks for coming. Thanks for showing an interest in your partner. And for every activity that your partner can join, you can join too. So please join and contribute. Now you might be wondering why I'm looking like this. In 2012, when I started with GitLab, I wanted to promote GitLab. I wanted to make the presentation memorable. And like maybe it's becoming a theme right now. I'd like to do it at my own expense. I got into a lab code because GitLab. And I went on this and I did presentations. And a while ago, someone from Sidand.rb, the local Ruby Meetup came to me and said, you looked ridiculous. I also thought it was a ridiculous idea. And this still thinks I looked ridiculous. But now they were considering joining our company. Because we proved that we could come from behind and come from being based on our product and based on being open source, being inclusive. Now today, I'm going to talk about why we're having a summit. Dimitri is going to talk about how we got started. We'll look at where we've come from since graduating from XYC. We'll look at our challenges. And Eric is going to look at 2018. What our vision is for next year, 2020. What our vision is for a couple of years. Jop is going to do the 2018 slides. We're going to talk about our vision and mission together with Barbie. And another challenge. Now, why are we doing this? Why are we having this summit here? We're having this summit to get to know it outside of work. So we didn't come here to achieve something. I'll propose a challenge. But that's not why we're here. It's optional. You can joke if you want. You think it's fun. We're not here to have a lot of work talk. Most departments will not have any formal meetings. We're here to get to know each other. Because the whole year we're working together and we might see each other. It's not always easy. We're a direct company. You get a text message. You get a chat message. You get an issue comment. And it's not always easy to read. It might criticize your work. So we're here to get to know one another and to build a report outside of work. So if you're going to do as many people as you can, join that other table. Because that's why we're here. The first summit was in Serbia. And as you can see, it was a pretty exclusive affair. And we were very much joking, calling it a GitLab summit at the time. And we were joking like one day this thing is going to be big. And we never would imagine. Now, I'm going to call this a GitLab summit. But just as I told the customs officer that I was coming in town for a three-month conference, I was also coming in town for like a three-month summit. And we learned that three months is too long. Maybe it's okay to go to an office for three months. But it's a bit too long to live together for three months. But it created a bond like every hardship does. The next one was in Amsterdam. And I enjoyed this a lot. Jett said yesterday, Amsterdam was great because we were in the middle of the town. We all came together in a beautiful canal house. It was also pretty chaotic altogether in that house. We grew enormously. So the next one in Austin, it was amazing. It was amazing to see everyone together. There was a slight problem. We weren't all together. We were in multiple locations. So we figured out the formula in Mexico, in Cancun. It was amazing to be in the same all-inclusive resort. So everyone got to meet each other. We weren't constantly figuring out transportation and dinner. And it was very casual to get something to eat or drink together. Today we're here. And I'm very excited. And I hope you all have a great time. Welcome someone to the stage. I want to welcome the original author of GitLab, my co-founder and our CTO, Mitri, about how GitLab got started. Please welcome Mitri. Thank you, sis. Hi everyone. I'm going to tell you a story about early days of GitLab. I have a strong connection with the company and I wanted to share it with you. And I think the storytelling is the best way to do it. Okay, so let's go back in 2011. Back then I was working as a software developer in an outsourcing company. I got a backdoor degree in car engineering two years earlier. But I realized that I like software more than fixing cars. In the meantime, I was living in an old house near the countryside. It was a really small house. Thank you. But it was not my main problem. My main problem was code hosting tools. I used github.com for my open-source projects. And I felt like self-hosted tools are years behind. Less amount of features are unusable web interface. So, instead of doing code review online, I usually just downloaded it and did it locally. There was one co-worker who understood my pain. And his name is Valeriusizov. He is working with GitLab right now. So, we usually had a coffee break together and we talked about software development. And one day we had a conversation. We were wondering how hard can it be to actually build a web interface for Git repository management. And by the end of the conversation, we already knew we are going to build it. Because of our daily jobs, we couldn't spend much more time on it. So, we did development during evenings and weekends. Luckily, prototyping with Ruby on Rails is really fast. So, initial version was ready in a month. We decided to open-source it so other people can use it and modify according to their needs. I even made a static website for the project and shared it with Ruby community. In the end, it bring us good promotion and few contributors right in the first month. Still, it was more like a hobby. We didn't have any plans to build a company or something bigger out of it. We had our daily jobs that were totally fine. Valeri focused on his family and I just decided to stick with the project for a bit longer. To my surprise, we get more than 50 contributors in the first few months. Brightboard Costing Company provided me with free server for GitLab development. So, I installed GitLab there and I use it to develop GitLab. Yeah. So, I did release every 20 seconds of a month. The date was a random peak, but the month's shadow was on purpose. I didn't want contributors to wait too long before their contributions appears in a new version of GitLab. And monthly shadow is easy to remember. It's quite predictable. So, Project Grow, the company I worked for, started using GitLab. Some of my friends started using GitLab and their companies too. I got an email from Seed. He said that he admired the project and he sent me for merging his contribution really fast. He also said that he's going to build a software as a service business at gitlab.com based on GitLab. And he promised me more contributions in the future. So, I wish him good luck. I was really inspired by his honesty and the fact he actually contributed to GitLab. So, I didn't ask for money or anything. A few months later, I started another project, GitLab CI. The purpose of the project was to run tests for GitLab because I didn't like to stop Jenkins. So, by the end of 2012, I have two projects to maintain GitLab and GitLab CI. So, GitLab took a lot of time. The amount of users grow, the amount of contributions grow, the amount of issues grow. And with this daily job, it becomes a problem. And in order to focus full-time on GitLab, I need a sustainable income. So, I tried to make some money with GitLab. I started with donations and it didn't work well. I referred to it as an ice cream money. Yeah, probably in the best months, it was still less than $100. I tried to install and update GitLab for other users. And yeah, I tried for a bit and I stopped doing it. Instead, I focused on improving installation and update process for everyone. Yeah, so, I totally failed with my attempt to make money on GitLab. I gave up. And one day, I was really tired doing GitLab, doing my daily job. Open Twitter and wrote, I want to work on GitLab full-time. And Sid contacted me immediately. He said, amen, I'm going to pay your salary. And you work on GitLab full-time and help me with myprojectgitlab.com. I was really happy with it, really. But leaving my well-paid full-time job was a risky move. So, I asked him for an upfront payment. We didn't have any contracts. So, I asked him to wire money through Western Union. So, Sid comes to the Dutch Western Union office. And they're like, yeah, I'm going to wire money to this person in Ukraine. And they started asking him different questions. Like, do you really know this person? Are you sure that it's not some stranger from the Internet? And Sid, like, yeah, I know them. Like, we are friends. It's okay. Yeah. So, that's how I left my full-time job and started working on GitLab full-time. It was January 2013. It was a team of three people. I, Sid and Marin. But Sid and Marin were also busy working on other companies. So, they can earn money to pay me a salary. And also cover infrastructure costs. Still, we were doing much more than before. Like, we were shipping like crazy. Every release was much bigger than the previous one. Probably the only things that left is we never met in person. So, Sid decided to fix that. And there was a Rails conference in Poland. And it seems like a good opportunity to do this. So, I applied for Visa. I bought airline ticket. I did my first flight in my life. I arrived to Poland. We agreed to meet at the Airbnb place. My flight was at late evening. So, I arrived to the Airbnb place by midnight. And I was really surprised to see some other people living there. I get a call from Sid almost immediately. But, I could only hear hey, Dmitri, before I run out of money on my prepaid phone. Because of roaming. So, it was midnight. I'm in foreign city. I don't know local language. I don't have smartphone. I don't have internet. No Google Maps for me. No Uber, obviously. So, I was walking by empty dark street. Toward what's supposed to be a city center. When there was some lights. Luckily, I found a taxi here. The taxi driver didn't speak English. Neither he understand what hotel. So, I was looking for someone at the midnight on the empty street to translate what I want from taxi driver. I was lucky again. I found a young couple. They knew both English and Polish. So, they helped me communicate with the driver. Driver took me to the closest hotel. I ran to room. And first thing I did, I connected to the wi-fi. I get a bunch of messages from Sid and Maren. It appears to be that Airbnb address changed in the last minute. But, they forgot. Yeah, they didn't forgot. They actually send me a bunch of messages. But, I was in the airplane by that time. So, I didn't receive it. They give me a new address and said like yeah, come to us. And I was like no way, no. I'm not sure if I trust you guys. So, Maren and Karin took a taxi, drive to hotel. Karin was staying with the taxi driver. So, he doesn't leave. And, Maren come to my room and started convincing me like, pay me three, let's go. Yeah, it's a real scene. We're real people. We have a place to stay. We have beer, we have pizza. Yeah, so, in the end I agree. And, yeah, we drive to this Airbnb place. And by 1 am we finally met in person. Yeah, the rest of the trip was fine. But that was my experience meeting GitLab team first time. Time change, the year passed. GitLab project grow enormously. We tried to make money by doing consultancy and support. I think it didn't work really well. At some point we started enterprise edition as an addition to the support package. But really fast it becomes a main single point. And the product was good. I was really satisfied with it. So, we were quite surprised when we lost our first customer. It appears to be that our manager didn't even know about GitLab. So, didn't consider it as an option when he bought a software for the whole company. So, product was good, but it was not enough. There was a clear problem with awareness. And we need to fix it. Sitting an idea, applying to Y Combinator. And we did it. It was a deep own story. It's like so many things happened back there. But great thing is that we succeed. We get that customer back. We won much more of them. That's it. That's the story about early days of GitLab. Thank you. Thank you Dmitry. Thank you Dmitry. Yeah, and since Y Combinator a lot improved. The most important thing is we changed our logo. So, it's no longer nightmare inducing. Apparently, when you look at a very angry fox for eight hours or more a day, it gives you nightmares. So, we had two independent reports. And on Y Combinator demo day, the original contributor of the GitLab logo was in the audience. And Dmitry asked this person, hey, is it okay if we change it? And Ricardo Marr said, yes, it's okay. And by the way, I know someone who specialized in fox logos. We said, that's great, but we need a Tanuki logo. But we figured that out. Then we grew. We grew a lot. We grew from less than 10 at that time to almost 200 people now. And we're going to grow a lot more. We're going to open a lot of vacancies over the coming weeks if they're not open already. Because we have some pretty big ambitions for 2018. And we achieved our first goal in our sequence. We became the default Git hosting solution for the enterprise. Yes. We're in 2012. I was an idiot in a lab code. I'm still an idiot. I ditched a lab code and we are on the map. Another thing. And I'm really proud of the marketing team for pulling this together. Not only is GitLab CI the best product on the market, but it's now recognized as the best product on the market. Better than people that do pure play. So if people say they want best in class, you can say use GitLab because our stuff is best in class. We also got our challenges. So I want to highlight three of them. Our reliability is not where it needs to be. People desperately want to be a fan of us. And if they're running, if they're using GitLab.com, we're not making that very easy for them. They're disappointed. We let them down. We let them down now for about two years. So we got to turn this around. More and more companies are switching to.com. It's essential that we get this right. And to give some more detail about what's wrong and what we're going to do to fix it, I want to welcome to the stage our VP of Engineering, Eric, please give him a welcome. Thank you, Sid. And before we get started, I just want to say I'm really happy to be here. You've all been so generous with your time helping me on board. I'm excited to be meeting face to face and starting to jump into some of our hardest problems while we're here. So first, the current state as Sid said, the availability of GitLab.com is not where we want it to be. To quantify that, we're at about two nines. So 99.5. And that's not good enough for enterprises to build on us and to rely on us and integrate us into their workflows. It needs to be significantly better. So Sid has put this goal in front of us. Make GitLab.com ready for mission critical workflows. And to quantify that, I think it's three nines that where we need to be. And I picked this number because this is the SLA of our underlying infrastructure provider. So it's quite aggressive, but I think we can do it. And how we're going to get there is, and you'll hear me say this a lot as a reframe, it's a mixture of people, process, and technology always. And in the short term, we've got to be prepared to do things that don't scale. This is something that Paul Graham, who founded Y Combinator says all the time. What it means is that startups grow so fast, you typically have to focus heavily on automation. But in the short term, for the sake of the business, you have to be willing to get your hands a little bit dirty. So we're going to do some of that too. But you always have to have a plan to get yourself out of that mode. And so we'll have a long term plan to focus on automation. So we need tighter collaboration, specifically between certain teams. We need to find a way to allow the scale, the traffic on GitLab.com, which is several orders of magnitude larger than any other on-prem instance, to really influence and improve the features that we're shipping. And lastly, we need to fix our infrastructure issues and adopt some new technologies that sort of intersect with the product vision that you hear about soon. So reliability as it relates to the team, our people. Again, short term, all hands on deck. Get ready to get your target going to have impact in this quarter. And then some of the other solutions will start to have an impact into Q1. Long term, we need our production team to focus almost entirely on automation. And this graph on the side is what I think the ideal time split needs to be over the next several months. The amount of firefighting we need to do in solving issues needs to be about 15%. The amount of go forward features specifically Giddily about 25%. And we need to carve out 60% of the time to really focus on this issue and specifically a migration. We need the build and production teams to work. I know they're already working together. We need to make them work a lot closer together. What they're doing is so similar in character, even if the technologies are different. We want to really foster that communication and a lot more sharing of technology. And eventually we want our back end teams to be much more involved in shipping the code. We actually found that about 70% of our downtime minutes were as a result of application features. We've got great engineers. So that's not the issue. I think we've just separated them from the running of gilab.com and I want to break down that silo. And then process. So again, in the short term I don't want to be too prescriptive here. This is something we need to really talk a lot about and we can do that here. But BJ who just joined and leading our quality function is diving into this as we speak and he's going to generate a set of recommendations about what we can do in a brute force way in a manual way to make strides against this goal in this quarter. And then again, long term a big process that I'm a believer in is demoing frequently. So the first tenet of the agile manifesto is that working software is the best measure of progress. So I want to start demoing more. And you probably won't like this at first because when you've done everything right and you do a demo it feels like it was unnecessary. But I'm going to encourage you to do it and do it more often because more often than not you find problems that you weren't looking for and the more eyes we get on these things the better it's going to be. And so I promise you by the first or second project that we complete you'll fall in love with this process and you'll see the difference that I'm asking you to kind of trust me in the beginning. And then continuous delivery. So we have to adopt this philosophy for gilab.com meaning shipping small things and doing it very frequently, you know up to and including many times a day. And lastly, we have two new functional groups. Security is going to be led by Kathy who's I see right there in the audience. Please make an effort to get to know her while she's here and help her out and start to figure out how a re-department is going to collaborate with her and her team. And same with quality. We've got Vijay Gopinath, a former colleague of mine joining us as interim director of quality and same thing. Seek him out to the extent that you're passionate about willing to pitch in and do the manual that's going to be and then long term he's going to be on automation. And lastly, technology. So we're going to be migrating to Google that's going to be a big project. That's why we need to carve out 60% of the production team's time. The top capabilities we need. We need to build a foundation of the system that we want. And I think the most important things are multiple pristine environments and a continuous delivery pipeline that threads through them. Those are sort of the minimal things that we need as we move to GCP. These dictates some specific technologies. Specifically Docker containers are going to containerize everything in our application and we're going to Kubernetes. And luckily that we're also going to adopt a lot of smaller open source components. Helm is a good one and where open source can help us we'll build some custom tools and we'll probably do that and go and maybe we can even contribute some of that thing back to our product or back to the open source community as well. And then there's a question an open question of can we do more in this first iteration? Can we install a CDN? Can we do distributed tracing? I want to have those conversations and figure out what those things are going to be. But we're going to do this as kind of our smallest possible iteration launch it and then keep iterating towards our ideal infrastructure. So again I think this is a big challenge but it's a really exciting project. I think it has the potential to be a career defining project for those that get to work on it. Not many people can say they've worked on a consumer scale SaaS platform. And if we do it you know even our open source contributors will get to say that they've worked on a project that operates at that scale. So I think this is a a really fun and exciting challenge. I'm looking forward to talking to you over the next four or five days and diving into this. We'll keep it casual we'll focus on relationships for now but we'll try to make progress against some of this and if we're lucky maybe we can crystallize what we're going to do and be kicking it off in the next couple of weeks when we return home. So thanks. Thank you Eric. There's another problem. And our problem is that our Q4 forecast is below plan and that we need to do better. We did really well last quarter but we're now looking at a 28% miss. So we got to do everything we can to help our marketing and sales departments. And if you're not in marketing and sales you can help by creating leads. If you know what we're going to do if you know of an organization using GitLab that are not a customer yet tell them if you know of an organization using GitLab where there's another department tell them we got to ship the features that our customers want and that they want to pay for and there's a list right on the slide so those things need to ship on time and we got to work really hard to bring in orders from future quarters and many times that means an extra effort by our support team that means an extra effort by our product managers that needs an extra effort by our engineers to talk to those customers to be available to help sales and marketing get this done. The first thing I want to highlight is shipping GitLab Geo We want to ship GitLab Geo to general availability this year. GitLab Geo is the biggest want from our customers this is what they want this is what some are expected to have when they paid for enterprise edition premium and we got to make sure we give it to them and that it's really really good because this is something that that helps customers to care a lot about uptime we also want to use geo ourselves we want to move to Google Cloud Platform we want to use geo for it so it's an essential thing to get done and it's an essential thing to get done this year we'll even get into revenue recognition problems if we don't get this done so every hour every day counts to get this out the door I want to talk about where we're going next year the first thing will be the product vision done by yop we'll briefly briefly discuss our sales targets and we'll talk about some big bets that we're making and our product vision is an outcome of growing with some of our users this user said look I started to use GitLab and as I evolve more and more GitLab is there every step along the way and we want to keep up with our users and make everything easier and more fun to talk about that please welcome to the stage our VP of product yop all right I started recording my heart rate so after what you can ask me how nervous I was you can actually see it um this is how GitLab started we were just doing small things we had issues and we had a repository so you could start creating things but not much more you had to go to other tools and as you know that's that's not really our philosophy so what we did is we said last year we have a master plan we want any developer to be able to do whatever they need to do within GitLab run their tests look at how their code is working collaborate effectively so we said this in summer of last year and by December we delivered and we expanded everything GitLab does and we created the whole dev cycle anything a developer typically needs to do they can do it today in GitLab so this is exciting so where do we go from this well in 2018 GitLab will go beyond and will ship the complete DevOps site so what does it mean well so today you have developers and you have people that run operations and then there's this whole new flow of tools called DevOps and if you think about the tool the way I think about it is like duct tape the images you see here is really applicable right the only thing that it really covers is the overlap between dev and ops and with GitLab we have a very unique opportunity because we have the whole dev cycle so what if we connect the cluster what if we connect your infrastructure directly to GitLab what do you get you get complete DevOps so I'm going to talk you through what are the things that we're going to do how it's going to look and some of the features but first to give you an idea what this really means and how powerful this can be a short example imagine starting at a company maybe GitLab what do you do your first week you start onboarding and as a developer the next thing you have to do is you have to start setting up the development environment and it's not unheard that it takes a week two weeks I've even heard that it takes an entire internship just to set up a development environment that to make sure you can actually effectively come in the idea behind complete DevOps is that you enter your work you get your new laptop you open it you go to GitLab and there you have a full environment running you create your commit someone reviews it it gets deployed it gets tested and if you made a mistake it wasn't caught in code review it wasn't caught by CI we roll it back automatically so that means that on your first day in the first five minutes that you're at your new job you can deploy to production and you can do it with confidence and everyone around you can be confident that if you do screw things up GitLab will fix it for you and that is the idea behind putting all of the DevOps cycle inside of GitLab so when you ask organizations and developers what are the things that are important to you because this is what we should be thinking about right we build software to help organization ship software they call out a few things they want to automate more they want to do better at monitoring customer experience they want to do a better job of moving to the cloud and lastly they want to speed up cycle time and when you take all of these and this was something that was reported by Forester the same people that called us awesome in CI the most awesome when you think about these things and you start thinking like okay these are all important things you start to realize that there's an order to these things or in fact there's a relationship of a dependency between these things to reach one you need the other one so I'm going to talk you through this and then we'll get into features and how we're going to actually realize this and most fundamentally I want you to think about customer experience and not so much our users using our platform but why are people buying GitLab today why do they want to do this because they want to improve customer experience recently I had to sign up for a new bank what what were my criteria for looking at a new bank well for one it has to be stable and I have to be sure that my money is there but the next thing that I considered was how good is their online banking like can I do everything from my mobile phone are they able to you know when Apple comes up with a new cool payment system will they be able to support it and how do organizations do this they do this by focusing on the customer experience and the only way they can do that is by releasing by reducing their cycle time because the goal is constantly moving and to be able to stay up with the goal be that you know Apple releases something new some new Apple Pay system or anything else where your customers needs change you need to be able to respond to that and the only way to stay agile and to make sure that after the end of a sprint you're ready to go to a new goal or you're ready to adjust your goals is by reducing that cycle time and the only way to reduce your cycle time is to do less right you you always have to do the same things so you have to start doing less and the only way to do less is by automating and in the world of today just like Eric says how do we automate today that's by going cloud native so what we want to do with GitLab is we want to help our customers monitor their customer experience we want them to help adopt that whole DevOps lifecycle and we want to help them automate all of these steps and lastly and what we're going to do from today on over the whole next year is we want to help them become cloud native and use these tools to achieve everything above so let's have a look at what are the actual things that we're going to do and this is this is why I love my job because I love all these things and we're going to walk through the whole cycle so the whole cycle we start with planning right you have an idea you have to collaborate on a plan you have to make a plan together so how are you going to do that well I think we all realize how valuable it is to be able to work together in Google docs right that you see each other writing stuff you don't have to wait for someone else we talk about asynchronous working but when we are working synchronously it should work extremely well and we should be able to work together and not have to wait for the other person so one of the first things that we're going to do is we're going to work on real-time editing in issues and merge requests and next we're going to do something very cool so today everything in GitLab is very much around the idea of a single project they have one project one repository and there you have your issues and we started making ways of making this easier but we want anyone whether you are an individual developer or a high-level manager we want anyone to give access to give insight in what is happening in the organization and with portfolio management and epics being the first thing we'll give people access to that we'll allow people to look at projects from a higher level and see what is actually happening from a high level when are we shipping all these things what is next and we will roll those things up in roadmaps and the cool thing about this is we'll actually ship this before the end of the year so we're talking about the 2018 vision but this will be live this year let's talk about create so I started by saying GitLab was already doing this part we were already doing create we already had repositories but then I gave you the example of Sally that starts a new job and just has to log into GitLab how can we make that a reality now we always work in an iterative approach so the first step we have to do is we have to allow anyone to edit multiple files it sounds so simple we've been doing it on our desktop for ages but if you go into any web client you go into GitLab you can only modify one file at a time so already today we have a multi file editor it's still hidden behind a cookie but you could enable it but from there what we're going to do is we're going to build an actual full web IDE so that the next time you have to make a change to about.gitlab.com you can just do it here you don't have to spin up a local environment you don't have to upgrade your gems you don't have to do anything you go into GitLab you press edit on a file you'll have your console running on the bottom you'll have a preview window where your changes are and going from not making any changes to having a full development environment where you see your changes updated in real time will take you just a second and lastly we want to for anyone still working from the command line we want to make it easy for them to start something new so we'll allow you to create projects just by pushing no more having to go into GitLab you just push and there's your project all right let's talk about verify I mean when we're talking about verify we're thinking about the parts that are in CI and there's an infinite amount of things that we can do here but we're really stretching the bounds now because our CI is already so powerful so on the top here you see code quality this is something that we actually already released meaning that if the quality in your code changes GitLab tells you so that you can be sure that no matter the contribution that was made you don't have to go look for very specific mistakes that are often made and we all know with a very large diff with a very large merge request these are easy to mix but for very large organizations and in particular enterprises adding a new dependency that introduces some functionality also comes with it a new license and you want to be sure that whatever goes into your project actually meets the requirements that you have for your license so we'll actually start telling you what happens and what kind of license are added to your project and whether they meet your criteria so we do code quality right and we have CI we test your code we make sure your code quality is good you know you make sure that your tests run well we make sure that you don't have any licenses added what is left well there's still a few things left one performance and we know this all too well at GitLab having focused on performance for a very long time there's almost nothing more important to the quality of your product so we want to give people the power to do performance testing straight in the same place where they checked our code where you do your code reviews so that it's no longer the case that you have to think about going to test your changes or only doing it once in a while and testing hundreds of merge requests at the same time no for a single change you should be able to see what the impact on performance is and even better you should be able to see what the impact on security is you have to make sure that you're not introducing new security issues if there's anything that's more important today I don't know it and then lastly what you often see is when you have a big test suite then we experience this often with GitLab you get flaky tests tests that fail very often or you know that you're always struggling with so we'll help you fix those all right next part packaging and this is something that's very interesting if you're a ruby developer like myself you don't think about this very often but most of the enterprise today runs on java for instance runs on enormous maven repositories so the first thing that we'll do is we'll start supporting those so we'll have a binary repository in every project so that if you're using these kind of tools if you're using maven for instance or any of the other package managers you can do that straight from GitLab because that's where it's supposed to be and then if we start thinking about release I told you in the beginning that what I want to do is I want to hook up your cluster I want to hook up your infrastructure where you're deploying to GitLab and the moment we do this and we can do this through the power of Kubernetes and hard engineering work we can do very cool things we can show you how your changes are being rolled out and as I was telling you in the beginning when Sally deployed their code made the first merge and not everything was caught by CI and not everything was caught in code review GitLab will allow you to automatically roll back changes because maybe the error rate is too high or the performance degraded too much and we can do this I just think this is incredible like you have a change you don't you don't have to do anything anymore if you press the button and GitLab will take care of the rest I think it's super cool and I told you we want to hook up the cluster we want to hook up your infrastructure so we'll have first class clusters in GitLab so that if you have a project and you want to deploy it you just enter your information for instance from Google Cloud and there you go you now have a cluster connected to your project and if you have a cluster why not start monitoring it right you have to know what the status is I don't want you to ever leave GitLab again all right this is my favorite feature this is release trains it's uh I always try like it's really hard to explain this without going very much in detail but I'm going to give it one attempt you want to be able to test the results of your merge but the moment you do that you have to retest for every new commit that enters the target branch that's very problematic release train solves this problem by merging with the next merge request in line so that when they're all green they merge in subsequently that's the explanation I hope you understood it it's an incredibly cool feature basically what this allows organizations to do is allows them to move faster and more confidently wait less for a ci but be more confident about the results that they're actually testing against so then you have all these changes you have your whole cluster there why not give you more insight into it we know how much people like issue boards and they like moving cards between stages why don't we just do the same thing with changes if you have a particular change in staging and you want to see it in pre-production you should just be able to drag it in so that's what we'll do let's talk about configure if you have your application deployed now you have traffic coming in and we know this very well because of gitlab.com and it would have been great if we had gitlab at the time that we were starting to deploy gitlab.com because we could have just said hey let's scale this up and this is one of the things that we can do now with Kubernetes and then you know I said I never want you to leave gitlab again but we all know the truth most of us are spending 80% of our day in Slack so might as well make it easy to do all of this from chat so we'll make it possible that not only today you can say I want to deploy my staging environment to production but we want to give you much more power here and we want to make it much more easier to do these kind of things straight from chat so when you're talking about fun things and the new games that are coming out you can also quickly do a deploy to production all right and now monitor and I think this is one of those things that has so much potential the first thing is tracing so today you can monitor things from gitlab you can see how your application is performing but you don't actually know where things are slow the only thing you know is well it took four seconds to resolve an entire request but you don't know exactly where in those four seconds we were slow where which parts of it were fast and tracing allows you to do this today and there's a huge movement now part of it is for instance the project open tracing that builds upon this idea that allows you to basically track for instance an entire request so you instrument your application and you can see exactly what part is slow and what part is fast this is incredibly powerful when you want to speed up applications and we'll do it from within gitlab and then if you have all this monitoring and you have all this data coming in you shouldn't have to think about you know what what is not a good value what is a good value we will actually tell you when something looks strange so for instance if you suddenly have a huge peak in the time that it takes for a request to resolve we'll just alert you because it looks strange you don't have to set anything up and then if you go from a higher level because you now have your entire infrastructure connected to gitlab you can look from within gitlab and see what is the status of your entire entire organization all the projects that you have running you can even see the logs from within gitlab and now the coolest part I told you from the beginning I want you to start thinking about customer experience the reason why people by organizations adopt gitlab is because they want to reduce their cycle time and they want to reduce their cycle time because they want to be more responsive to the needs of their organization to the needs of their customers so if you do manage to reduce your cycle time how do you actually know that you did a good job and we will tell you in gitlab what we will do is will allow you to define business metrics and that means that if I make a merge request that changes the color of our website in that same merge request after having been checked for license security tests etc etc I will be able to see what the exact impact is on the sales of gitlab in the experience of our customers and that just based on my little change I think that's amazing I think that is the future of software just seeing that every little change that you do you're just a developer you come in you spend five minutes working on your first comment and you will immediately see the impact that you have on the business as a whole I think that's a very powerful idea so we hope and I believe that together by building gitlab and by including the full complete DevOps cycle our customers can achieve better customer satisfaction and a better customer experience thank you like I said thank you Yop I want to talk about sales for next year 2018 we want to keep up the pace with which we've been going so far and that is an amazing pace 90% of the startups would really like to have these kind of growth numbers we've we're on track to do really well again this year but we got to keep it up it's not let down and we see a lot of opportunity to keep growing but it will need we'll need to execute everything we'll need to do a great job in channel we'll need to do great job in customer success we'll need to attract new people we'll need to launch enterprise edition ultimate etc these are all things we have to do to get to those growth numbers I want to talk about our big bets and the definition for a big bet is something that gets us into a new market a new big market and we've identified four of them the two first funds will seem pretty familiar because they're part of our 2018 vision the first one is the security scan Dimitri is working on it right now and what we want to do is we want to leverage existing security tools for static application security testing and for dynamic application security testing and we'll do what GitLab is good at taking the best tools in the market and integrating them better because right now security is very frustrating to do it there's a disconnect between the security teams and the development teams and we can do both so we're going to make that integration better the second bet is integrated DevOps we're going to create a dedicated packaging and configuration team the packaging team will focus on making sure that there's an artifact repository so if you have a Java jar file that too can go into GitLab just like we have our container registry right now then there's two other bets and where the first two bets are things we'll definitely do these two other bets are more risky and things we might not do as we learn more about them every week we're going to see whether we'll do them because they're very ambitious and they're going to be a distraction and the question is how much of a distraction are they going to be can we limit that the first one is peer education we believe that everyone can contribute right now there's 20 million software developers in the world if you think that number is low I agree with you because I think there should be way more software developers but as most of you probably know it's pretty hard to become one and it's not enough to just do a course of three months or six months it takes a lot of time to become a software developer and most people don't have the privilege to spend three years without income doing that so we're going to try to remedy that we're going to try to create a financial space for those people to learn how to program the second one is complete bizops we're already doing complete devops and every company in the world is becoming a company so you need two components actually you need four you need kubernetes you need payroll you need devops with gitlab but you also need go to market you need to promote your offering and if you look at the marketing and sales landscape the problem is not that there is no tools to help you with that the problem is that there's 1500 tools to help you with that and it's up to every company in the world to figure out how to integrate them sounds familiar i think it does because it's exactly what the development the software the development life cycle looked like before we entered the scene so we're going to see if we can do the same thing for bizops brian flott joined us recently and he's going to create an open source offering to make sure you get complete data about how your company is doing in all divisions and we're going to try to act on that to automate more and more and more as we go along i want to switch gears and talk where we where we will be in 2020 since we graduated from YC our goal has been to IPO in 2020 and we're still on track as long as those revenue numbers keep growing like they're doing now we're on track to do that but we should strive for more and i was really inspired while volunteering at reels girls a couple of months ago it's not so much inspired i was ashamed i was ashamed of our industry because that morning a student came up to me and they she apologized for her windows laptop because she was told that in order to learn ruby it would have been much more convenient if she brought a macbook now i for the longest time couldn't afford a macbook so i worked on other machines all my life and i think it's ridiculous than in 2017 you can't learn to program if you don't have the right laptop which is like twice as expensive as everything else so we got to fix that and we got to fix that not only for people with windows laptops we got to fix that for people that have tablets so our web IDE will work on tablets and the next thing is obvious we got to fix it for people on mobile it doesn't make sense that you can program if you're on mobile beyond 2020 we have a bigger vision and mission and to kick that off i want to welcome to the states our chief culture officer barbie please give her a welcome thank you thank you very much it is amazing to be at my very first git lab summit it's super exciting so let me click here so what i love about git lab is not just that everyone can contribute but everyone can contribute from wherever they are we actually have an astounding i am told representation here of 38 countries that's huge not many companies can say that even if they're 10 times our size and yet here all of you are along with your significant others and we should all be super proud for that so welcome for me the way that we work was just as much of a decider to join git lab as what we do i love that what we do enable software developers from around the world to be functional to be effective and to be productive from wherever they are but i also love that i can do my job from wherever i want to be what's really awesome is that finally for the first time in my life i'm home when my kids come home from school my son's math scores have gone up 30% in the month i've been working here because i've actually been able to help with homework for the first time and it feels good and there's nothing that can replace the satisfaction of that so thank you for everyone who's built this company and the way they built it and i hope we can continue to scale this to be strong but that takes all of us to scale and work well together in a distributed environment and that's hard so i really want everybody's feedback here from slack from issues to help me help all of us do that in a way that will scale as git lab grows and part of that is having the best people and it only works if you have the best people so look real-time picture here that's you thank you urns for taking that photo and y'all at some point we're going to have to compare heart rates i think i'm tracking mine as well it's gone up about 10 beats per minute so part of being great and having great company is the talent we have and our product will only be as good as you are but we want to grow the product so we also need to grow the number of people in this room we also might need to grow the room that might be a little harder and part of that is going to be well let me put it this way you are all now officially talent scouts it is now your job to find your best co-worker and the best talent for git lab it's a hard job ask sasha ask jacy it's not easy but i believe that you can do it and for those of you who weren't aware you actually can make money by doing it and you can go to our ascento's page in our handbook but if you refer a candidate that gets hired to git lab details on the site you can actually make a thousand dollars better yet if you refer someone who's from an underrepresented group in tech you can make two thousand dollars and double your money and diversity is very important now we're luckier than most companies and that we are distributed so we inherently have diversity of national origin in terms of where everyone's from 38 countries and that's an amazing start but i also do believe we can do better and i want you to help us do better one of the things that i'm going to do to help us with this is not just the programs we do internally around making sure that every single person in this room feels respected and valued regardless of their gender their accent and their and the color of their skin quite frankly we all deserve to be respected and we're all equal in the work that we do and how we do it it shouldn't be based off what we look like or what we sound like it should be based on what we can do and our capabilities and the value we add that's important and that's key and that will only be reflected by the way that you treat your co-workers in the way that we treat each other but there's other sources to help grow our diversity at the company and one of those is college hiring now it's it's uh it's not easy you want to make sure you're getting the best and the brightest but we are going to start an internship program here at GitLab to help us bring in some more young talent and more diverse talent that's going to start small we're going to start with our first intern from Cal State, Florida and his name is Trevor Dutson and he'll be joining us when we get back from GitLab and he is going to help build out our internship program now the great thing about this is again you can help I know some of the wonderful schools and universities in America I do not know all the best schools and universities around the world so slack me twitter me but give me your advice give me your thoughts around what schools you think we should be targeting again with the idea that we want diverse candidates so we should be sourcing from schools that have diverse student body populations but I'm really excited about that and I think it'll be great for GitLab not just in the work that we can do with our interns but also in how it can change the look and feel of who is in this room so again I'm super excited to be here at GitLab I'm super excited to work with all of you and I hope you have a wonderful time here this week in Crete thank you thank you Barry there's a point of confusion that I want to address we're an open source project and that's not always easy on our sales people and sometimes our sales people say look I lost a deal to community edition and I can tell you that will keep happening will keep being an open source project and will keep putting out a great open source version of GitLab so don't worry about community edition that's the first line on the slide there you can lose deals to that you can lose deals to GitLab.com I just want this slide a few years from now to be ce GitLab.com and then a whole lot of nothing because we shouldn't lose deals to anything else I also want to say as we grow I want to say a few things and they're inspired by amazon these come from Jeff Bezos and he says it it's still day one and that means a couple of things we don't ship the process what we do needs to be in the interest of the user and the customer it's not about the process so if you followed the process but did something that wasn't in the interest of the user or the customer you did something wrong if you didn't follow the process but you did something in the interest of the user or the customer that is great and I'm going to give two examples if you decide to shake people's hand instead of fist bumping during the summit you're doing it wrong because you didn't think about that or if you thought about it you did it wrong you should talk to Paul's significant other Kathleen because he knows infectious diseases and we'll get sick we always get sick and we can prevent a percentage of that by fist bumping so please do that that's a that's a process it's not in the interest of the user or the customer to not listen there's also Eric here who also is not following process because I told everyone don't organize group meetings here but the bill team and the process engineering team are going to have meetings here they're going to have three meetings because there's a lot of work to do and there's a lot of change to me so he's going to use this summit to do that he didn't ask me and I think that's great because it shows that we're not stuck to process you don't need if you're doing the right thing it should be obvious that you can deviate from the process the second point is to embrace external trends it should be a tailwind for us and the biggest example of that is kubernetes kubernetes last summit we decided to go all in and it's going to be a major tailwind right now there's a lot of investing from us but it's going to be the next operating system so as the world moves from vms to hybrid cloud with kubernetes we're there if you look at hacker news at the blog post about days getting acquired the top five comments four people mentioned using a ci system all four of them using gitlab ci if we can keep that up we're going to become the default way to do development and operations and that's why we want to end up and the last point is about high velocity decision making we evolve as a company at the speed with which we take decisions and there's two parts to that it's about how many people you listen to and how many people need to concur with you at gitlab we choose two extremes we listen to a lot of people this is live streamed people can ask questions we work in open issue trackers everyone can chime in so you're going to hear a lot of opinions and that's great because they might change our mind now what we don't do is have to convince everyone we're not a consensus based company if you own it you make the decision you're accountable for it you do what you think is best after listening to everyone and we got to keep that up as companies grow some companies slow down some companies keep the high speed we want to be in the second category so keep making decisions don't wait, don't waffle many decisions are a two-way door if you make it and it's not right you can go back in that case just make the decision and go for it now i also want to talk about everyone can contribute it's our mission it's our slogan what does it mean it means contributing with GitLab so people can use GitLab to make awesome digital products and we're going to make that easy for them easy because GitLab is totally integrated and will guide you and it's easy and fun as the user said and and because GitLab is available for free with a free tier on gitlab.com and a great open source version that we lose some deals to people can contribute to GitLab the application we got close to 100 contributions every month and that is awesome because for us it will be really expensive to find out exactly what those people want we can double the size of the people the number of people in this room and our competitors have twice three times the number of people but they don't have a better product because it's super hard to understand the user so when the user contribute themselves that is that is gold that is very valuable and we'll never be able to replicate that and last but certainly not least contribute to GitLab the company and I want to call out for example Greg Barbie's significant daughter and he's been here for a couple of days and he helped with a lot of things he fought with us I learned things from him and I hope that other significant others feel that liberty to pitch in but it's not just significant others it's a whole wider community we have an open handbook and people can contribute to that and change our processes so everyone if you just join the thing that makes me most happy is to get a merch request assigned from you and you give me a ping on chat hey I made this change what do you think that is awesome that makes me very happy because it's not just building the product it's also building a company where people want to work and where people experience the sense of progress now the last thing I want to highlight is our sequence and the sequence has been the same since we left YC we wanted to become the most popular on-premises software development lifecycle solution we did that we got to two thirds now we're going to get to most revenue and we're coming from behind but we're coming at a great speed and we got to keep up that speed of revenue go after that we'll do private repos on SaaS and after that we'll do public repos on SaaS and we won't stop there but we want to make the most popular collaboration tool period for any industry not just code but right now we're at number two so we got to focus on that now I want to end with a challenge and I really enjoyed the challenge last year I said look if you can make idea to production with Google container engine I'll do the sit shuffle from IZH 2 thanks chat for that idea and I got lots of compliments so although people laugh really hard I felt I did a good job I want to up the stakes this year a bit it's like a Kickstarter campaign the more you raise the better it gets there's three parts to it the first one is to replicate a backup of .com with Geo before the end of the week so we got to up our Geo game and do more replication faster the second one is to ship an alpha version of our web IDE we got the multi file editor in there there's a web editor already in GitLab we need a preview screen and then we're there and the third thing is a challenge for marketing and sales the thing is to record 10 objects in handling training videos so that's a video of two people sitting together where one person has an objection and the other person addresses it online in YouTube and on our course list now the reward depends on how many things are achieved is there just one thing if there's no things I won't do a thing if there's one thing I'm a programmer we started zero if there's one thing me and Karen will sing the GitLab song together and we still got to make that so join the user generated content session for that if you want to contribute the second one is me as a backup dancer with Karen singing the song and I'm pretty solid on my backup dancing skills so that's going to be good the last one I rather not end up because I got to sing alone while dancing and that's going to be a really tough one so if someone sabotaging the network to prevent that replication it's not me so these are the challenge this is the challenge should you choose to accept it it's voluntary no pressure it was fun last last year so last time so I wanted to offer a new one now that was the presentation thank you very much for listening and we'd love to get some questions there will be a mic lined up there so you can get out the row here walk to there undisturbed and I want to invite all the other speakers on stage thank you very much for your attention is this on it is of the four big ideas that you proposed or the the moonshot which one are you the most optimistic about and excited about the question yo you heard the question it's different so I'm very optimistic about security I think that's a thing we can do Dimitri is already doing it I explained to someone in the industry what we're going to do and what timeframe I said we're going to have dynamic application security testing by integrating open vass probably by the end of the year if not otherwise in january and that person was like looking at me like I was just making stuff up like couldn't believe the speed so that person went home totally puzzled and the speed at which we can do this is is amazing and the market is really big and I'm hearing from all our sales people from from other people that this is something customers need and what we're going to get to next year is that you can prevent untested code from going out Google recently released an open source application where you can store the results and then Kubernetes will prevent you from ever deploying code that wasn't security tested I think that's awesome I think that's what customers want if you don't think so walk to the microphone or hit me up later but I think that's it's it's something we can do on a short time frame there's a lot of value in it now what I'm excited about I'm excited about all four ideas but a special place in my heart is for the peer education not because it's easy it's good by far I think the hardest thing to do but I think it could have the biggest impact on people's lives so that's why I'm very excited about it thanks for the question Sarah so I have a question about diversity there's a lot of talk about increasing diversity at GitHub and I think we are very diverse but it's not enough just to bring diverse people in there has to be an understanding of what that means culturally so what are your plans in terms of helping to train people of unconscious bias and the kinds of communications that can happen that make diverse people leave companies once they come in so I believe that we've already done some work that predates me on this but this week we also the team up here and some people in the room did our e-team meeting this week and one of the first things that we did was have me take the entire team through a diversity inclusiveness training which included implicit bias training and so all your executives have gone through an implicit bias training now where we had about I would say three hours of discussion and training about diversity and inclusiveness and I do think that it starts with the I DNI starts with the I inclusiveness is the most important thing to being diverse it doesn't matter if you hire a lot of people from a lot of different backgrounds if they don't feel comfortable and respected they will leave and they will not refer their friends and their family to the company so that was the first step the challenge at GitLab is greater than companies with the workforce concentrated in one location that diversity means the same thing for everybody the reality is here at GitLab diversity will not mean the same thing to all of us we are all from different countries and the make-ups of our countries are different and so our definition of diversity will be different and I think we have to understand and respect that as well so I think that trying to get to a common understanding about what it means it's going to be important and so I will work and try to focus on that another recommendation I have and maybe we'll do something about this at the next summit or you can do it on your own the culture map by Aaron Myers is actually a very good book to read to understand different cultures and how that affects decision making communication trust and relationship building and it was really interesting for me to read that book and to understand where I fall on the continuum and various different dynamics that are affected impacted by culture and where you're from and what's interesting and fun to do and I've done before at previous companies is that everybody reads that book they all take the test for themselves if you buy the book you also get a link that you can evaluate it's interesting if you're from America and you realize you're actually more like people from Germany or you can see where you fall in those generalizations but what's also interesting is you can then take the test again and evaluate your company and you can say where do we think GitLab is and then we can get together and compare that so maybe it's one of the breakouts that we have at a future summit where we can actually explore that it's not a point in time thing it's never something that I will say we're done so I and I also won't say we're just starting it because I do believe the team started it before me but we will continue to work on it and we will put some increased focus on it and like all things I appreciate everyone's input here on it as well but the first step will be making sure what I would love to do is that everybody in this room feels empowered but not just empowered responsible for standing up when they see something so if there is if any of your colleagues say or do anything that you think could be interpreted as disrespectful or discriminatory even if it's not directed towards you you need to speak up very often the person that is experiencing it is the person that's most afraid to speak up so if you see something say something and that's really critical to starting this off hey my name is klemmit and I got a kind of follow up questions on the diversity thing so one of our values or sub values is being direct have we considered how potentially that may and I like that value but have we considered how that value may hurt some diversity so like for example some cultures may not be as direct as certain cultures and maybe for polite reasons or other reasons so wouldn't that potentially affect our diversity and candidates since we screen candidates based on our values as well that is a really really good question and it's no surprise that I came from Netflix and that was one of the biggest challenges that Netflix had because Netflix has also a very direct culture and all our employees in the beginning were in the US but when Netflix expanded to having employees outside to be honest in Japan and Singapore and some other countries that are traditionally less direct it it it did make them have to think about what direct means so and I believe that it's not about other cultures not being direct but direct looks different so direct doesn't look different in every country however we also can still hire for it and teach for it so if there is someone from a culture that is not used to being direct who has been taught through their life that you don't disagree with your manager then as a manager it's your responsibility to farm for descent to try to get people to disagree with you to try to bring out those opinions and recognize and and diagnose for who needs to be encouraged more and who does it just find on their own so we can help each other through this and one way you help people through that is not reacting defensively and not making people feel punished when they are direct or say something you didn't like so that's something that we all have to work on as well but we also have to appreciate that direct will look different and so let's not tell ourselves that wow that person isn't a culture fit let's tell ourselves let me figure out how they communicate and what direct means for them and appreciate that and that's one of the things that the culture map is good at one of the dimensions that they that they evaluate and talk about is what they call high context versus low context and basically that's which cultures you have to read through the lines more and which cultures are more direct and so it also improves that understanding but you're right it can turn off certain people if they're not type A or they're not super outgoing and it might make them feel I wouldn't be a fit here so it's our job to counteract that and take active steps not to however it doesn't mean that we should be okay with people who talk behind other people's backs people who are political people who manipulate that's also not direct but that's not necessarily culturally aligned that's a behavior that we also should not accept so it's a balance and I think together we can if we continue talking about it I love that we're getting questions around this because it means it's important to you and it should be and that really makes me happy and so if together we continue to talk about it that's important but we have to be able to talk about it if we feel like we can't ask the questions then we're not going to learn new perspectives and get new ideas and ways of looking at things and not understand each other better so it's it's wonderful we're having this dialogue can people please make a line so thanks yeah I'd like to know how do I become a developer so the the question was how do you become a developer I think I would just start coding just dive in and there's there's so many good open source projects there's so many resources out there I think that's a really important skill all engineers you know we we we're never solving the same problem twice it's always something new so you have to be someone who's excited by unknowns that's sort of innate to to what engineers and what developers do so so just just jump in and then you know everybody that's self taught also tends to have holes in their in their skill set and sometimes it's the computer sciencey things like big o notation so also take advantage of the teaching that's available out there whether it's the the programs or a university course or something like that to make sure that you're complete and and you know learn from your from your peers I mean we've got a culture of anyone can submit a murder request directly to our CEO for a corporate website you know start start doing that and start with markdown and then build your way up into into the rest of the code base and into the javascript and and it should be very easy to do and I think we've got such a such a open and inclusive culture I don't think you know you're gonna lack for people that want to help you out and teach you jump in the questions channel on slack and ask questions I think you're gonna be overwhelmed by the response I want to add to that as you can see in our expense policy if you want to follow a course on Code Academy or Udemy that you can expense that so whatever your role is if you're going to learn how to code I strongly recommend that especially Udemy where you get a teacher that will refue your work and Abby your comment inspired me and I hope that Karen's okay with this I can locate her but Karen and me are gonna organize a session that will be based on the real skills content but everyone can contribute everyone can participate even if you don't consider yourself a girl so please come up to Karen she's located there near the camera and we can organize a time to do this together thanks Karen so one thing that I really like about github is also thank you culture so I want to thank you first of all maybe you can take the mic out of the stand first of all I really want to thank you for the great keynote because this is also part of our culture and I really like that filling us in on all the different topics I'm coming with two different questions so the first question is you can ask one question then you have to get back yeah I will queue back so I will take the first one so dogfooding what is our actual plan to dogfood our product vision into our development cycle so are we going for continuous delivery are we going for all the different great tools that we are building where everyone was popping basically their eye and saying yes we want it when are we going to feed that into our cycle yeah so the question is are we going to dogfood all these great features that y'all talked about and the answer is yes absolutely it's going to be a very tight feedback loop there'll be cases where the product is head of what we've implemented there'll be cases where as I mentioned we're going to create some custom tools and we want to get that back into our on-prem product and our open source project so absolutely and again the great thing about this is that when we do it we'll have a great story to tell people a great showcase that if you adopt these features we can tell them we've used it on gilab.com and we're doing orders of magnitude more traffic than perhaps they are which will make them feel like you know they can scale with us and and vice versa thanks hi i'm kashal us being a remote only company we are right now at around 200 team members so in the future as we scale up what are the problems that you foresee now and what is the plan to tackle the problem of scaling as a company there's going to be lots of problems and we're going to iterate our way out of that i think something scaled beyond what we ever thought was possible when we were doing our first team calls it was seven people and we were nervous because the company could never grow beyond 15 people because that was the number you could have in one google hangout so sometimes the solution comes but it's a great example the team call right now it's not scaling we got about 80 people in the call we used to have two first participation right now it's it's lower than half so we're gonna we're gonna mix that up barbie's looking into that what to do there and we'll keep encountering things like that we might go out of these rooms things like that i think one one's one problem and one solution at a time and so far i think we've done a great job and i think that the amazing thing is that because we write down how we work and what our culture is and what our values is those wordings get stronger and more people read them and more people that that join the company now have actually read them before they join and they subscribe to it so that's encouraging to me is that where all other cultures that are implicit they get diluted like a telephone game ours gets stronger over time and i think that is a superpower and we're gonna we're gonna we're gonna see more of that as as we grow barbie you want to add to that well i hope you're right i do think that is one of the challenges with growing is making sure it remains a superpower i think that quite often when we grow we take our eye off the ball in terms of our values in our culture and i'm gonna hope that GitLab is not one of the companies that falls falls victim to that but that's again not our job it's our job and so we all need to make sure that when we're referring candidates or candidates that believe in our values when we're interviewing that we're interviewing and hiring for people who believe in our values we promote based on our values those are all really critical you know you have some of the really traditional stuff we're lucky we're not the company that has to say oh no we need to build a new multi-billion dollar building to fit everyone so that's that's good but there are other challenges like the summit it'll get more complicated and complex as we get more people but that doesn't mean it will get worse it can very well get better but it takes focus we can't just assume every will grow correctly we have to actually deliberate on it and be thoughtful about it and there'll be some hiccups but like said we'll iterate so i love that abbey came up here sorry my voice is really raspy the abbey came up here and asked about coding which kind of brings it back to diversity there's a ton of people out there who are finding unique ways to learn how to code in different channels and although i do like like that you're starting with college students for your diversity internship program but are you planning on tapping into other like markets or areas for sound talent absolutely and and again it's not all about what ideas i have so if you have other ideas feel free to share them one of the things that i think is a is a strong power of git labs way of working is the veteran community so and the and the veteran significant others community i i britney is an example of this but i know many people who have a spouse who's in the military and it inhibits their ability to work either because the base is in a location that's not a a focal point for industry or because they have to move move often and so they have to switch jobs and it's hard to develop a career so i think that's an area we can tap into i also think that when i say internship it doesn't mean we have to make them all formal if if we if we have someone who's learning from a unique source of learning they can still be an intern it doesn't have to be a traditional buttoned up university we're not planning to do unpaid internships i don't believe in that so we can do internships pretty much with the wide variety of groups and and be okay in addition to that i would say that we i don't care about what school you go to if i if i want to be completely honest i think i don't know how to say it in a nice way but i think it's largely irrelevant i think there's some really amazing people who go to some really amazing schools and i think there's some really amazing people who don't and i don't want to be that company that values people based off the pedigree of the university they attended so i i hope that we don't become that at gitlab and i and i don't want the internship to drive us in that direction i want to yes i want to formulate that a bit stronger i don't care whether you went to school and we have a lot of people at gitlab that i didn't start or didn't finish their final education and i want to second what barbie said the internship can be informal is colon here in the room can you stand up so colon was i think the most dedicated person just keep standing up this is your moment 50 minutes of fame man most dedicated person ever he absolutely didn't qualify as a support engineer but his his passion was overwhelming so when he heard we did a bad job scheduling so he talked to me about one half two weeks after he talked to the last person at gitlab and they told him what the problem was which kills he didn't have so he said look i took courses on that and i was like wow that's amazing if it's true you know me by now i'm a trust but verified guy so i said okay that's great can you please share your desktop and show me show me your credentials that like show me the courses and how much time you invested and colon showed that and said well this is amazing we're gonna we're gonna figure something out for you so we made him an intern he's by no means an intern he is our only person in campoja so far so you had an internship from campoja not related to university and colon you did great i'm very proud that day you got the junior position at gitlab thanks so much son and it was great hearing all the things that we're going to be doing next year as a sales part of the organization it's great we're excited we're going to take over the world but yes it would be great to hear more about the vision that you have on the sales and marketing side for the team to share with them as well yep on the sales and marketing side there's there's a couple of things first top of mind the cro search that's happening right now they're using the time that we have at the summit to get the first candidate so i'm i'm excited about finding a great new cro i think it's it's going to be i think we got to augment sales more so we got amazing account executives but we got to back them up with amazing collateral and william has been doing an amazing job just in his first week and now a second week of of adding to that but we need two possibly three more people in that department to give ourselves people the material they need ourselves people need to have the training you you deserve so hence the challenge like we we got to get better at training you how to talk about good land we got to get better in customer success so christen has done a great job of of helping with our solution architects which kind of function like pre-sales engineers but we got to also do more for people that are with us and identify the ones where is an opportunity so we got to get better data on that we got to know what we what we have to do there another thing is professional services if people sign an order to get GitLab they don't want GitLab they want a better customer experience and GitLab is a way to get there but it's not a complete story we just give them the licenses they don't want that they do want help they want help with the migration they want help with how they need to restructure their process if they switch from legacy tooling like Atlassian that doesn't work together and they switch to GitLab and they keep doing all the things they were doing in that old tooling they're not getting the benefits they need to they need to also make a change in how they work we're not doing the job we should be doing and helping them with that so christen has already started that but professional services so you be so i'm sidd i'm the CEO of GitLab and i'm going to discuss the different modes of filming we'll have during the summit we'll be live streaming every every day from nine o'clock in the morning till nine o'clock in the evening i will want to keep the stream live but that means we have to mix up what we do to keep it interesting for the viewers and also to give the mobile camera team a break every now and then so the first of the nine modes will be the keynote mode during this there will be a presentation and afterwards a Q&A we'll film that and it will look very similar to a conference where you see the speaker you'll see the slides and during Q&A we'll show both the speaker and the member of the audience asking questions the second mode will be the chat mode i'm very excited about this this is where we interact with our viewers our live stream will be broadcasted on youtube and next to the live stream will be a chat stream now every time we're in chat mode there will be two people from GitLab two volunteers being a moderator and a facilitator the moderator will be hands down in the chat stream so they'll be on the laptop on wi-fi engaging with the audience in the chat now every time there's a great suggestion made in the chat they'll inform the facilitator the facilitator is closer to the camera crew and they will try to execute whatever was the suggestion was that made sense so for example it can be like hey, hand down the vp of engineering of GitLab and ask them about this specific problem or ask one of the people of Spheres and This or That or maybe do something interesting so it's a bit dependent on the creativity of the audience and as long as it's it's appropriate and good fun we'll try to go along with it here's our train it totally represents of a candy this is not for people so just a candy people want your choice of candy for me thank you this is our own I know it doesn't pay when it's wake up it says video this is taken to the video it says still wake up yeah me? jill I have gum I have gum you do not have any but we are for my life and you just hold on yeah yeah we're gonna see see see what we'll do ** වන් person වා වඳු ඛන් සිරන් වොික් ලා ප ඳිලා එකකියැින් එකක Lordm essay ගැ because before this i got Library emoji side effects. 【 එකක් එකක් වෙස 4 වික් පඕ් පා ව�SHеленු බහා වන්. విదికిభిల్కud వినామెయాయానీ నామెగఎలాయారుకరితlait�ిక conception Neo వివిచా౰ికరిసుకానితూపటెరో౛ చి఼ిర్హిస్చె paj�ట్లివీ between AUTV and విక�大哥 ...वलँ transparency..  chimney pad house buesthing ? सालित ब homeland  को ब वयी.... जो अख ल contrيع... कह् мнन ढे how feminine. और ई você आँ  शमर सऱब लग वत खलग णाजन कर तहा�ji decrere ry jo n by saalikechaalne. koh man air lagu mein, dule aw ko kan nga hrien. ැනෟ෸ූ් මිතාද්ි ලිති්දි එ� classical හව ලෙයි상,ගණුරවේ යසණුකය් මීඩ්මයකය් වකෙරස澤්ප හව,ධි මූ්ඪක්තු මීම�arpගකරු Oh, yeah, there's another bell. There's two bells. There's another bell. But this is the duplicate piece, and there's the හ හ ස හ හ කා එයයඹා එයයස්ති මින්ෙවඩ්වකම මුන්ත්වා නරීුවමක් ලෙමේ්වලෙලිත්වත්ක්න්න්වක්න්නූයිත්න්න්නෙන්න්න්නි ම්න්නි මෙමේ්නිත්න් බිකාරිගමඩ්නි විතුක්රක් තාලයක්නික, ලිසුවක් වහක්නි, අතා මෙගට්න්නා ප්වලින්න්නාවහික්නාවහක්නාක්නේ්පික්නිවහිකක්නිවහික්නාවහක්� ensitive challenge ARIN jiang now වද්කෙති මේු එෂඅු මූ්ක෯යිකිරදයු ලෙලේ්ර්කියියිලු, líගට මඹිකු ති෻කිරඒ කරාපාලාති? ඖහෝලට, අේ දිමකකියිාේ мои Hồng Hieso ḍᶜḍᴇ ḍᶜḍᵉ ḍᵏᶜᵃ ḍᵁᵉᶜᵉᵃ ḍᵎᶜᵇᴇᴇ ḍᵉᶜᵃ ḍᵃᵃᵉᵒᶉᵃᶜᵉ ḍᶜᵃᵉᶜᶜᵃᶜᵃ Ḑᶜᶜ�ᵃᵃᵃᵃᵃ Ḝᵉᶜᵃ Ḃᶜᵃᵃᶉᵃᵃᶜᵃ ḍᶜᵃᵃᶜ� විෆ්ය මෙිහා අවවහොස්ල එක් මොව්න පිසුම ක් අවහගස්න එක්හා අවහීමට්න. කෝජධීවහැනය කෝුවින්න. ව කි අරය වහාලයයයය මූිව ලමති අවශප්ගට්වඤ acronන්වතාන්ටි දනෙින් කිට්ක් මබ්. 김 ưỗ භනා මපාග්ලිද පවනාrust පිනාඳූ් this is my Cort major වලසෙතුවවඩු ලඳම දිල් විසිඳීමය යද සැනා පෙක්venge� පානගීටමනාන ලඳ කර මේ පොනා යර් වලිර ඍකමය ක�마ග අය, ගේ් ම පිදා lure† ? entrenrivere ආය් ඛනාදයරඦ, අයේ් ඔබතට්භ දතාය ානඟත්ය කර Foreign අය්ශට ඉවපක, නුයටය. අප competitorsmain එබතසධareth අප ඀ත පළමුමී මක්예 Allāh කිවෙග්2 स්ායු ඘ාපස රිදිරු මීශඅ එහ ම gesprochen අප Lah් ඇ දලය, දපිමක, දලයරයයයන ග ඛතතු ලපදැ මේය කусаන්.ු ඀ාමි දණෝුල වු strengths ඇලෙතියය කසින නිනපිදැ මෙවමියක. බානි, අපි,ouve is෗ර, ද මශන්. We only did one challenge. Yeah. We got points for drinking, which is like I never get points for drinking. The minimum was 241. How? What? 62. 62, and... 638, 128, 138. No, it's not here. 241, it's, it's a little, I see.  butts go  Lichter 2  sampel 2  sampel 2  nadzieó 2  exclud                                                                                                                                                                                                           ව දිරවා ඨුහ වබ්ඨා පිනෝ ආබුණයඑකර් ක�今日 මෝනා ලේයා ස්ලි මෝනිමව ජහ මොෝව඀් දධි කුයෆවුෛ වදියික්ලු ඒඳි‍රස ස්ලිල, විදිනො෋් පිවඟ් ඔ඼ි  Kensuke ස්වශ ස්ව Player pi vontāÁவர theirs 在why සක් tuated a mu ḍ ḍ �要 ḍ ḅ្ጉ᝼ក្ក ḏ Ḁ្ទ៕ៅកកកកកកṍ៕ទ ḃ� LIAMកកកទកទ ᲁ។។ ᱅� acompañ ᦬្ទកកទ �Help ᦬្កកកកកទ �EOက ន៕កកកកក ន។ between 캡៰កកកកក ន�កក �កៜ, ឣ។កក比較 wrestlerteri describeළ curvesuper අවප්, 라 highlighter කරාදු රැනිඅරස එය ඔබලි कළමග ලන්විරක දැනේති අවශවව඙ කෙලිිරික ආහෝිරෙłද්ιචරවානිෝවි,ශි� ංහිවි බිසිල ෢ීයු2021පු PТы అా� runs నాసిండ్టూతోల్టేవ్నోక్టేౢౚన escaఎసీచుola stamina external Okay, okay, we can, we were done with the... The next one is next, all right. Next, what's the next one? Red one. Red one. We're in the ward. Is it far away? Yes. All right. So, all right. I can say we can do a few more types of boots. It's like we're here. We could go some other way. No, so we came... We have to go all the way down to the water. It's, it's... Yeah, this is where the other champs challenge was. It's the side of the challenge. Do we want to do a picture challenge? This is where the side by side was, yeah. Why was the craziest picture of your team came from up here? වෙිදුකිරචිකිල් වැන්ත්ප් කැන්ල්ල්නාභයakap�් වන්වෙ.  olara ikte � ���වවහසම මීමිය වශ්රාුවසයධියයා වෙබ්ලන් ස්ධන් එයියියියියියුන් වෙබ්ිය්නෙ න්රාුයියියියියියයියියියය් නැන්ම කිේියගු එයියියි ාවිව,ව෢ිවා,වේිවිවි欸 ගොේ ඇත්ව cool �alog ඖය මෙවි keiner ඈ Tada, 22elnzas අසු nai ඇතන, ම෴පද්ම ද෸ිඪ෸යීමත්මיח ගසුĩමකත්මේ් ඿සබාborneවේ it ම්යිසනකටයක устрой�න yeah ඔබ, අ� fr consigo� down කැපාසිඅ කී නි ඇසති people මපාගාක්තර කිපාසින අග් කුරක් අාලාන මූස්රොඩික්නේටකි rule ඇත පොතින මේ්බා ඵක්න මේ්බ�aid � fry  withhold for  avent and contract że  feasted people  telefono  Shelley plets                           しappeal visa  他   다             לה          థLucamı కితిన కం చిసి పఛమా మచది వయి పనమ。 గాటశని నయకౕు ඔ� realizing for sporting ඔබ කින්නයට න්ලය කන가지 කෙඪා වැල්ක තාසම දැන මේය එකර. ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ � ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ � ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ ლ �  Paige,                                                                                                                                                                                                                             ඇලින් ඐලිවීමු මිනය් සහ�板 ජය රහ ල�iano peril සහිවක්, නොේ් තෙද � introducing… ඔලි මිය් ගේ් අරඩශ. එය එය තෙබ අඩස් ගොින්නක් කපා  stimuler felt to make them freeze them చాద snail చాద Difficult లాంచాల52 మనచరాసిల౿వ Milky తచాటిల౾ పాసి�II బిర్స్సూ్యి candles అిటాటెచిటн. సివోదరదకసల asylum మి మికి నితాఆచనజ Babs Water నేన్తోంట్రుడ్తాన్టికా సింన్మై ఠివినేడ్మై. I went to the last GitLab summer in January and there was only about 100 people at the company then. So, it's really good to meet new people. న్ర్నానేపినినోన్ట్స్తోర్ త్ర్నాన్ను. I think that because we've had the extra funding into the company we've got a really high target of sales to reach. ocide hésitez  embrissdha räge n Bruin  Keys ఫస ioxid క్ необход ఛ kern నఽద్ ధ౅త్లూం క్లై  sécur�ో� люб మిస నటంయానిని, ససథాస్. ఘ్టరటాను ës. టాంలి artetagen భENNIS గొలి ష్రి నౕరితిసాంలోicano�్ల్ హిత్రి మీతికొభా క్గక౭కాచాోద్నేటేను మూరోర çใหనూత్రాంి సెదింపక generates in githab�תతుయాన్లి, సావర్యiscernibleచిం� so companies are striving to build the best software applications because that's what's controlling companies and with the tool like lab you're able to do that because it really speeds up the speed at which you can bring out applications and make a change through your business. And then do you think so you're being given a possibility of creativity in your job because of all this new expansion and all of this? I am in a sense yes I mean the team is growing and you know we've all got different skills we're all from different backgrounds we've all got different languages that we speak or some of us do anyway so I'm hoping to use my Spanish and hopefully do some work in South America but yeah I'm sort of mainly based from the EMEA region at the moment and so would you say this is your favourite summit so far? Cancun was great because it was slightly smaller but I had more people to meet and this time there were so many new people that joined I had a hit list of about 30 that I wanted to make sure that I spoke to because I know that you're not sort of going to get around and talk to everyone well thank you so much ok thank you very much ok bye you you're going to look right into the camera let us know when you're ready come again so how are you enjoying your time in Cree? it's great basically we had a little of the time on Wednesday when I could go to the pool and have this really nice weather and this very nice warm water so it was kind of relaxing to basically do that because a little cold there is something about I don't know 10-15 degrees so it's way way nicer the sun is a good reason to be here I mean it's like sometimes it's a little too much like today so I have to do it what did you think of today's activities from the keynote speech to the fun adventure the amazing race adventure that we had I mean it's like I like it because with this amazing race we could do something together we could do some of this do some races and things like that with other team mates kind of competing so it's always interesting because normally we don't not compete we just work towards the common goal but something together something that is basically not work you guys don't necessarily work in the same building or even in town so basically we don't have people on table right? right so like usually like you often hang out and you go to coffee break it's not really the same feeling like big like together because you actually felt that the person is not the that is on the hangout this is actually the real person that you can feel touch that you can something do together now are there people that you like have spoken with online while doing projects but they are so surprising because they are way taller like bigger or different because the impression you have it's way different that you have on the on the flat picture so Yarko for example this is this very tall guy but you would not see that on the camera so how did you first hear about it? I actually did something like that because I was really passionate about the open source and open source project it's early days when it was still like not a company but it was like very cool and any kind of started contributing more and more to G-Club and I basically became so you're full time with G-Club and how many some in Amsterdam in Texas the most fresh memory that I have so I would say that right now this one looks very cool and so if you had a vote for the next summit or for the they've already picked where the next one is going to be but it will be around the vacations it's really how big I would rather not do it well thank you so much thank you I'm running out of questions here Kat I got 4 more for you here Kat or use to how GitLab does things. What is something that they should know? I would say that if you don't know much about the company, we have a ton of information on our website. We find it on not only our website, but our YouTube channel also. We post videos all about us and what we do, and we keep everyone informed that way. But if you have to pick one thing, you met somebody on the street at the coffee shop, they're like, what are you doing? You're not at work? How's this all working out? If I had to pick one thing, I would say we were probably, in my opinion, one of the most diverse groups I've ever been a part of. Well, thank you so much. Enjoy the rest of your trip in Crete, and I'm sure we'll see each other on the live stream soon. Thank you. Thank you. Give me a second. There you go. Oh, the chick. Everything you wanted to know. Here you go. All right. Seconds. Cut? Can you talk to cut? Good to go. Good to go. All right. What is your name, and where are we? My name is Cortland Smith, and we're at the GitLab Summit in Crete, Greece. Nice, man. Why the summit? I think it's a good idea. I think it's a good idea. I think it's a good idea. I think it's a good idea. I think the summit, what it is evolving into is an extension of GitLab's overall mission, which is to change the world from read-only to read-write. And so what I think it's all about is getting a remote team together in one place, but also extending the event to people worldwide. So wherever they are, they can participate in it and not just be an audience member, but be an active actor with agency in the overall event in terms of determining what it's all about, what we cover, what questions we cover, what things we talk about. So the event summit, it's all about being welcoming to the broader community, being inclusive, being diverse in terms of the geographies of people represented, the backgrounds of people represented, and giving them a place where they can all congregate together and learn and grow together. Why is it so important to have this time together? Obviously it's fun, but why? Why do this summit? So there's like the very hard-nosed business aspect to why this is a good use of time and money and resources, which is that when you have a company that's fully distributed and they work together, they work asynchronously, oftentimes they work with people who are in different time zones who see what one person or team member has done and written down and takes that and advances it and moves it forward, it can be difficult to build relationships with the people that you work with when you never get to meet them face-to-face, live and in person. So the so-what behind it of getting everyone together is that when you have people get to know each other as humans, not just in a work context but kind of who they are or what they're all about, what you end up with is groups of people and teams of people and teams of teams that trust one another and what that means is that if you trust the people that you're working with you work faster, you ship faster, you reduce your cycle times, you get more done and you enjoy it more while you're doing it. So I think that's what we're all about here. Alright man. Anything to say to somebody that would like to be here, maybe work with GEDLab? I think it's an incredible company. It's the best company I've ever worked for. It has got the best aspects of a company that understands open source and why open source is so great, why open source software is the best and most secure software in the world and also understands enterprises and understands the value of listening to your customers and building and shipping product for them and in a way it's going to be a value to them. So for anyone considering coming to this company I would say take a look. We're open. We're transparent. The work that we do is available and accessible. You can just go on to about.gitlab.com, take a look at our handbook, see how we do our work, see what our vision is, what our mission is, what our roadmap is, how we get things done. It's all out in the open and if it speaks to you it doesn't speak to everybody but if it speaks to you then you know, apply. We're growing very fast. We're growing about 300% year over year so there's a lot of opportunity here for people that embrace transparent companies and companies where you can be remote and work in a remote first culture and build in a way that is great for developers and great for enterprises. Awesome man. Enjoy your time. Thank you. Okay, cut. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. ාන්ඩ ඇපි ප්න්යෘණයදාක්වයතායියතාක්යත තෙවන්යදා අඩිෙලි‧ เฃිරිට! ඔබතරසු, ආකා or සමේ්ස්යැක්සය 所以 පෝමිලියව ඕයීක්ෆ්ස මටීශ කුහයක්තවprisingly�ටා기를 ිසැශ්ට ව෢හ්ක බේ epoxy එැහිව වතිරුව වකිරු.කිෙට්තු ැස෡රනිරද. ක ණාරකු OF වෙ මණබ පඒු෋ක඿ිම වැසේ dunnoියිා‐භෙනි් මොනාව� Halfenelle AN ordin పణరతే berger య్న్న్కా퍼 переход ప్లగస struggled through light stream కారా న్తినినిలెన్నేండారా కారారెశిసి engaged కారిండిషికా. ఇనిసారి కాకి సిమ౨ి కిసివరక౿కి. ఇనికిను 0.1 పకదిలి కారి సిసినిలి. � mahah- mahah, lun podd coated mahah- mahah mahahars mahahars 키  Tombi  добɤch 찹 ˌ如果 owed ˌ ˌ ˌ ˌ ˌ ˌ ˌ ˌ ˌ ˌ ˌ ˌ ˌ ඉකර්ය්ය්මු මුළශ ඀ප්ය්මු ක්වල්ම අම්තා ල්ව මාශ්සමු කසැුල්ර්න්යක්ස්යක්යක්න්රේ්රෙශ්න් කරීශක්ව්රිකින්යක්රේ්රුඥයූක්යක්නයින්මෙ� and we should try and keep this sort of format going as well as possible. It's awesome. Awesome. For the people who aren't actually physically present here in Crete, why do you think this event is of interest or of use for them? For the people at GitLab or for the people watching, just anybody watching their life. People who are not employees of GitLab but maybe have contributed to GitLab or who are potentially customers of GitLab or who have been following what we do. The first thing I'd like to say is if you are considering working at GitLab, I think this is a great example of what it's like. Obviously this is only once every nine months but we do take this stuff seriously. We are hiring for a lot of positions at the moment including developers. I'm a development lead so I do some of the hiring for that. Poor ones in marketing, he's hiring for plenty of people as well I'm sure. The other thing is I think transparency is one of our values and this is the most transparent thing I can think of a company doing is live streaming their annual get together. We're not trying to hide away, we're trying to go somewhere but then broadcast that back out which is cool. Excellent. Any last words or final part in thoughts? I wish I knew some Greek to end on some Greek so I'm just going to say this is awesome. Thanks for your time, thanks everybody for organising it and if you're interested in working at GitLab be sure to check out our jobs page. Awesome. Thanks Jan. Thank you. Thank you. Thank you. Thank you. how do you know it cheeky工作 yet uh... for the summit 크게 pm whom set sonplain ar al  apparat quarters, ԱԱԴԱԱԳդ, ԱԱԱդԱԳԱդ, ԱԱԳԸԺԱԱԳԱԴ, ԱԱԳԷԱԸ, ԱԱԯԱԳԱԳո, ԱԱԱԱԳԱԵ, ԱԱդԱԳԴ, ԱԱԵԱդ, ԱԱԷԳԱԷ, ԱտԱԯԱԱԱԯ, ԱկԱԱԯԱԾ, ԱԱԲԱԱԵ, ԱԱԳԱԱԴ, ԱԱԻԱԨ, మ్కికి క్త్ని Kwang Q. περιifall నేన్త dellady మాడ్యందింని మాలాయ్ form మరోానునురి మిి vu మున్త gdzieśచెఆం మినుొనణ మిఝన్యదిదిఉ heating త్వతేచివ్ Darkness ස්පියියි, ආපල් පිමුළ්ාඩුවය මිතුින්ම්යක්ක්ය, තෙස්මේතිවිරිමික්යගේ්යන්යක්ය තෙස්මේතුන්යක් සප් තෙස්මේ්යක්යික්යබායක්යක්යකගේත� that they might get out of it. Well, I mean, you know, GitLab is a kind of open and transparent company, so I hope you see the roadmap for the company and the vision and the stuff that we're going to be working on and get excited about that and want to try the product or maybe even contribute to it. And then I hope you see the culture of the company and how we kind of interact with each other and how we do stupid things together and play games and stuff like that and maybe want to come work here or maybe want to check out some of GitLab's products and contribute. And yeah, okay. Any final thoughts? No, these are fantastic questions. You must be a pro at this or just well trained. Well, this is I think my second time, but I feel like our community is very forgiving of errors and that kind of thing. Cool. Thank you so much. Of course, yeah, thank you. Hi. Thank you. Thank you. Okay. Thank you. Thank you. Thank you. Yeah. Watch it in my mind, man. Watch it in my mind, man. Hello, welcome to Adelaide. ប ឬ្៙ក្្ ឬ្ក្ក្ក្ក្ក្ក្ក្ අුහ  Kolleginnen අ� degree මිාත කුරින Pron කරූමන පිශත් අඩ මිා feasible.Lo..වේෛස්ප ඔබ,හිා ගී� FY හයිද්D friends හිි ඔබකීටයවක ගේ ඃම් වහිස් පැක් ඇ développementachelor�ගයු. ೀಎೊನೂಕೋರ್ಸಿರಿಿಯದಾಿರ್ಲು ಅಡಿಿಯೊದ ಠಿಂದೆತೀನೀ ಮೇತುಗಳರ್ತತೀ míಸಿಲ್ಲುಯನಿಹಾಿ ಥಾಡಿ ಬರ್ಲಿಗಳ಻ಗಾರ್ಲಿರುಡಿ ಬಾವಾEduಣಾಂತ ಆಾರಿಸು ಠಿಲಾರ್ತ ಕಾಸ drawers.ಿಯನ್ಌದ లylie contro brewerish ర möglichst  despair it finding quickly డాపడారితటిభ Project二 చ� tr వౕిమినస ఱధిక 👌 నాకిని ని బర్ంద37 మాఔ ראל�్ని పమడారోతు టుడిక మాడ crazy Man, Infin�ాకచitters�౟ మనాపడ చొఀటిస్నపసి two අප, දමාට් ගමක්වරුනු ඃිම් දievers අපශ� ali goes අපශුනු හුම්erman chien лаг interpret  spannend වවවවවව දැරවක්න්රල් මේ දෙගන්න්න්රල්න්න් and වලිට්න්නයුයික් වකිශුක්න්යියියක් ඔවසබා සිටියිල්න්න්න්නේ්නවුස්න්න්නවේයියිදෙ neuronally hai, Service's rivalry, this is policy So how do you feel I think it's great and I think thatö there's a great setting for this there's a rumor do them better better and I think it's easy for it to happen the opposite because the more people, the more difficult, but we're making it, the more people, the better, so it's awesome. Could you talk a little bit, you had said in the keynote that it's great to not to be able to work with you because you're able to really balance your work life and your family. Yes. Could you talk a little bit about that a little bit more for our viewers? Sure, so I live in the California Bay Area and in my previous role I was commuting an hour and a half each way on a good day. And if there was rain or an accident, then an hour and a half each way could become three. And it was very, very difficult to feel like I could be a good worker and a good mom and a good spouse. I mean, some things got to give at some point. And so it was, and really everything gave. I was leaving work early, I was getting home late, I was having nothing left to give when I got home. I was filling up for gas about three times a week. It wasn't good for the environment, it wasn't good for me as an individual, it wasn't good for my family and it probably wasn't good for the community. And so what I love about remote work is I feel like I don't have to choose. Now it doesn't mean I can do everything at once and it doesn't mean that when the kids come home from school I'm not in a meeting. But more than likely that meeting ends within 30 to 45 minutes in the getting home and I can actually help them with their homework. And it means that I can start dinner and go into a conference call. Or it means that my partner can start dinner and I can actually be there to eat it. So it's really great but I think it's more than that. I honestly really do. I think there's the individual and the family effect but there's the community effect too. So when all of the jobs and all of the industry are concentrated around certain cities, all of the income from tax payments go to those certain cities. And when GitLab made me my offer it was the same time an article had been written. I'm not quite sure what publication but they were rating the top 10 least educated cities in America. And my hometown showed up in the top 10 least educated cities. So they didn't, my hometown didn't get quite a point of masters for my career or they get none of my tax money. And so what you end up having is you have cities in the world and in America who continue to fail because their best and their brightest have to leave. And then the cities where the best and the brightest go continue to thrive instead of the world thriving. And if more companies can figure out how to make distributed remote work, then we really can distribute wealth in a way that is actually earned instead of just redistributed mothers. And that's not to mean to be a political thing at all but I think it really is great for communities because it's not just about the tax income that goes into communities, it's also about who's volunteering in the schools, who's volunteering in the hospitals, who's contributing to literally, who's, you know, it really affects the whole community. And so I really hope that not only can we make this work at GitLab and make this scale at GitLab but then we can go out and we can teach other people how to make it work too. And I think that can be great for the world. Not to mention the environmental aspect. The house that I live at I can walk out of my front porch and I can see the 680 freeway in the Bay Area. And I can see all the cars stopped and I can smell the views. And if we can get some of those cars off the road, we also are doing more for the environment. So really to me it's a win-win. So did you talk to some of the challenges like the traditional corporate setting obviously a lot of folks put on resources and engaging productivity but there's a very much traditional aspect in how you guys do. Yes. And obviously there's a lot of challenges. Yes. Well I'm still figuring some of that out. But I would say that it always gives back to making sure you have the best people. And that's not relative to whether or not you're in an office building or working or not. You have to trust your staff to do the right thing, to make the right decisions, to be capable of what they do. And if you can't, you need to get people that you do trust. And I think that's the foundation. Now in terms of the way it's easier is I don't have to convince people to move. I don't have to convince people to take a terrible commute. And so the world is my talent pool, not a certain area. So I feel like that enables me to get the best and the brightest without compromising because I don't have to compromise. And they don't have to compromise. Now with that being said, we all have a whole lot of different cultures and a lot of different backgrounds. I think that's great. I don't think that's a liability. I think it's an asset. And I think it's all about how we use that as an asset. And the important thing is to, one, recognize as an asset and then figure out how to leverage it the best. And that's a little bit what I'm still figuring out. But I know it can't be a bad thing. And it's funny, I was with the executive team a few days ago and I don't remember the quote exactly, but it was Picasso. And it was something about you can't see things differently until someone shows you how to look at it differently. And I really do believe that. And so by being with people with different perspectives we can look at things differently. And the problem with the Silicon Valley I believe is we think the world revolves around us. When I live in the Silicon Valley, I went to school in the Silicon Valley and I built my career in the Silicon Valley. I had the opportunity to live in England for work. I had the opportunity to live in Germany for work. So I had a little exposure outside of it. But what I do realize is that everyone I really meet, everyone's hyperbolic, most people I meet in the Silicon Valley really feel like everything revolves around the Silicon Valley. I talk to so many people who think that everybody owns a Mac and Mac is must be the number one computer sold because we're in the Silicon Valley and everyone uses Macs. But believe it or not they're five or six. Novo is number one. But if you live in Silicon Valley you don't realize that because you're not looking outside past your window. And the same thing with iPhone. Everyone thinks everyone has an iPhone. Well, no. Globally, Android is a lot more popular. And so we don't get stuck in those myopic views of only what we see, where we sit and we have a whole group of boys that know that's not how it works in my country. That's not how people think in my country. That's not how people make buying decisions in my country. And then we can be stronger for that. So nice to talk about. We spoke with a gentleman, it was very interesting. He said he's only been with the company around like six, eight months. Very new, but he already started to get to know people through wedding photos and baby photos. And it's so counterintuitive in the sense that when you're not in the same room together how do you create relationships but when we look around people seem to have an incredible bond. So what is some of those aspects of team building that you guys involve in a digital world? So we do have... We have a lot of different Slack channels. We do it that way. We also do a lot of Zoom calls. I was a little bit of a skeptic. I was thinking, okay, how is this going to work? I have a great team that works for me. But I wasn't sure how I would get to know them and if I would get to know them until I got to Crete. So okay, let's go. I'll get to know when I get to Crete. No, I've been here for a month. I got to know them on day one, day two. The difference, I think, at GitLab is you don't just get to know the people who sit next to you. I think when you're in office building there's been studies that if you have to walk more than 100 feet you email, you text message or you call but you don't actually walk 100 feet. So at GitLab you can talk to your colleagues who are more than 100 feet away and would be more than 100 feet away. Incredibly to me is that we all work from home so we understand that introduces other variables. So if FedEx delivers and my German Shepherd barks no one's getting irritated at me. I'll put my phone on mute while the German Shepherd's barking to be polite but then they want to see the German Shepherd. And you know if my kids come in to give me a hug when they're leaving for school they'll come in in front of my computer screen when I'm on a video call and they'll give me a hug and they'll wave to the video and then they'll walk on. So my colleagues get to not just see me they see my family, they see my environment and that makes you feel closer when you actually see how and where people live and so it's really fun and then we do more thoughtful, pragmatic things like we have a team call every morning at 8.30 a.m. say just like that we have a team call every morning at 8.30 a.m. and the team call is not about work. So the team call you talk about what you did over the weekend or what you're doing next weekend or the things that interest you you might play piano if you just use learn a new song on the piano it's very much just about getting to know people and it's not based on an office building you tend to get to know either the people that you work with or the people you figure out have the same interest as you so you're like why scuba dive so when I was at Netflix I started a scuba dive club so I got to know the scuba divers really well but if you weren't a scuba diver I didn't get to know you that well and guess what that means you develop new interests because you see them getting passionate about something that you weren't passionate about and you didn't know much about and then suddenly you might want to try it so it's really fun so it seems that it's a very life centered model and it's very futuristic and it's very new to a corporate world where do you see in five years remote work and this model culture that you guys are bringing where do you see it going well honestly I hope I see more people doing it and I think that one thing that makes it easier for GitLab is that we all do it I think it's harder for companies that are centered in an office building and you have a few remote people because then those remote people tend to be out of sight out of mind because you're still doing the hallway conversations and you're not bringing them into those as much so I think that what I would love to do once I tackle some of the things that we need to tackle here at GitLab is I would like to while working here also help other companies figure out how to do more of that and then I also think through the GitLab software and through what GitLab creates at least from a development standpoint we enable every company to do this you don't have to be at your desk next to your co-collaborator to push code and figure out a code you can do it all online together so the technology we create enables other companies to do this and so I think that we can take our technology and take our experience and pass it on I don't believe in one-size-fits-all and I don't believe that one culture fits all I believe we have to build our own and each company does but I do hope that the learnings that we get and the success that we show one shows people that you can do it and then maybe help them know how now none of this will matter if we don't have a great product it doesn't matter what our workforce looks like if they're in the big skyscraper or if they're all in their homes if we don't have a great product the way we work won't be credible so the first thing is having a great product and how do you have a great product by having great people create that product so that needs to be our first focus but once we can prove that I think we can really help others and I hope that in five years this isn't strange this isn't unusual this isn't different but it's standard thank you wonderful rest of the trip thank you very much thank you thank you is that okay or should I move the camera ඔිස්ව� Chair එගු එමා ක Dais Adam, 你 see the bread coming over it. प्ऱाद करीडवग, लिए करीडवग, से अग ग़ी शीए। या, एक चागी। ಡೀಡಿಾಸ್ಮಿಕ್ಟಿಂದಾಡಾ wipes ಇಥಿಸaaSಧರ бог ಕ astronoiಕಿಸಿಳ ಮೆವಂದ ದಾವಸಗಾನ್ತೀಟಿಲೂ ಪುರವರೆ ಕದಿಳ಴ಡಾಗಬಟಿಲ ಂ chacunದಿರೇ ಪಾವಾಂದಿಲಿ ಕಕಾಕ್ಯಾಲಾಮೊ ಡಿಸಿಗಡೆ � Prime Pawnಯಡಿಲಾಯಸ್ಮ� ૐ ૎ ૣ ે ૄ ૬ ૎ ્ ૎ ્ ૃ ી ્ ્ ્ ૬ ૎ ્ ્,્ ્, ્ ્ ૎, lend. ... Ja, am I wound it? ... ... I'm no that ... edsiębior  wygl Nova හාසුකාවස්ම්ත්තයික්තුර්ප෠ල්ර් එයිකුස්තයියම්මත්යම රයෙිද්න්නේක්නයමයික් එයිකක්න්න මෙයියික්න්නේක්නකක්න්න්නක්න්නේක්නක්� మాలు మెడిలు మిస్లు మెసిన్డ్దె మోబర్. మార్, మారిలు, మోబు, మోంరిట్టోన్యదికెతార్. మార్లు, మారిటృచుం.  Kes  regulators and customers  day, when he is нем sweater and I've been mentioning him  day left yesterday yesterday comment asking for a haunted world oh I'll return please 💦 aren't supposed to be staying down at be around those so just again ᄄ ᄁ ᄇ ᄹ ᄄ ᄅ ᄱ ᄁ ᄄ ᄃ ᄜ ᄟᄵ ᄄទទ, ᄂ ᄜទទ ᄱ ᄕ ᄒទ ᄂᄒ ᄔဉ ᄕទ ᄕទទ ᄛទ ᄮ ᄌ� book concealer. ᄏ ᄪ ᄤ ᄹ ᄜទ ᚔ Она ᄟ ᄅ.... ᄛ. ᄉ congratulations.  Airline   gegenüber ege dwe  insists on pulling in to this corner zewa ǐ ɑʈ ʈ ʈ ʈ ʈ ʈ ʈ ʈ ʈ ʈ ʈ ʈ ʈ ʈ ʈ ʈ ʈ ʈ ʈ ʈ ʈ and uh... ʈ ʈ ʈ ʈ ʈ ʈ ʈ ʈ ʈ ʈ ʈ ʈ ʈ ʈ ʈ ʈ ʈ ʈ ʈ ʈ How long have you been with your lab? Since February. It's been great. So this is your first summit? First summit? What do you think so far? So far so good. I had a little bit of a... As you do in Agile, you inspect, you adapt. So what are you most excited about with those? Everybody here has really been, it's a great experience to see everybody tomorrow. I'm sure that's going to be a great trip. But really, it's just a good opportunity to meet everybody. You see them out and talk to them and learn all kinds of new things. Did you know about the summit before you joined it? I did, because the guy who hired me was about to leave to go to the summit. And so we had to wait until he was back to actually finish. All right, take care. By this time she couldn't come. I don't believe a lot of people, last time we had a little bit more kids and families and so this time it's more focused. So I really like that. And obviously the live stream is something new that is exciting. So how big is your team? We're about seven people. So you guys meet together very often? Not really. My manager has actually had some family challenges and so he hasn't actually been able to come out to much summit activities or anything but I was lucky enough to get a lab to pay for a trip to actually see him in DC earlier this year. So it's really nice. I love the food. No, nothing special. You go side trips already? No, just going back to it. gilab.com and our production environment web service, software service we have, as well as the internal resources that we use to develop and build. How long have you been at GitLab? Values and everything was incredibly transparent. Everything on how we function, organize, the decisions are made, people are empowered. It was all there. It was like, this is amazing. I want to work for this company. Have you ever worked remote before? I have worked remote, yes. So that wasn't anything different. What was different was the places where I worked remote weren't 100% remote companies. They had offices and I was a remote employee. So you always found yourself missing. People gathered in the conference room before the dialing started after the conference call you missed something on the water cooler. Being 100% remote is amazing because we're all using a remote medium to communicate with each other. We're not actually in an office. So you don't miss anything. The communication is amazing. How big is your team at GitLab? There are currently 11 of us. How often do you meet? So we actually have stand-up meetings once a week where we get together and talk about what's going on, just a real quick stand-up, what's the current activities, what's up next on the radar, any problems that we've had going on and what any hotspots are with our workload. What would you say is your favorite part about working at GitLab? I love working with the technology. I think we've got a great product. It's really cutting edge technology but the people in the community, this is honestly the first place I've actually ever worked where somebody came up and hugged me at a conference because of the software that we made. I said thank you for making this. That gives you an incredible feeling in terms of like wow, this is actually something important that people are using and quality. So definitely the people in the connection. So if I do my math but this is your second summit? So I actually started on a summit. So I started in Austin, Texas. My first day was actually lazily floating down the river with the rest of the team and then my second summit was Cancun so this is my third. Oh wow! So how does this one differ from the other ones that you've been at? There's a lot more people here. It's been interesting to watch things grow by leaps and bounds. When I started I was employed number like 54 and now there's 200 of us. And what are your plans for the rest of the summit here? You know, I think definitely going to get some cool side activities in. We got these fancy flashy badges to try and make a project with. Yeah, I saw that. What is that badge? The flashy badge? Yeah, so we got these in the same ideas like conference badges or like hacker conferences. It's a programmable computer and the whole goal is to see what you can do with it. So they have Bluetooth in them. They've got accelerometers. They've got all kinds of gadgetry in them. So it's just a creative hack to see what you can actually make your little badge do. So what about for non-technical people like myself? How are we supposed to code these badges? So the goal there would be to partner up with one of us nerdier folks and it's a whole learning experience. So the beautiful thing about this stuff is that the software that you use to like write it really was designed to help children learn about programming concepts and structures. So it can be as complex as actually writing code to as easy as dragging and dropping building blocks to make the badge do what you want to do. That's fantastic. I don't want to keep you from dinner so it was good to meet you, John. And I look forward to talking to you. Jamie, you're sitting here. Thanks. It's great to see you again too, Jamie. What do you do at GitLab? I'm in a sales position at GitLab and my responsibility is to bring in some very talented people from technical support to development to help solve problems that our customers may have and generate revenue for the company. How long have you been at GitLab? I joined on the 15th of May so that's about five months now. Did you know about GitLab before you joined GitLab? I was at a customer site about a year ago and it was the first time I ever heard of GitLab and the customer said I was at Rally at the time and the customer says do you work with GitLab and I had never heard of the name before but it wasn't until Mark Roge reached out to me and introduced the organization to me that then I began to put things together. And is it everything that you thought it would be? I would say to you that I wasn't sure what I was. When you make a move, a career move, there's a push and a pull and you always look at the push and you consider the push. The pull was fascinating. An organization that's completely remote an organization that has certain values that you feel strongly about are all real important so I was very impressed and I just felt a high degree of alignment with the organization and where it was going and I love the idea of disrupting Atlassian. What's your favorite part about working at GitLab? Favorite part? There's a lot of parts I think it's fun and quirky the afternoon team call and when you hear about what they did last week what they did I've heard some really funny stories I've seen somebody who's cleaning money money laundering but buying a horse things that I've yet have been exposed it's a unique experience so it's just fun. I reside in Maryland and we have in fact I've been remote since 1995 I don't think I can ever go back to an office again and I have a feeling in a couple years many organizations will also be completely remote I don't think it's a I think it's a growing trend not a declining trend that's for sure So what have you enjoyed most so far about the summit? To be in Greece to be in Greece with my wife and some nice people to be in Greece with my wife and a lot of nice people and with the weather as it is what more could you ask for? Do you have any goals for the rest of the summit? No I'm here as a listener I'm here as somebody to take advantage of all that it has to offer In fact that's really a nice thing Jamie is it often when you go to either a sales kickoff or a club there's a lot that's expected of you Here the idea of getting together with our compatriots is what it's all about I'm thrilled Well thank you so much I don't want to keep you from dinner so I'll talk to you soon Take care David Thomas Your solutions are packed Yes I'll go You can start anytime So David what's the best part of working at GitLab that I wouldn't be able to tell from a tour? A tour A tour isn't it Tour of Tour of our virtual virtual workspace right? One of the things that I like about GitLab is how highly collaborative we are especially given how distributed we are so we leverage a lot of technology like Slack or video conferencing to stay connected and a big part of using that technology is having a presence within the team What's neat about that is it really breaks down the barrier of time zones and being distributed Awesome So in one sentence how would you explain GitLab to a friend? In one sentence how would I describe GitLab to a friend? Of course you have to say amazing Amazing has a lot of different layers but from the people the culture what we're enabling our customers to do enabling people to do there's a lot of goodness there So I would say awesome So basically one word right? So let's see What are you most proud of that GitLab stands for? What are my most proud of that GitLab stands for? So one of the things that we strive to as part of our mission statement is to contribute So when you look at the platform and what it offers my background, I've been running software for 20 years and when you look at my interpretation of that is when you look at what it takes to work on a project and release software there's so many stakeholders involved in that process from your project managers your scrum masters, your devs your release ops, etc and having one single platform that gives a unified view is wildly powerful and it's super exciting In fact I can get goosebumps thinking about it So I came from an environment where you had like 15 tools all stitched together and duct taped together So the fact that we have one tool where everyone can contribute see what everyone's working on collaborate is really exciting So I have one more question So when you were interviewing and going through the whole process were you what were you thinking in terms of if you really really really want to work had you done your research beforehand so what was that process like for you in terms of interviewing for GitLab So I knew I wanted to work at GitLab the moment I went to the homepage Now granted I've been doing this for 20 years so I know what it's been like for developers, for teams for stakeholders how complicated it is to build software and when I saw there was finally one unified platform for everyone to ship great software fast to me that was it It's been something I've wanted for the last 10 years writing code Finally it survived, why haven't we had this Why didn't we have this earlier Awesome, thank you so much Thank you I guess I'm next 8 seconds Anything you want me to ask you Did I scarf down a pound of lamb and I'm paying for it I should have thought better about that Alright, you ready? Sure So we start with the names Okay So tell me your name and what you do here at GitLab My name is John Woods I am a Solutions Architect here at GitLab And how long have you been with GitLab Just over 5 months now So, relatively new Tell me what your biggest challenge was onboarding at GitLab What was the worst part of onboarding Just getting through all the onboarding tasks For every new hire there's over 100 tasks you have to complete If I wanted to break it down probably doing the coffee break calls getting all those done I felt I was so busy right off the start that actually connecting with my colleagues and peers was really difficult So that was my biggest challenge Since then though, I found it's a lot easier You get a little bit more time in your hands and you can catch up with folks and get those coffee break calls done So for the audience members that don't know what a coffee break call is what is a coffee break call So a coffee break call is a way within GitLab of connecting with folks because we're all remote we don't have a water cooler to stand around and chat about we don't have that opportunity to go for coffee in the afternoon with somebody So instead, you call somebody up you spend 15 minutes, half an hour just personalizing with folks find out what their interests are what board games do they like to run on the weekends, what do they like to do and just get to know your colleagues and your peers So I heard you say board games Is board games a big thing at GitLab? Apparently it is A lot of people at GitLab love board games so it's been great connecting with folks around a hobby we all share and love and I think that's been great I mean you and I personally have connected on a number of times talking about the games that we love we've all brought board games to Greece we're going to spend a night playing them so yeah just finding those connections with the folks you work with is a great way to get to know them So what so far and it's only a couple of days in for you so far This is going to sound funny but it's realizing how short and how tall people are because we talk to everybody behind a camera so you only see from here on up so I've been told a handful of times you're taller than we thought you would be and some people oh he's shorter than I thought he would be one of my colleagues Joel he's like 6'5 I'm like you're way taller than I thought so that's actually been the biggest take what I've found so far is just seeing people in real life for the first time so last question then I'll let you get back to dinner for you and now I'm in UX so I have a very different experience than you do describe a typical work week for you my job is interesting in that I'm sort of half sales and half technical so half my work week is pairing with the sales folks on discovery calls I run demos for potential customers the other half my job on the technical side is I'm doing training for customers I'm doing implementation stuff so how do people deploy their GitLab server how do they make it so that their GitLab experience is successful for them awesome thank you so much John great to see you good job got more names in there right if you could just say your name and what you do here at GitLab my name is Brett Walker I work in the back end development team on the platform team awesome so I see that your badge is in Sharpie are you relatively new I am very new I started last Monday still a little green around the gills but you know so having just started for you and I've asked this somebody else what was the interview process like before you applied did you know about GitLab were you excited about it what was your incentive for coming here and going to that process I've done a lot of freelance work and I actually used GitLab already and enjoyed using the product and I was doing a few things and looking down and saw the jobs and I looked into it a little bit more and I read the handbook and it kind of inspired me the open culture and the transparency and everything so I thought alright let me give it a shot awesome so being new you have a series of onboarding tasks that you have to do which is intimidating for everyone who starts and you have to do a series of coffee breaks and we've talked about this with others that coffee breaks is a way to get to know people how do you feel about that I have I've been a few of them I enjoyed it it's kind of getting to know people a little bit it's a little bit intimidating meeting someone on video and talking to them but it's nice to get to know people and understand the culture and all that stuff everybody was super friendly now I work in UX so I don't have the same experience as everyone else here we all have different teams that we work with and different areas that we concentrate in so so far what has been your work week like in terms of being good and kind of what you do for the back end working well I have a one-on-one with my manager we've had a couple of those but I've already been assigned issues even from the interview process I worked on some issues and contributed immediately from that and they were bigger than expected so I've continued to work on that as well as pulling in a couple more so I've been digging into those just getting after it as best I can wow you're an overachiever so now I'll turn it around do you have any questions for me you're new is there anything that I can answer for you I don't have anything not right now I don't okay then thank you so much so let's do what Greg wants which is to stay on the table you're about to lose battery I say we find something and then hard wire in and a beer close I I I I I I I I I I I I I I ව඲වරමන් ඔරුස ජොපදෙ අටිව් ඝාණ�kraලඩ් ආුඪළස්ප්K爸ට වළටිවා W Ó R ඉටි අනමට් කිශ්ත් බාර්‒ ජඩෙි, අවොතින් වක්ශිනඔ එකිකිඅවකස් ඇපාවදාරටිඔ෸ක මත්කක්ාවු අ Illust margatස්වු, ██වrils болරහමකටරණ ලිතණකෙතය1 මත්කක ග෠්ක්වළදාau Zhiceth石, ඔමිගිදාර� BefHHh දැරකට උෙU os veland త౿机 resize నౚfeeding శ్థత్ ͡° rules న౔మ్నравствуйте మ్త్ ͡° న్రిదేమ్స్ర్ dean ఱిమ్నేకమ్గ థ్మ్� Industry ఉపయు ఽివి కిమ్గాన్టికే возв�౔ బ్యఅ మ఍ధోనxaటా. న్ 먹어ап Auft Voygas