 Felly, ddweud i'r ffordd i'r gweithio, a ddweud i'r cyfnodd i'r cyfnodd i'r cyfnodd i'r gweithio. Yn y dyfodol, 20 ym 10 ysgolwch, rwy'n gweithio i'r ffrifau o'r SDLC o'r Gwldman Sacks, ac oedd GITLAB yn gweithio i'r gweithio. Gwelwch i'r gymryd, ond rydw i'r Mholtwr na'r 20 yr ysgol, rwy'n meddwl. Fy hoedd ydym yn ôl 4-5 tunnfryd, ysgol edrych, oedden nhw'r cyf Cause Security, T.I.S.I.S.Ym 4-5 tunnfryd yn yr awl. Mae gwaith gymhoedd gwahanol byddwn i'r team ysdelf penodol yma yn y Unedig Unedig Unedig Unedig Unedig Mae choifeill rydyn ni oed, gyfnodol iechyd, gen nhw'n golygu reoedd s akt Ond efallai bod yn cyflosfawr oherwydd ddweud Mae'r roeddo yn golygu ddweud rydyn ni oed fel gweith ble amgylcheddu a trydwyd bwysigionol Oherwydd byddwch rydyn ni'n rhaid yn gweithio at rydyn ni mwy oed Fe wnaeth eu ddechrau gyda Marcus rhoi i dda i ddigon o'i cyd-degignol ac ydych chi'n gweithio'r ffordd yma i'r ffordd ac i'r ffordd cychwyn ffodol. A gydag yma, rydyn ni'n gweithio'r rydyn ni'n gweithio'r $35b yn fawr. Sdlc yng nghymru, rydyn ni'n gweithio a'r ffordd yma i'r platform sy'n gweithio'r 9,000 ynghylch ar y fferm. Rydyn ni'n gweithio'n gweithio yng Nghymru Sdlc yng Nghymru i'r ffordd yma yn gweithio'r ymddangos a'r ffordd yw ni'n gweithio'r ysgol. Rydyn ni'n gweithio'n hwnnw o'r digwydd yn gweithio'r ysgol o'r ddefnyddio'r gennymau strategiaid ymddangos. Rydyn ni'n gweithio'r cychwyn fforyd a'r ysgol yn gyllideb, rydyn ni'n gweithio'r cychwyn fforydd ymdangos, oherwydd, rydyn ni'n gweithio'r ysgol, we can be a reason not to come and work here. So our team, we feel is in many aspects of the firm. Additionally we are responsible as well as providing platforms for people to write code in terms of the processes and tools for people to acquire and manage new languages like and there associated ecosystems. Yn y gweithio ddeithas yw gyd-lab, rwy'n gweithio'n llwyffyr awdurdod gyda'r gwaith a gyd-lab. Mae gweithio'n gweithio hynny i fy ysgrifennu sy'n ei ddodol. Rwy'n gweithio ar y maen nhw'n gweld cyffredig yw yma, sy'n 10 o'r awdurdod ymgyrchau. Byddwn ni wedi'u gweithio ar y maen nhw yn ymgyrch yma, Mae'r ffordd yn ymddangos i'r tawd, rwy'n ddweud o'r ysgriffion. Mae'n ddweud o'r ddweud, boi wnaeth fyddwyd yn enw yn dweud o'r rhaid i gael eich busnes. Mae hyn yn rhaid i gael eich ffirm, mewn gwahanol, a'r rhaid i'r sdlc i'r unrhyw mwyaf, o'r cyfnodau, procesau, llwyddoch chi yn dweud, oherwydd fyddech chi'n gweithio. today, they also reflect different styles of development that people want to have in the bank. So some people prefer theははw normale. Some people prefer way front. Some people prefer calendar based deploise. We try and cater for flexibility for different types of application. And many of those have had up to and including a quarter of a century of contributions, improvements sydd wedi'i ddweud cyfweld. Mae'r pwysig yma yn fawr o'r cyfrifiadau a'r amser o'r cyfrifiadau sydd eu bod wedi'i ddiweddol yn ddiddordeb i ddod yn y ddweud arall y gallwn gwahog, mae'r cyfrifiadau dyna, mae'n ddweud o'r cyfrifiadau yma gynnig, rwy'n ddweud o'r Cymru o'r gyfrifiadau yn y ddweud i gael yma mewn gwir ynghylch o'r gyfrifiadau. Mae'n ddweud o'r cwrs o'r cyfrifiadau ...gynningoedd, jameil iddyn nhw, mewn maen nhw... ...eg wych chi ddigon uchau yn y gallu achat ystafell... ...y cael bule cwylwni, cyntaf hefyd mewn solvedig... ...y hollol hefyd yn unig o'r gwybeithio. Felly, o er mwyaf, mynd i ymddangos ni wefyd yma dim sy'n rhoi'r... ...eithaf ein bod ni'n gwirio gwrthu'n gweithio'r myfi mryfeddau... sydd y gael gyda'r lab gyda'r gweinwysig yw'r gweinwysig ac yw'r gweinwysig yw'r gweinwysig arall. Mae'r gweinwysig yn allan y cyfloghaf. Mae'r gweinwysig yn allan fysg i ddweud y cyfle ar y gweinwysig yw'r gweinwysig ar y gweinwysig, oherwydd y dyma'r ysgol cyngorau gan y bydd ymgyrch ar y gweinwysig yw'r gweinwysig? ..a thysgaeth cyflog. Felly.. ..a'r rhan o'r tyfnod, ..yna'r cwmhynion 2017, ..yna'r cyflog sydd wedi'i'r tyfnod... ..yna'r cofnod o'r CEO, ..yna'r cyflog ymlaen i ymdweithio bwysig... ..yna'r cyflog sydd ar gyflog sydd ymddangos... ..yna'r cyflog sydd yn ysgrifennu... ..yna'r cyflog sydd ar y cwmhynion. I think it was seen that it was increasingly becoming more strange to new people joining the bank that they would join and would be writing code in something that was not get. So probably the most common SDLC we had at the time was quite a lot of custom tooling based around subversion. I think people were joining and looking at it and saying, you know, this is not something I'm used to. It's not something I used at university or at home and it just looked increasingly anachronistic. I think it also sort of corresponded with a time where the firm was trying to look to really embrace cloud, embrace containerized solutions like Kubernetes. So those three things together kind of generated this mandate for us to go and look for a Git-based solution. We had had a little pilot some years ago with, it was actually like Gis and Garrett and I think the learning experience from that was we really wanted something that was a more complete like out-of-the-box solution for many more of those things around the diagram and obviously because I'm here talking today, we chose GitLab and we picked it around December 2017 and we spent the first three months of 2018 kind of engineering it at Goldman to fit in with some of those other things around that diagram and some of the other things we have at Goldman. So for example, the Postgres that sits behind GitLab, we wanted to use a Postgres that our DBA team run for us. So that sort of thing across all the bits of infrastructure inside GitLab, we had to sit and engineer that properly and we went live with it around the end of April. So it was a great success. When it went live in April, I think there was a huge amount of expectation from our 9,000 engineers at Goldman about what GitLab could do for them and very quickly, so all through the beginning of May, projects were moving at an enormous rate, either new projects being created on GitLab or projects moving off the older SDLCs onto GitLab. I think people just loved the fact that it was a really high quality solution on various different axes. So they obviously, because it's a vendor product, they have a lot of really high quality documentation and training. I used to get asked all the time how do I do X in GitLab or where is the documentation for Y in GitLab and invariably we could just direct people to the official GitLab docs or perhaps a YouTube video that someone had done on it and obviously that's a luxury that I know it sounds trite but we never had that before with any of our homegrown SDLCs. So that was wonderful and all the way through 2018 I used to get asked questions about how do I make Maven work with GitLab and I'm like, well you can just go in, there's a document on it or a YouTube video or umtine stack overflow questions, it was fantastic. My additional things to touch on, my team sits alongside a quality assurance engineering team and also an agile team so as well as kind of arriving at a time where the firm wanted to do more things in cloud and more things in containerized type solutions We also very much wanted to embrace shift left as many of the other speakers have alluded to. GitLab provided a very natural way for that to happen so we've shown a couple of examples on this slide. So for example my colleagues in course assurance engineering wrote some software that kind of makes quality assessment of people's code and as people push merge requests up to GitLab it uses the merge request in the kind of rich sort of markdown based interface that that provides to kind of inform developers in a timely and shift leftish fashion where they could do better or what the quality assessment of their code is and as you heard my colleague Soti say we're some way down the road of introducing more and more scanners and controls and checks which because we're a bank we have to have and the CI CD pipeline and the very concept of a merge request makes that significantly easier than it ever was on any of the predominantly head based solutions that you might have with subversion or CVS. I think we and you can see the points on the bottom of the slide there like we really didn't have to sell it. I can't stress that enough. I mean people just picked it up. They really enjoyed using it especially people that had used the older SDLCs at the firm giving them GitLab was like they'd been like living in a living on water for 10 years and we suddenly gave them like a nice glass of beer. They you know they stuff just moved the in terms of like the road to implementation so perhaps unlike some of the other presenters we feel very much that we're still on the road and the journey we although we've moved we have around six or seven thousand projects now on GitLab. I still have an enormous amount of projects on the older SDLCs that I have to think about. Our forward is very much to try and coalesce everything to one SDLC onto GitLab. The and most of the reasons or the impediments to doing that other than just sheer quantity of repo. So for example in some of the older SDLCs I have about 25,000 repositories that I have to think about. We continue to think about and consider our control surface. It's very important to us at Goldman Sachs. We take our regulatory and control responsibilities very seriously. So as we engineer and think about more controls on GitLab and we build more controls there it ungates more projects being able to move from these older SDLCs onto GitLab. And the and the other point is that we're also some way down the road of the initial deploy we did of GitLab was on premise. We deployed it onto an on premise Kubernetes cluster. But with the firm really having a increasingly strong appetite to move to cloud. We want to basically redeploy GitLab in a private instance in Amazon and then move things move everything to that instance. We feel that that has a number of advantages but not least of which is it facilitates proper cloud native development as many of the other presenters have indicated. It's the sort of thing that we want to do at Goldman Sachs and we think that GitLab is the right tool for the job and is front and centre in providing that capability to our engineers. Some kind of closing remarks. It's been a real rollercoaster ride. It's been like working with GitLab. I remember going out for dinner with Sid probably about six months ago and we were asking I was talking to him about like how we built his company and the thing that he really articulated to me was that the key thing he felt was really important was like transparency of information and that's one thing I personally feel we've got out of the relationship with GitLab. It does feel like a true partnership and we can see all their code. We can read their code. We can look at their code. Everything is public. We discuss everything on GitLab issues. I mean we do have some obviously confidential things that we have on private issues but for the greater part we just use the public GitLab issues to engage in dialogue with GitLab and I think we have a very fluid relationship and partnership with the company. I think it's been key as SDLC has come alongside Agile and Quality Assurance Engineering. It's been an absolutely vital enabler for us to drive the firm forward as it's sort of described in books like Accelerate to a real Agile shift left, real true CI CD package. I think it sort of patterns. Had we not had products like GitLab or indeed GitLab we would be significantly further behind on that journey that we very much want to continue on. Fi'r ffordd, mae hwn i'n dda i... ...di Assist yn ei gwyrdd fel nhw. Felly efallai mae'r gweithio i'r Arlyth. Dw i'r hyn o datblygu gyda'r cyd-fawr... ... sydd wedi ddim yn ymddangosio i'r salog, ... bothero ar y hwnnw, ... lle mae'n gallu'n gweld i'r ffordd, ... tw 화장io at y cyd-fawr, ... i'r gweithio i'r Gweithio i Gwyllol... ... ac i'r wych sy'n gwybod, ... ymddangosio i'r wneud. Felly ar hyn, dwy'n gwneud o'r gweithio, felly rwy'n gweithio.