 All right, let's find a new slide deck now. All right, it is 11.35 in my watch. So we'll get started. We've given five minutes buffer for people to get in and let them come in. So this title of this talk is inverting the pyramid. And we can introduce the word testing in it because I'm going to eliminate the word testing from it eventually. That's essentially the idea of the stock. This is an experience report of me having done this for two specific organizations where we have inverted the testing pyramid and I'll talk about what that means and why the title. So everyone's familiar with, you know, back in the Stone Age, the kind of development we did and there's the surprise. Yes? So what do we see in stuff like this, right? When we do development in this fashion where we plan, design, distribute, work, work in isolation and then come back and try to integrate stuff, right? I've not even put the testing part yet, right? I'm just talking about this, even this stage, we see a big surprise. So what we see generally is a lot of last minute surprises. Bad things are visible too late and we find that as a real problem, all right? Actually, let me pause for a second and ask how many people got a chance to look the slides before they came in, okay? So for some people what I'm going to talk is kind of sounding familiar, but for the rest of them we'll kind of go a little slower. My idea is to brush through first initial section and spend a lot of time getting into more interactive session where I want to talk through some basics and then get people's experience and kind of take it from there on an evolutionary path, all right? So bad things are visible too late. We get last minute surprises. This was a typical problem. So to address this problem, what did we do? From a distribute work and then get back and integrate everything together and then test it to address that issue. What was the practice that teams started practicing? Continuous integration, right? Any other practice? Early feedback. How do we get early feedback? What specific practice? Test-driven. Test-driven development, fantastic. What else did we do? Continuous delivery. Continuous delivery. So we went further all the way and started looking at continuous delivery, right? So let's talk about birth of continuous integration. Anyone knows which?