 Before we start, let's do a quick show of hands. How many of us believe that continuous integration, CEI, is an integral part of the development process? Please raise your hands up. Okay, cool. Keep your hands up. If your CEI takes less than 30 minutes to produce stable build artifacts after running all the available tests. That's nice. What about 15 minutes? What about 10? Wow, cool. So we have at least two people here who can help us out if you have any questions. If you have any questions, you can reach out to them. In our case, though, around 10 to 12 months ago, our CEI system used to take around 60 to 90 minutes to produce stable build artifacts after pulling the code, building the code, and running all the available tests. Now, that's a pretty slow time there. And it used to get really bad if the test failed because while the prior build was running, multiple developers would commit their code. And now to go and isolate which commit actually caused the problem and then to fix the commit, it would take four to five hours to get the next set of stable build artifacts. And you can only imagine a situation when there was a mistake in isolating the problem or fixing the problem. It used to be much more longer. Now, clearly, the team was not happy about it because our ability to get quick feedback, to quickly learn from it and to take a course correction, that was getting impacted. Now, having these long-running build cycles also had a specific developer behavior impact. They were discouraged from committing their code frequently because if they commit their code frequently and the build fails, then now they have to spend their time making sure that whether they were the cause of the problem or was it someone else, so it's a waste of time. They were also afraid of committing their code during evening times. You can imagine, right? If I commit my code during evening and if my build fails, my entire evening is lost. So they'll prefer to keep their code on their machines and come next day morning and then commit their code. Now, that leads to other problems, like the longer, the more away you are from your repository, it takes longer time to integrate the code with the repository. So it's a waste of time. And God forbid if the hard disk crashes, then your entire efforts are lost. Now, these are profound business impacts. But apart from these business impacts, there are also some social impacts. Like me, has anyone been in a situation when you had to stay back late night to integrate your code with your colleagues just because your CIS system does not exist at the first place or your CIS system takes longer time to run? Anyone? Okay, cool. Okay, have you been in a situation when you had to rush back home living behind an unstable build just so that you don't miss the dinner with your family or friends? Okay, this is how your colleagues would be looking and pointing at you when that happens. Or have you decided to stay back, make sure that the builds are successful, all the tests are passing, the build artifacts are produced.