 So ask yourself this question, you could have a time machine and you could go back two years and have a conversation with yourself, what advice would you give to that person? I had this interesting project which was for the travel industry. So one of my seniors, he used to make a lot of estimates and you know I used to have a buffer like after making estimates and he used to hide buffer, here buffer, that buffer, you know, he used to keep a lot of buffers and then I think maybe that buffer might work or not work. But almost always, I've never found but it's 100% it always happens that his buffer is always utilized and it's both about like two times or three times his buffer. So discussing today about no estimates, it makes sense. I think it would have been better doing no estimate process. Like rather than saying no estimated thing, do a small step, measure exactly time which it took, raise the bill, go for the next one rather than making an upfront big estimate and keeping a buffer. Because it would have saved the cost for the customer and also you know a lot of misery in the process. That's all what I think today. It is hard to get up here so it's good to have applause. Anyone else? I saw in your eyes that you had something to say. Well, the question is if you could go back in time two years ago and talk to yourself, what advice would you give yourself? I'm going to start singing until somebody comes up on stage and gives a lightning talk. That's not good for anyone, trust me. We just went through this noise technician right. So, mostly we thought that it would be a gift. I think one advice in the last three years going through, I can say that delay your duty and as much as possible till the last probably until the last responsible moment. Till you have enough information to take practice here. Come up on stage. Right here. You are now the star of the room. If I would have gone back two years back, I would have imagined to know a bit more of the technologies at that time because when I'm catching up with it now, I feel that a bit delayed. So, I think that if I would have done that, I would have just started some of them two years back. And with this constant, it's helping me to get back to the question. You have nothing to say. Everyone has something interesting to say. Interesting story. Stories are great. Not a story. I'm from the ops background. So, if you think two years back, so I will be choosing to have like implementing the infrastructure as a code in a better way. So, that is my thought. Using the new technologies like Terraform and like infrastructure with Chef and implementing the cloud technologies, that could be the cool one. Now, we are just starting up. That could be better option we should have started earlier in the marketing. The market is catching you. Okay. Excellent. One more. I started three years back into this. I will tell one thing. When we started, we used to implement everything here and there. We did not think about what we are doing and what we are implementing and why we are using this. But if we would have researched a bit on two things then taking a step ahead, we would have been a bit more ahead where we are right now. That is something. Thank you. Anyone else? There's nothing to say. We've got one more. So, today the deployment or delivery pipeline of your development pipeline cycle. So, today we use Jenkins. Previously, two years back, we used the Jenkins as only job schedulers or job run things. So, now we use the Jenkins as a pipeline. Jenkins 2.0. We versionize that Jenkins pipe jobs and run into the different stages. Dev testing and the deployment stage. We see how the code flows through the different environments. So, we can easily catch up the bugs. Okay. We are out of time. Would anyone take the last minute before we finish up? Awesome. Okay. You guys enjoyed the last couple of talks? Thanks for those who were brave and come and stood on stage. It is scary. But you liked it so much. You came up twice. Thank you.