Hey, everyone, this is Alan Schimmel of DevOps.com. And welcome to another DevOps.com webinar. Just a little audio problem here. OK, hopefully we've got that rectified. I apologize. OK, everyone, today's webinar is sponsored by GitLab. And it's top five takeaways from their 2018 Developer Survey. Before we get started, though, let me just quickly go over a couple of ground rules here on how we're going to run today's webinar. We really would like to see questions from our audience. I know many of you are just logging on. And we have a special section of our Go to Webinar Control panel set aside for questions. If you look, for many of you, it'll be in the top right-hand corner of your screen. You'll see a section of our questions if you click the arrow, so it's down pointing. You can put your question right in there. You can type it in. We see someone's already typed in ready. The nice thing about putting your question in here, folks, is it's automatically queued, so we have a record of it. We'll be able to get to it. You don't have to worry about forgetting it. And if you have multiple questions to ask, you can put them all in here rather than trying to remember three or four questions. So question section is for questions. If you're having any technical difficulties, perhaps the audio isn't working well or the slides aren't progressing. We do have engineers standing by to help you. We ask that you use the chat section, which is at the bottom of your Go to Webinar Control panel. Again, click the arrow downward facing, it expands. And you see you can type in your message there. And as I said, if you're having any technical difficulties, that's the place to go. If our organizers, our engineers see it, we'll try to help you out to make sure you get the full webinar experience. OK, that being said, though, let us get going with what I hope is going to be a great webinar today. Our first, as I mentioned, it's sponsored by GitLab. And this is based on a 2018 Developer Survey they did. And I am happy to be joined by my friend Ashish Kuthialla, a director of product marketing at GitLab. Ashish, welcome. Thank you very much, Alan. Excited to be here. Absolutely. So Ashish, before we get dive into this survey, a little background, if you can. When was the? So GitLab has been doing an annual survey every year with developers. And the objective of this survey is to find out what's really keeping developers motivated, what's working for them, what's not working for them, are the perceptions and the findings similar to and compared with their management, are there disconnects, or which organizations are functioning well and not functioning well to get to the root cause of this. And then to share this with everybody. We have a lot of developers using our products that love reading what comes out. And for this particular survey, now we ran about a month's worth of data collection and more than 5,000 people contributed. So it's a well-read survey and therefore everybody wants to participate in this. And the good thing is that we were able to attract not just the typical male coders, but actually good diverse section. Yeah, 25% female is outstanding in an audience that's probably only 15% women, unfortunately. Absolutely, we were very happy with that. But we're getting there and that's good, good for you guys. And so if you wanna look at where did everybody reply from, it's from all over the globe, right? So of course there's a majority in Europe and the North American continent, but pretty good representation from other parts of the globe. And the demographics, if you look at the different services, they were also well distributed, like people doing IT and education and business services, telecommunications, retail, you see a good mix. And so we can start to talk about it. This is the next slide, but yeah. So I love that it is so diverse, frankly, as she should. Interesting though, eating your own dog food, right? We find that the tech SaaS industry really consumes so much when we're talking, because we see it at devops.com too. Our demographics are not that different from that world map that you put up there. We probably have a little bit more in India than you do, but otherwise it's similar. And we also see that technology companies are one of the biggest demographics followed by financial industries, healthcare, stuff like that. So we're looking here at a perception gap, right? The transformational promise of devops. And again, this is something we've done surveys with too, Ashish, because for too long, I started devops.com four and a half years ago. I remember. And for too long, it was more of a gut feeling that this devops thing has to work well. It's got to save us money. It's got to be a good thing, but we really didn't have metrics to show that until relatively recently. So I'd love to hear what your interpretation of this is here. So I think if you look at it, companies tend to look at devops as the next, transformational methodology that's gonna solve all software delivery problems. And of course, there's a lot of truth in that when done really well. What we're finding out is, when you actually go and start with these organizations, managers and management layer seem to have a more optimistic view of where they are with the progress with it and what they can do with it. And developers, though they are very, they find the promise in it, they tend to agree less with the optimism of the management. And from our perspective, that makes a lot of sense because it's the developers who are in the trenches tooling, retooling, trying to configure, making that CD pipeline work, always kind of running into different roadblocks and trying to solve that all the time. So, though they're excited, I think they're not necessarily like, all rosy about it as management thinks it. So let me just take a contrarian view on that. Tell me what you think, Ashish. Could it be, and I'm not saying it is, but could it be that the developers are kind of lost in the trees and not seeing the forest in that they are so consumed with their day-to-day tasks, their piece of the pie, their piece of the puzzle, but that's all they see and they see those problems with their little piece of the puzzle. And so they don't take that larger view that sometimes a manager might have, right, of the entire project, of the entire thing. And so perhaps that explains why they're, let's say, a little less optimistic, not pessimistic, but a little less optimistic. A little less optimistic. Then the managers are, because the managers maybe have that larger, bigger view. And I think it's, I would agree with that. I would also say that the developers are dealing with massively incremental changes that they have to fix and make. It's their universe. They may not see the overall progress, like you say. But even at the management layer, I think, they do seem to see the progress is being made. If something used to take six months, you're maybe down to five and a half months. But the developers, I think, being the innovators they are, they want their code to do magic. Better faster, cheaper. They want to get there faster, right? I mean, this is our observation again, but the stitching together of the tools, getting them to work right, different technologies, they spend a lot of time doing that. They love doing it, but it takes them away from their core of developing the software that'll deliver value to the business or deliver more revenue. Absolutely. I think there's some frustration there. There is. And again, let me just have full guy. 65% of developers agree that DevOps saves time in the development process. That's a super majority. That's almost two thirds. That's pretty good. Which is still high. Yeah, it's not 81%, but it's still a pretty high thing. So by anyone's measurement, we would have to say DevOps is saving times in the development process here. Makes sense? Yes. Okay. So then we next found out the big learning was, everybody acknowledges that there are bottlenecks and delays in this development pipeline or by using DevOps, it still gets stuck. But where do they actually encounter these delays? The bottlenecks varied from team to team. The majority of this was in testing. The next one was planning. And even here, we found out that while the development and the operations and practitioner teams actually found most of the bottlenecks and the delays in their actual phases of work, whether this was testing, applying to production, et cetera. And it came to management again, bringing it because we just talked about it. Management found this, they were most frustrated and concerned about the planning phase of actually getting this kick started. And that's not very surprising, right? Because they spent a lot more time there planning and wanting to generate ideas and push them out. And that's where they want to get started really quickly. When the developers and the testers, they still work in silo teams today, even though they're practicing DevOps, they look at their local universe. The testing phase might have gone on from three months to two weeks, but they still think I can go faster. Yeah. Well, again, 52% or majority of people say that testing is where they encounter the most delays. I don't think that's not a number to be taken lightly, right? That's a significant finding. But I also, to me, it just feels true in speaking to DevOps practitioners around the world, because this is why continuous testing, automated testing is such a big piece of that DevOps software development lifecycle, right? Because if that's the single biggest cause for delay and we can automate more of that testing, it's got to come down, right? It's got to, you would think anyway. It does. And you can't start testing. We'll see a couple of slides down if you're not trying to continuously integrate right away. Yes. You can't do the automated testing without a CDCI pipeline.  Yeah, you absolutely need that. And this is part of, whether you want to call it the software factory or the software development lifecycle, the continuous integration pipeline, you need that infrastructure, if you will. You need that assembly line. And we'll see a couple of slides down. Like I said, the idea here is that you want to take code change or your configuration change, whatever that might be, and put it into production readiness right away. And the only way to do that is continuously integrate into the main trunk. Yeah. And test it. That includes security testing, right? I was going to ask you about that because I don't see security up here. So I think testing there includes the security pieces of it. Okay. And you find that, you know, it's not just unit functional performance testing, but security testing is a huge concern. And often, you know, believe it or not, even today, security is still an afterthought for a lot of companies. They want to shift lift. They get it, but it's not an easy process today to do. So they'll often find code is ready for production, except it hasn't been security tested. You find, you know, the bugs and it goes back to the drawing board. So testing does become, you know, we call it verification or testing. It is still like the most critical thing and people, you know, don't want to go to production without making sure everything works. Absolutely. Ashish, before we go further, I wanted to just mention someone already asked in the question section. This webinar is being recorded. The slides will be available. We'll have them up on devops.com and devops.tv, usually within 24 hours. So hopefully that answered your question and we can move on. Absolutely. And so if you look at these findings, they were pretty interesting too. So, you know, we tried to ask teams to self-assess themselves as whether they were high performing teams or low performing teams. And then correlated them to other questions that we asked them. And there's a stark difference in the thinking and the performance of these teams, right? And whether this is because of the tooling they have, because of the culture that they have transformed, but the teams that can go faster, work on smaller pieces of code, get them out of production quickly, i.e. do devops well, we're finding out that they assess themselves as higher performing teams. And if you look at the characteristics underneath it, they validate a lot of that, right? So, you can see the project expectations, requirements, what you're going to do, how are you going to do it, how are you going to deliver are much better understood by these teams than those who struggle to take the ideas and transform them into production, right? Or production readiness. You see that, you know, if you look at, I'm given realistic deadlines, no deadline is unrealistic if the team performs well, they know what they can deliver at what point and, you know, what is realistic or not. The whole thing is the work is broken up in smaller chunks. The work is, you know, getting to the end really fast. And if it doesn't work, you can roll forward. They actually even end up taking higher risk, higher risk, higher reward, because there is no risk actually, like you can roll forward. You know, when I looked at this slide earlier, she, I'll be honest, I was surprised that the difference between lower performing and high performing was as close as it was, right? And I'll tell you in one area is I thought that. Product expectations and requirements set up front. Of course, you're gonna see disparity, I think, between low and high. But I was surprised that even in the lower performing organizations, 83% are responded, still said their ideas and opinions were valued. 83%. Now, 88% in the high performing set, so. But 5%, it's not a big delta there. It's not that big a delta. It goes to show you that whether high performing or low performing, engineers, ideas and opinions, these people feel valued in terms of that their ideas and opinions are. Even felt set up to succeed. I mean, I've been working with engineering teams for 20 plus years. In the lower performing ones, in the grumbles, you usually say, oh, I'm set up to fail, right? I have too many deadlines, too many deadlines, too much code, we have to push it to bigger features that too ambitious, a release schedule. Right, and again, numbers were fairly close, you know, with the kind of thing. But now we get to the last two, and I think the old patterns rear the heads, right? Right. I'm given realistic deadlines, right? I was impressed that 57% of even the low performing guys or folks was 25% of women. 57% of those people, you know, agreed with that. 70% in high performing, and that's a big number right there. I think it's, you know, they're correlating back to the deadlines that they get and how successfully they deliver them because project deadlines always get pushed out. And so there's this, you tend to forget that, you know, this was due to one scenario. We really blew it right. Phoenix Projects. Exactly. Two years ago, but we're still on track. We're on track. The deadlines have moved. But, and then the last question to me is the money shot, right? I rarely need to sacrifice quality to meet a deadline. Said no developer ever, right? Because they all sacrifice security testing or something. But again here, in the under performers or lower performing, 40% disagreed with that, meaning that they do sacrifice quality to meet a deadline. They do, but I think even like maybe, you know, the 40% and I'm, you know, we didn't double click in here, but you're trading something off. Yes. So maybe you're not sacrificing quality, but your deadlines are. Maybe you pushed your deadline out. Or the resources of the budget have gone out. Or maybe you cut scope. That could be too. You're right. Interesting. Interesting slide. Interesting results. And then we kind of double clicked into, where is it that it makes a difference for these teams who do well, right? And we found that removing roadblocks, removing like it says here, you know, the blockers in the development process, it starts with continuous integration as we had started talking about, right? And if you were doing continuous integration well, and you were automating that portion of the life cycle in the process, as well as, you know, other pieces in the process, in the life cycle, we saw that there made a huge impact in removing bottlenecks and kind of automating the process. I think it goes back to what we were talking about. You got to ship or get the code or, you know, the configuration change, whatever you do, production ready right away. The more you wait, the more you pile it up, the harder it becomes. It's sort of like accumulating debt. It is like accumulating debt and then having to sort of sort all of that out at some other point in the, in the life cycle. Yeah, yeah. I, before we move on, I'm sorry, just quickly. So, you know, I think our folks online here looking at this, look at it and say, yeah, that's pretty self-evident. Of course, doing continuous integration alleviates blockers in the process down the road, automating more is a top priority. Now, it says it's a priority, doesn't mean that they've gotten there. How successful, that's what I was saying. It's a top priority, but how successful are we at it? You know, you're talking to someone who comes from the security field and I haven't read a security report in 20 years where security was not a top priority. And yet we still have more breaches than ever. So, you know, there's an interesting disconnect there sometimes. So, we also asked, you know, just what we were talking about just now. Yes, you know that it's a good thing to do. How well do you think you did it? Are you doing it today? And it's interesting, you know, it's only about 15 to 20%, you know, saying we do it between very good to excellent. So, there's a lot of scope to actually increase and get better, you know, at continuous integration. So, we also asked a question about how does your tools here look like? You know, where are you struggling with this? How many tools do you typically use to, you know, do DevOps or even deliver software? And we found these interesting, right? These interesting findings. One was that they use a number of different tools that they put together. They would choose, you know, use open source, proprietary software, whatever they use, inbuilt at home. But they spent a lot of their time actually integrating these tools, right? That third box in there. And that was interesting because would you rather, would the organization rather have you work on delivering the next feature that can bring in more revenues or actually save costs? Or would you rather have them integrating? I know it's cool to integrate tools. You know, it's cool to kind of like bring these together. But the value of these developers, a highly expensive resourceful, you know, resources is better spent actually building the software. The other thing which we're all familiar with today is context switching. If you're using different user interfaces, you're using different tools. Yes, you know them well. Every time you take your attention off of one task and one tool and switch to another one, think about between your email and your Slack and your phone and, you know, like...  So it's really a productivity hamper. So let me ask the obvious question, right? And what's the answer here? How do we reduce that complexity? How do we reclaim that time, right? How do we become more efficient here? So let's dig a little bit deeper into this and maybe, you know, we get into that. What we're finding out is people are starting to choose tools that best help them, right? And though, you know, we're an open source company, we keep asking the question and we're finding that open source tools are becoming a very critical component to how developers choose to solve their problems. And the difference is one, the pace of, you know, innovation, the velocity of innovation and using the right tools or contributing to things that they want, they're not in there is a lot more with open source tools, right? So people are starting to look at tools that they can integrate with their stack that makes their life easier, that they can modify or contribute back to, they wanna be recognized as well. And so they're starting to turn into, you know, tools that are malleable, tools that they can use, that they can understand what's underneath the hood. And, you know, the hidden part of this is that there's a good community around it because as they face their problems, they can ask their peers or they can help their peers. So, you know, that's one of the things we found out. Yeah. We're also finding out that there is more and more propensity to try to use fewer tools if I can. Yes, I want the choice of my tools, but I don't necessarily wanna integrate six different, you know, tools because it's not just learning six tools or it's not just these context switching. Now I got an upgrade in one tool. I gotta make sure everything works. I got a patch coming in. I gotta make sure everything works. I mean, Ashisha, we recently did a sort of a snapshot of the DevOps tools market here at DevOps.gov. And most of our eBooks are eight pages, six to eight pages. This one came in at 72 pages for exactly this reason. And just about every category of the stack, there is such a wide choice of tools that, you know, I imagine being the person on the other side of that book trying to pick tools saying, what do I pick and do I really want more than three or four? Do I need 12 different tools in my software factory? And I have no control on the roadmap, so please, right? No, and they don't necessarily talk to each other.  I've spent 10 plus years in companies like that. You can't even get the UIs to kind of look between one functionality. It's a hard job. It is, and again, put yourself in the shoes of the people who filled out your survey, right? And it's a daunting challenge. It is, and though this was focused at the developers and their managers, I mean, I'll ask you, but you know, my experience with even the highest level decision makers and IT organizations, they identify with this. They want the right technology we to use. They don't want to waste resources integrating these different tools all the time. They don't want things to break down, right? They want the ability to modify the tools for their own use, their own usage. From that perspective, you know, throughout the organization, these challenges remain the same from a tooling perspective. I agree, I agree hard. So here's our summary. So we talked about all of these things from the findings. What do you think? So, I mean, let's take each one of these and then sort of give our finishing touch to each of these points. So number one, there's obviously, I think a difference of perspective between managers and developers, but you know, digging in one layer deeper, is it that one is more optimistic than the other? Is it that they have different views of what the world is, right? It's sort of when I walk my dog, I constantly try to remember that she's only seeing things that are three feet off the ground, she doesn't see up. Not to equate developers to dogs or anything, but they have a very, you know, their worldview is what's in front of them and managers depending on organization and have another worldview. So I think it's important that we try to rectify those and equalize those views, right? There shouldn't be such a big disparity. I think that's when communication becomes important, right? You make sure we're all on the same page here. What do we think is this working, that working? And I think they need to find a way, I mean, people still struggle, you talked about it at the beginning to understand those metrics that are common between these two roles, right? So I might have tested faster today, but didn't make an impact overall to the cycle time across the organization. That's maybe a metric what the manager is interested in. Right, right. So it is important for them to start looking at the same data and trying to understand where they agree and disagree. Agreed. So then, you know, bottlenecks and pain points in the software lifecycle. You know, I think testing was probably the biggest one we saw here and that included some security. You know, I think we could all rally around that, right?  What is the definition? And what are we trying to do with all of this agile and lean and all of that? I think at the end of the day, that right there is a key piece of it. How do we reduce these bottleneck pain points? How do we make us go faster with better quality, more security? A lot of that is also, you know, coming from the fact that even though we talk about DevOps bringing the teams together, the reality is in large organizations, especially, there are organizations based still on functions. Yeah. And you can't just toss them up in the air and say, we now suddenly have smaller DevOps teams working together. Some people do it better than others, but they're again, you know, smaller organizations within these huge organizations. So as you still work side load, work with different tools, work with different processes, work with different cultures, and they have handoffs between, you know, these pain points get exaggerated, right? They get amplified. Agreed, agreed. A quick word on high performing team versus lower performing teams. To a certain extent, it's relative. What is high performing to you may not be high performing to me.  Not everyone goes to college. That's okay. But I think we have to ensure is that even the low performing teams have access to what they need to succeed. And at least know of a pathway to become higher performing if they so choose to do pursue that. Let me give you an example here that might actually bring this point home. So first, these were self-selections, right? Mm-hmm. But if you really look at it, I've been with customers to whom when you paint the vision of what DevOps can really do, which is at the push of a button, you know, you can deploy code within minutes. They say, not really looking for that. I'm happy with bringing down my deployment cycle time from nine months to six months to three months. And that's huge. And that's huge for us. And we are good with that. And therefore, you know, I wouldn't equate them as higher or lower performing teams. But think about a company that's satisfied by deploying every three months. That's the business requirement. What if there's actually security patch? What if there's actually something that goes down that you need to fix? Your cycle time should support an hour, right? So you want to enable all of them to be able to perform at a high level and then choose the cadence that they want to go at. Got it. I don't disagree at all. Toolchain complexity is absolutely can be a drag on innovation. I'd like to throw another drag on there in a similar vein though, Ashish. And that is, we have such a plethora of tools. We also have a plethora of languages and infrastructure. In a lot of ways, today's IT world is a tower of babble with all people talking different languages at different speeds and so forth. And that is something we probably, you know, I always thought of IT as a universal language. It's ones and zeros, it's bits and bytes. But it's not, you know, in real world, that's something we need to work on. Absolutely, that complexity you mentioned is something that really frustrates people, right? It's the choice of platform, it's the languages. It's bringing all those tools together, those languages together, those platforms together. It really, you know. Absolutely, absolutely. You know what, we've got some time though. Let's do a company overview maybe people who aren't familiar with GitLab. Thank you for that opportunity. I mean, I'll take a couple of minutes, but you know, all the problems we talked about, I think, you know, GitLab has had a unique approach in solving this. We started out as a Git repository, quickly built a CI engine, and then quickly realized like, you know what, why do we need these different tools to do these things? So we built one application that integrates all of these workflow functions in there. And if you think back about this, right, it's a single application for the complete application or the life cycle. With one installation, actually, you're looking at what one user interface, one data store, you're not integrating tools and allows people to start collaborating together on the project. So the extreme left shift that you need, that's what we allow really better. And it's an open architecture. It's an open source architecture. You can integrate other tools that you're completely using. The interesting part about this is, we have more than 1,900 contributors on the open source community. And every month on the 22nd, sorry, every 22nd day of the month, we release and we actually deliver functions and features that our customers are asking for. And we have sometimes our own customers contributing to this. So it's a really like fast-paced innovation. Before you get into the obligatory customer slide, I wanted to mention something with this. So number one, can you go back one more slide? I'm sorry. So when we look at this, the single application for a complete DevOps life cycle, what I think is a real plus for GitLab is because this entire assembly line, if you will, this entire factory is open source through Git, through GitLab, you can adopt any one or all of these pieces, relatively low cost initially, right? Look, there's a- It's free, in fact. Our community- It's free. There's a total cost of ownership in open source as well, right? You don't pay for the software, but there's other costs. But it's a rapid adoption, right? It's much easier to just download it. And that's what developers love about open source. We could download, adopt this, download, put it in, and I'm doing it this afternoon. Actually, you can go to our SaaS-posted version, create an account and get it out of there as well. And do it there as well. Drop your code. What I didn't talk about here is the feature we have that's coming out, it's called AutoDevox. So you drop your code, we'll recognize the language. We'll actually build a pipeline, we'll do the tests, tasks, tasks, everything, start monitoring it, and it's done with the next. That's a beautiful thing. Now, in real life, unfortunately, we don't have green fields, we get brown fields. And people may have already made an investment in one of these waystations along the factory floor, if you will, along the assembly line, the pipeline. What's nice about an open project like this is if you are already using something, you can still use the rest of the GitLab because of the ability to integrate. Absolutely. And that's what we have taken an approach, is we don't expect you to rip into place. Right. We don't expect you to start using all the functionality right away. So we've had customers who were using competitor products in each one of these areas, but they found this approach very, very, kind of useful, very good. They started on, either maybe they started on the CI part of this, or they started on the repository part of this. Some of us, some of the customers are adopting us because they like the testing and that's built in, container security testing, all of it is built in. And as they get more of their practitioners onto this, they're realizing, okay, the more functions you adopt along the line, the faster your cycle time drops. And so, each organization's own pace and the needs that they can adopt this. Agreed. And that, I've told you this as she's talking privately. To me, that's the real attraction of GitLab, right? When we look at the breadth of the offering, the breadth of what you guys can help with, right? But the ability to pick and choose what you want to. So it's not an all or nothing, but yet there's plenty to the offer. Yeah, absolutely. And if you wanna do fresh projects, greenfield projects like you talked about, there's not much you have to do to get started and deliver. Absolutely, I agree, 100%. All right. We talked about this, I mean, the adoption in the market places is tremendous, right? I mean, all of these organizations are using this. So I wanna leave some time for questions and answers that you might have about it. All right, I don't see any questions in this second in the queue, but let me, I always have questions. So if you don't mind, is she? So let me ask you this, what's next? You mentioned, what do we call automatic DevOps? Auto DevOps. You know. We're using it next month, we're going GA next month. It's already available, we're going GA next month. So let me just get it straight. I drop code in, you recognize the language based upon that code, you build my CI pipeline. CI CD pipeline, all the way through. We run the tests, include static tests, dynamic tests, you know, the normal function unit testing and anything you've integrated with this. It configures it and deploys it. Wow. And it starts to monitor it. So we have a Prometheus integration built in. Really? Yes. How long have you guys been working? This had to be something you're working on for some time. So I think it's been a few months we're working on this and one of the reasons that amazes me and surprises me even after I joined the company and this was amazing to me before I joined the company was talk about a vision and what we want to do and it's there in a few months, three months, six months like this whole complete end to end DevOps lifecycle. I think it was an vision last year. Wow. And by the end of this year we would have completed that vision. And the reason is very simple I think, you know like we get input from our users. We get contributions from them. We get contribution from them. We can't do it all alone. And then we have our own in-house team, right? That builds this tremendous velocity. Yeah. But again, I think you can't have that velocity. The velocity goes hand in hand with the model here. Yeah. Of having that distributed thing. So is that the ultimate, not solution but the ultimate goal to do this automatic or DevOps automatic kind of thing like that you think? I think it was beyond that but right now we're kind of focused on delivering this. This was our vision for 2018. The good thing about a platform or a project like this is as the market needs change, what we hear, what our customers want we gravitate towards that and solve that problem really quick. And so a lot of our customers when they're scared of vendor lock and we're not really a vendor, right? We're a partner and it's a project that you share with us. So it gravitates towards solving the problems that you need to solve. Got it. Excellent. And then, so beyond this project, is there anything else you can tell us you guys are working on? That's coming. But I think in the short term I can share that look we've built the breadth of this product really, really fast, really well. And we continue to build the depth in each one of these functionalities, right? And we are at a point now for example with the acquisition of gymnasium and other open source projects contributing. We're looking at further security you know kind of integrations from open source projects. Now I'm having conversations with industry experts and they're saying this is by far already starting to change the face of DevSecOps while we're approaching this. And so looking at particular use cases like that and building the depth is you know also something on our radar. Absolutely. So you mentioned DevSecOps near and dear to my heart. Talk to us a little bit about what you know what are you guys specifically doing around the DevSecOps piece of this? So look we have, I mean other than you know built in SAS, DAS, container security all of that. The approach. That's not a small value. It's not. It's not. We did that before we went to bed tonight. But that's a big job. It's a huge thing, right? But I think the fundamental approach here is everybody realizes that security testing needs to shift left. Anything that you catch in security after the fact much more expensive, much more harder to fix. And though everybody theoretically understands that you need to start at the same time you're developing a planning code or writing code it is hard to do. So with our approach what we've really done has made that vision a reality. Because as soon as you open an issue as soon as there's a merge request you see everything on that same UI that's related to security. And it starts to build with security in mind and goes through the testing. And everybody has the same UI to look at. Everybody has the same, I mean all the pairs of eyes are looking on that merge request as it goes through. That's more of a cultural and organizational change that is hard to drive in an organization. And that's what we actually enable to do. I know I trivialize the functionality of what we do but that's the easy part to solve, right? How do you like fundamentally shift teams to work together from a cultural organizational perspective? I think this tool allows it. You may not have this info but in this survey of 5,000 some art people would be responded. Do you know what percentage of them considered themselves security people? I do not have that at the top of my head but there's a link at the end of the deck that points back to the survey. And it's an open survey, right? It's not good, you don't have to register. You can go and read through all the findings on that. You know, we'll put that link in when we post the recordings and slides. So we'll make sure we have that. So if we don't have any questions then, we can wrap up this webinar. Thank you very much for giving us a great look at this results of the survey. A good update on where GitLab is. Bunch of links here for our listeners and people may be watching this on YouTube after the fact, these links work fine and you can click on that. And we hope to have you soon on another webinar. Thank you for inviting me and this was- It's our pleasure. This was great. This was good fun. Yep, Ashish Kuthiala, Director Product Marketing at GitLabs. And this is Alan Schimmel for devops.com. Thanks for joining us on another devops.com webinar today and we hope you all have a great day and we'll see you soon.


So let's solve the equation 2z squared minus 13z plus 24 equals negative 8z plus 30. So the first thing to notice is this equation has a z squared in it, which means that this is a quadratic equation. And since this is a quadratic equation, we'll use the quadratic formula. Now the owner's manual for the quadratic formula does require that we have our equation equal to zero. And so for our first step, we need to get all the terms onto one side of the equals. So now our equation is in the form it has to be to use the quadratic formula. So let's copy down the formula. And we can read off our coefficients. b is negative 5, so every place we see b will replace it with negative 5. a is 2, so we'll replace every occurrence of a with 2. And c is negative 6. So we'll replace c with negative 6 everywhere we see it. And we'll do some arithmetic simplification. And we have our exact answer in radical form. Well, almost. Remember the plus or minus in the quadratic formula means we actually get two solutions. So our actual solutions will be 5 plus the square root of 73 over 4 and 5 minus the square root of 73 over 4. Now when we enter these answers into my open math, we'll need to be careful that what we're typing in is what we actually want. And here it's very important to watch the preview because the preview tells you what you've actually entered as your answer. Well, so our answers are 5 plus the square root of 73 over 4 and a comma to set off the second answer, 5 minus square root of 73 over 4. And if we look at the preview, we see what we've typed is not what we wanted to type. And that's because this expression 5 plus square root of 73, 5 minus square root of 73 is the numerator of a fraction. So we'll have to enclose the numerator in parentheses. No, that's the entire fraction. We'll fix that. We'll put the numerator in parentheses. And only after you've confirmed that what you've typed is what you want to type should you hit submit. And since the preview shows the answer we want to enter, we'll click submit. Now there is another option if you don't want to wade through the sea of parentheses. In the questions where an algebraic expression is expected as an answer, there will generally be this yellow up arrow when you click inside the answer box. And if you click on this yellow up arrow, it will open up a math formatting window. And we can use this to enter our answer exactly as we want. So the answer is a fraction. So let's hit the fraction button. We'll type in our numerator. And for the square root, we'll use the square root button. And we'll finish entering our numerator and denominator. Since the only difference between the first and second answer is that one of them is plus the square root and the other one is minus, we'll just copy and paste and change that plus to a minus. Once we're done, we'll hit save to enter the expression into the answer box. And we can press submit once we're sure that what we've typed in is what we wanted to type.


Hello, this is Laptop Media, and today, we will show you how to open the Dell Latitude 147420 and what's inside of it. Before you remove the bottom panel of this laptop, you should remove the SIM card tray. Then, undo all 8 Philips head screws, and pry the panel, starting from the hinge gaps. Please remember, it would be of great help to us if you just hit the like button and subscribe to our channel. That would motivate us to make even more and better videos for you. The first thing we see inside is the battery pack. This model comes equipped either with a 42 Watt-hours unit or a 63 Watt-hours one. Unfortunately, the memory chips are soldered onto the motherboard. On the bright side, the available configurations include 8, 16, or 32 GB of LPDDR4X RAM, all working in dual-channel mode. Storage-wise, there is 1 M.2 slot, that supports PCI-EX4 drives. As for the cooling, the temperatures inside are managed by 2 heat pipes, which lead to a side-mounted heat sink. If you'd like to see more disassembly videos of the latest notebooks we would highly appreciate if you hit the like button and subscribe to the channel.


Hello and welcome to the session. In this session we discuss the following question which says explain an isosceles triangle is symmetrical about the bisector of the angle included between the equal sides. First we recall the definition for linear symmetry a figure is said to be symmetrical about a line it is identical either side of the line. This is the key idea that we use for this question. Let's see the solution now. Consider this isosceles triangle PQR with the side PQ equal to the side PR. This angle P is the angle included between the equal sides PQ and PR and we have taken this PS as the bisector of the angle QPR. So we have to show that the triangle PQR is symmetrical about the line PS which is the bisector of the angle QPR. Now if the triangle PQR is folded along the bisector of the angle QPR that is PS then the triangle SQ coincides exactly with the triangle PSR. Thus we can say that the triangle PSQ is identical with the triangle PSR so we say the isosceles triangle PQR is symmetrical about the bisector of the angle QPR which is the angle included between the equal sides of the isosceles triangle. So this completes the session. Hope you have understood the solution of this question.


Hi there! I'm Sandy Allnach, artist and paper crafter here on YouTube. I'm going to talk about scenic storytelling avec les chats et les chiennes with the cats and dogs. And I'm going to show you some new stamps. Top Flight Stamps is a new retailer and they are focusing on something very exciting that nobody else has because getting stuff from overseas is difficult here in the United States. So they have collected a lot of brands all in one place. So I'm excited to see what we are going to be influenced by now since we have stamps from around the world that are much more accessible to us than they have been in the past. So these are just a few of the countries that you might see on their website. They sent me some stamps to play with today in this little treat package. Very excited to receive goodies sometimes. And these are from Catzel Craft Stamps in France. Which is why this whole thing is going to have a little bit of a flinch type of theme to it. I'll tell you more stories as we go. But these have been around for a number of years for quite a long time. So I have heard rumors of them and here they are in my house. Very excited. She also sent me some easy mount which you can get in a lot of different places. I don't see it on her site yet. She may end up carrying them. I don't know. But you do need some easy mount with these because they are rubber stamps without a backing on them. So they're not going to stick to anything. I am going to show you how to do this. I'll give you some quick tips and then we'll get into some storytelling and coloring and card making and all that stuff. This easy mount stuff has two sides to it. One is really super sticky and that's the side you want to put your stamps on. And what I do is cut off some extra pieces because I wasn't sure I was going to have enough. And so I saved that little piece with the paper protector on top of it because this stuff is really sticky and then just trim around each of the stamps. How close you cut to the stamp depends on how good you are at inking because if you leave a lot of room around the stamp you could get ink on it. You could also end up with points if you don't round your edges that sort of thing.  But if you peel it off then you're left with a backing that's going to stick to your acrylic blocks and then these are just regular old cling stamps. So I keep mine in stamp envelopes just like I do everything else. So for those who are going to ask that's what I do with mine. You can also put them in different kinds of thick like video DVD cases types of things. Now another way that you can do these this cling mount without wasting a lot of that extra space. There's a lot of that extra rubber in between is to trim these out.  Eventually and that that way you're going to be able to snug these up and make a little puzzle piece out of them.  And there's that whole big section up there. I'm going to cover that up with the paper again and save it in case I have little stamps that need it. And I ended up actually meeting it when I was doing the accessories. So here we go. We're all done. But some of the stamps sometimes will retain a little bit of sticky around the edge when you cut out with this easy mount because it is seriously sticky. If you have that as an issue then just take your embossing powder tool whatever kind you have and run it around the edge and that will take the sticky off. So that is the little short quick primer on using your cling mount easy mount. There's a lot of different brands out there. I'll have some links of course in the doobly-doo because that's what I do. And I'm just going to sit here and color not putting colors up and everything because I thought I just do some storytelling instead because we're going to get to the cards that I make out of these. I did do my stamping just on a half sheet of paper in my Misti so that I could stamp a couple sheets and then have lots of kitties and doggies. Just to color over time and that's what I did. I'm coloring on Nina cardstock but you can watercolor on these. You can do all different kinds of things, whatever kinds of coloring you wish to do. Now I do not know why there is a bottle of nail polish sitting right there in the corner. But since you probably want to know now that I called attention to it, it's 400 Royal Flush is the color number and it's Revlon's Color Stay Gel and Bee. There you go. That's the color I'm wearing today. I don't know why it's in the camera. When you call things out, then they disappear. People don't think about them, right? OK, so storytelling. I was in college a French minor. I had taken a bunch of French in high school and did very well at it. So I thought I would be a French minor. I didn't finish the full French minor, but I took a whole bunch of years of it. And for a long time, I was actually thinking in French, not all the time, but I was translating things in my mind in French and things would come out of my mouth in French weirdly. Just random random things. I eventually slowed down on doing that, but I still do it with my dogs to this day. Every once in a while, if I think of a French word or if I'm saying something to them that I know how to say in French, I do so. I will not torture you with my bad French accent, but there you go. The names of these two sets, by the way, are Les Chagruces, the Russian cats, and then these are just the dogs, Les Chiennes. They also have jungle animals. They have birds. That was their first one a number of years back. So you can check them all out in the top plates store. And then these are the funny accessories that they have. So you can add hats and glasses and all sorts of fun things to them. And what I did was after I finished all this coloring, I trimmed everything out. That was quite the beast.  You could do that this way, the way that I'm talking about doing trimming your images out, or you could stamp them in a scene by doing masking. This time, I'm just going to stamp them and glue them down on top of the scene that I color. So we're going to go through that for each one of the cards that I made to go with this set. So here are all my finished images and then I sat in front of the TV set and just trimmed, trimmed, trimmed so that I could arrange them into groupings to put on cards. And this first one, this cat looked like he was grumpy looking at the alarm clock when I saw those two images together. So I drew a bedroom scene. It's in very soft colors. I drew a little kind of quilted blanket that he's sitting on. I had an extra hat after setting up all the other scenes. So he's got a hat hanging off bed post. And with the clock, I ended up putting it on an angle so it looked like it was ringing and then just adding lines around it, both with markers and then with a pen to just add a little bit of detail to it. So that is my sleeping kitty. He's so funny. He looks at the clock the way I do when it goes off in the morning. Next up, we have the birthday scene. This was one of those where I just took a whole bunch of the animals. I tried to see which ones might stack up well on top of each other because a birthday party seemed good and festive for a lot of imagery. And this would have been a lot harder to mask because there's so many layers and so many things in front of each other. So trimming them out and gluing them down on some instances is going to work out a lot better for you because you don't have to do all that fussy masking. And then you can just play with the images and kind of tilt them at whatever angles you need them at. And I just put some carpet and wallpaper behind them to give them a little bit of a scene to sort of set them in a place.  And I thought, wait a minute, if he's riding the scooter and he's facing backwards, he is too cool for school. So he has to have glasses on. And if he's going to have glasses on and ride a scooter, he's going to be on the boardwalk. Because where else would you find a dog with that much talent except on the boardwalk? So I drew the boardwalk under him, some really far distant, with really light colors, seeing of the ocean and the sand and the clouds and stuff in the background so that all the focus is on him and the foreground. Next up we have some kitties who are going to, yeah, steal the ice cream off of the table. I was trying to figure out what these kitties might be doing and I laid them on my card and sort of figured out they might want to steal some ice cream.  It was going to be a frame behind them, but it looks almost like a window because I was trying to put a nondescript painting in the frame. But it could be a window outside as well. But how is that for like a cute little card that would look like something you could send somebody and say, hey, treat yourself. You deserve something special. And this one is for the cat of gloom and doom. So if you know somebody who needs a guard like this, it's a perfect one. There was this grumpy looking cat and an umbrella and they just seemed to go together. So I did the background with just a whole bunch of swipes of Copic markers. There's a lot of flicking. The ground is horizontal and the sky is vertical and less color, of course, on the inside of where the umbrella is blocking off the rain. So that he just looks like he's kind of semi-protected, but he's not happy at all, right? That is, some days, that is my attitude totally. And I know a lot of people who could use a card like this sometimes. And the last one is kind of the crazy fun one. There is this signage 1, 2, 3, and I'm assuming that that is like a train station kind of sign. So I drew two pillars in the distance back there, which you can't see because I put so many dogs in it. The distance is like a little sign of a train.  I don't really know why three dogs would be going by themselves, but they do have a suitcase. So they've got all their stuff packed. I'm pretty sure they have some toys in their suitcase. So you have a bunch of stamps trying to see what kind of a storyline you could make up for them. What kind of a scene can you put with them? It might be something really simple. It might be something complex, but it's a whole lot of fun to tell a story in a picture like that. If you haven't yet subscribed to my channel, you can do so by clicking on my face. You can watch other videos. There's a Copic class linked here on the screen and you can check that out if you're interested in more Copic coloring. And click on the link in the doobly-doo to go to my blog to get hooked up with top flight stamps for the blog up. And I will talk to you guys later. Bye-bye.


and I'm just a little bit more worried unspoken double the pump just if I could stay living that high I'm just a little bit more worried unspoken double the pump just if I could stay living that high


Hi friends, I am Purva and today we will discuss the following question. In what ratio does the line x-y-2 is equal to 0, divide the line segment joining 3-1 and 8-9. Let us begin with the solution now. Now, let the required ratio be ks to 1. Now, this is the line x-y-2 is equal to 0 which divides the line segment joining the points a with coordinates 3-1 and b with coordinates 8-9 in the ratio ks to 1. And the point of intersection of the line x-y-2 is equal to 0 and this line segment a-b is p. So, the coordinates of point p which divides the given segment a-b joining the points a with coordinates 3-1 and b with coordinates 8-9 are. Now, the coordinates of the point p which divides the line segment joining the points a with coordinates x-1, y-1 and b with coordinates x-2, y-2 in the ratio ks to 1 are given by k into x-2 plus 1 into x-1 upon k plus 1, k into y-2 plus 1 into y-1 upon k plus 1. So, here the coordinates of this point p which divides the given line segment a-b with coordinates 3-1 and 8-9 in the ratio ks to 1 are given by k into 8 or you can say 8 into k plus 1 into 3 which is equal to 3 upon k plus 1, k into 9 or you can say 9 into k plus 1 into minus 1 which is equal to minus 1 upon k plus 1. Now, since this point p lies on the line x minus y minus 2 is equal to 0, therefore we have coordinates of this point p satisfy the equation of the line x minus y minus 2 is equal to 0.  Or you can write this as 8k plus 3 minus 9k plus 1 minus 2k minus 2 is equal to 0 or you can write this as now 8k minus 9k minus 2k is equal to minus 3k and 3 plus 1 minus 2 is equal to plus 2 and this is equal to 0. Or minus 3k is equal to minus 2 or you can say k is equal to 2 upon 3. Therefore, we have the required ratio is 2 upon 3 is to 1 or you can say 2 is to 3. This is our answer. Hope you have understood the solution. Bye and take care.


Well, what's happening is I'm here in Austin for the Paleo FX convention. It's been amazing. This is the third day, thousands of people showing up for this. It's really impressive to see what's happened to the Paleo community and how it's grown and how it's flourished and how not just the people who are attending, but the vendors. That's really what I find most fascinating is the fact that we're creating basically a marketplace now with products and services that cater to specifically to a Paleo lifestyle. Yeah, yeah, yeah. No, man. It's crazy. So Paleo FX started four years ago in Austin and it was small and you were at the first one. Yeah. And like now it's it's huge if you guys have not been there. In fact, I haven't attended. Actually, I have a press pass, but I didn't get it. I was here interview, but but no, man. And it's just nuts because it's this huge cultural phenomenon. But you actually started like this movement massively, you know, actually the Pramble blueprint, which we see right here. How have you seen Paleo change and evolve over the years? Yeah, it has evolved. You know, it started really well before I got into this through the likes of some of the people doing work in in the 80s. Mel Connor, Boyd Eaton wrote some of the first books really looking at the Paleolithic diet. Lauren Courdain came in in the early 2000s and started looking deeper into that. It was one of the impetus that I used to change my own diet. And I'd gone down this route where I started to be accepting of healthy fats. The concept that less exercise is probably an appropriate lifestyle for me. I looked at a lot of these different hunter gather experiences and the last thing to fall into place for me was elimination grains. And I got a lot of that from from the guys I just mentioned. So I started writing about this in 2006. And that's when I started my blog. I started to write and I figured I'd write every day for a year. And at the end of the year, I'd have written everything there is to say about life and diet and exercise and health and fitness and whatnot. And of course, that wasn't exactly an accurate statement because at the end of the year, I just started digging deeper and deeper into these nuances and these different paths that we could explore. And so it became Mark's Daily Apple. And and you know, when you say, you know, you credit me with with having advanced this movement, I'd like to think so. I'd like to think that that my blog has taken what other guys have done and kind of brought it a little bit more mainstream. I pride myself on the way I write and the ability to take complex scientific ideas and translate them into a way that appeals to the mainstream reader who wants to just like get the nuggets, give me the information. Just tell me what I got to do. So you touched on some of the the Boyd Eatons of the world who were kind of preceding you. And I can even think of back in the early 70s, I got my name of Stefan Boyd, an Australian, you know, human ecology writing about this stuff. And yet, there seems to be a lineage at least 50 years talking about this stuff, if not even earlier to the early home economics, was there's a grain in there. There's a German there about like, here's the stuff you do in your life and home and sleep and some of what you even dig backwards, even further into with the primal connection. Why is it seem like it's so hard for people to get on board with this idea? Because it's not like it's not like you're the first person to say this. That's exactly right. Right. I mean, and there's an whole academic discipline dedicated to this stuff.  And I'm trying to put them into a framework that is accessible to the average person. So yeah, these are these are concepts that we sort of intuitively all get. Yeah, we should be eating real food and not packaged food. We should probably be getting, you know, enough sleep, we should probably be going to sleep a little earlier and not waking up to an alarm clock. We probably should be getting more sun and playing out in nature and digging around the dirt. But you know, we're fighting that whole movement is this science and technology and advancement in, you know, interactive digital technology and all these things that are sort of taking our minds that are hardwired to be hunter-gatherers, taking them in a direction of short attention span. You know, Instagram and Facebook weren't enough. Now it's got to be Snapchat.   So the concept of fast food kind of flies out the window and yet society is pushing fast food on us. Here we are trying to encourage people to spend time face to face. I'm hanging out with you guys. This is awesome. We're looking at each other.  It's so while we're hardwired to extract the greatest amount of pleasure out of life, sometimes we perceive that pleasure as being instant gratification. And so I'm just trying to tell people, look, let's just really if we're here to experience joy and pleasure and contentment and fulfillment, let's figure out ways that do that that resonate with our genes that resonate with our hunter-gatherer brains and that don't rely on digital technology, but but you know, cause us to have to go back to face to face communication, real food, getting sleep instead of figuring out hacks so that we don't have to sleep. You know what I mean? Yeah. The whole biohacker community is kind of funny, right? Because I think I think we have gone so far off the path that we need hacks to kind of grease the skid to get us back to where we should have been in the first place.


10 Biggest Solar Projects in Africa Africa is a leader in the development of renewable energy. The continent's availability of renewable energy resources, like its solar photovoltaic and concentrated solar power, CSP, has given it the opportunity to offer utility-scale electricity to the over 600 million people who do not have access to reliable electricity. Nor Africa's largest solar project is located in Morocco, whereas South Africa is home to eight of Africa's top 10 solar plans. By installed capacity, power technology has compiled a list of Africa's largest operational solar installations. While we hope you appreciate our work, please give us a thumbs up by clicking the like button more, better yet, sharing, subscribing and turning on your notifications for new videos. Join us on a little excursion today as we look at the top 10 solar projects in Africa. 10. Calpolt Solar Plant 75 megawatt The 75 megawatt Calpolt Solar PV facility is located near Petrusville in South Africa's northern Cape province. The project, which was developed by Scatic Solar, was officially opened in November 2013. The Calpolt Solar Project began construction in November 2012 and was connected to the grid in September 2013. The PV plant is made up of 312,000 solar panels that are spread out over 105 acres of land. The Calpolt plant produces 135 gigawatts hour of renewable energy each year, enough to power 33,000 homes. It will also reduce greenhouse gas emissions by 115,000 tons per year. 9. SonicDix Presca PV Project 86 megawatt The 86 megawatt Mililo SonicDix Presca Solar Photovoltaic PV Project spans 125 hectares of land in South Africa's northern Cape province. In July 2016, the solar facility began commercial operations. Mililo Renewable Project Developments designed this project for Mililo SonicDix Presca PV in collaboration with Mililo Renewable Energy and Ixowave Women in Power, TAI. During its 20-year lifespan, the Mililo SonicDix Presca PV Project will provide enough electricity to 40,000 South African households via the ESCEM system. 8. Jasper Solar Power Project 96 megawatt Jasper is one of the most important solar energy plants in continental Africa, with a 96 megawatt DC installed capacity. The solar facility is located in post-Mesberg, South Africa's northern Cape province. Solar Reserve and its consortium partners Kinsani and Intikken Energy developed the Solar Power Project. The Jasper facility began construction in October 2013, and it became fully operational in October 2014. Jasper produces roughly 180 gigawatt each hour of renewable energy each year, enough to power 80,000 houses in South Africa. The facility generates 180 gigawatt hour of electricity per year, enough to power 80,000 South African homes, and offsets approximately 145,000 tons of CO2. Jasper has a 20-year power purchase agreement. PPA, with ESCEM, like many of the other solar projects mentioned. 7. Cathue Solar Park 100 megawatt The Cathue Solar Park KSP is a 100 megawatt MW. CSP project located in Cathue, South Africa's northern Cape province. In January 2019, the Solar Park opened for business. In Jai, Siak Community Development Trust, Public Investment Corporation, Larico-Medier Rape Fund Trust, Investec Bank, and the Cathue LCT Trust are the owners of the KSP project. The Greenfield project combines parabolic trough and molten salt storage technology, resulting in a thermal energy storage capacity of 4.5 hours. During the peak demand time in South Africa, it serves 179,000 households. With a capacity of 100 megawatt, Cathue is South Africa's largest solar park. The plant's construction began in May 2016, and it entered commercial operation in January 2019, with a 30-year operational life. The park is expected to cost $811 million and will reduce CO2 emissions by 6 million tons over the next 20 years. It has strengthened its environmental credentials by launching a program to protect endangered and vulnerable plant species. A total of 3,345 plants were rescued and transported to a safer location for growing as part of the initiative. 6. Alanga 1 CSP Plant 100 megawatt In November 2018, Center and its partners in Velo and Cobra finished commissioning and testing the 100 megawatt Alanga 1 CSP plant. Kerashuk Solar 1, RF. Proprietary owns the plant, which is located at Kerashuk in the northern Cape province of South Africa. There are 266 seen artroff loops in the Alanga 1 CSP plant. The plant's molten salt storage system provides five hours of thermal energy storage, allowing it to generate heat in the absence of solar radiation. Over the next 20 years, the solar power plant is expected to deliver clean electricity to about 100,000 South African homes while reducing CO2 emissions by 90,000 tons. 5. Xena Solar 1 100 megawatt Xena Solar 1 is a 100 megawatt concentrated solar power, CSP. Project developed by Ubingoa with an $880 million investment in paw fatter South Africa. In September 2017, the plant began commercial operations. The CSP plant uses parabolic trough technology and has a thermal energy storage capacity of 5.5 hours. The plant's parabolic trough collector is considered the world's largest commercial CSP project to date. The project is expected to produce around 400 gigawatt hour of electricity enough to power 95,000 homes while reducing CO2 emissions by 348,000 tons per year. 4. Solar power in South Africa A look at the country's solar plants. The Public-Private Partnership project, which was completed in March 2015, provides sustainable energy to South Africa's power company, Escom, under a 20-year power purchase deal. Ubingoa owns 51% of the project while the IDC and KAZU Community Trust control 29% and 20% respectively. The KAZU Solar 1 power plant has the capacity to provide clean, green energy to 80,000 South African households. South Africa used to support substantial nuclear power expansion as a solution to fulfill its expanding energy needs with clean energy, with the technology serving as the cornstone of its 2010 integrated resource strategy. However, by 2018, the ever-increasing expense of nuclear electricity had forced it to shift course. Its 2018 IRP calls for the addition of 5.7 gigawatt of solar electricity to the grid by 2030 on top of the almost 1.5 gigawatt now in use. The Northern Cape is home to a large portion of South Africa's solar sector. 3. KAZU Solar 1 100 megawatt KAZU Solar 1 is a 100 megawatt solar power facility located near Poffatter in South Africa's Northern Cape province. It is South Africa's first commercially functioning solar thermal electric power plant. It's also South Africa's first CSP plant that utilized parabolic trough technology. In March of 2015, the project was formally inaugurated. It provides sustainable electricity to almost 80,000 African homes while reducing CO2 emissions by 315,000 tons per year. A BINGOA Solar, 51%, the State-run Industrial Development Corporation, IDC, 29%, and a community trust owned by broad-based black economic empowerment are all shareholders in the KAZU Solar 1 project, BBBE, 20%. The South African Department of Energy, DOE, announced 28 renewable energy projects in 2011. KAZU Solar 1 is one of them. 2. Benbin Solar Project 165.5 megawatt The 165.5-meter Watt-Benbin photovoltaic, PV. Solar Park is located in Benbin, Egypt, in the Iswan province. The Solar Park consists of three solar power facilities with separate installed capacities of 67.5 MW, 70 MW, and 28 megawatt. Chin Solar completed the 165.5 megawatt project in August 2018. The Solar Park, which cost $190 million to build, is developed, financed, and operated by AQUA Power. 1. Nor Solar Complex 510 megawatt The Nor Solar Complex is a 510 megawatt solar park in Morocco's Agadir area, located in the town of Wazazi. It is the world's largest concentrated solar power plant. The project's site receives 2,635 KW per meter square of sunlight each year, which is among the greatest in the world. Multiple utility-scale solar power facilities using diverse solar technologies are integrated into the Solar Park. The Nor Solar Park consists of three projects with a total area of 2,500 hectares. Nor 1, Nor 2, and Nor 3. By 2018, the three power plants have been connected to the grid. Phase 1 was anticipated to $537 million. The African Development Bank, a FDB, group was the sole source of funding. The total investment for Phase 2 of the Nor Complex was $2 billion, with 80% of the money coming from loan and 20% coming from equity. Mason provided the whole debt facility, which was backed by the FDB, Agents' Frankays to Development, Clean Technology Fund, European Commission, European Investment Bank, Creditanstalt, Ferwiderofbau, and World Bank. Solar technologies turn sunlight into electrical energy by using photovoltaic panels or concentrating solar radiation with mirrors. This is a modern and efficient kind of energy that is increasingly being adopted by various countries and continents. When it comes to the usage of renewable energy in the form of solar energy, African countries are not left out. Thank you for watching this video all the way through. Please support Africa Reloaded by liking, commenting, sharing, and subscribing. To be notified of new videos about African projects, subscribe to our YouTube channel. Please make sure that your notifications are turned on.