publish date
Feb 16, 2023
duration
32
min
Difficulty
Case details
"This is a real story of how we implemented Shift Left by influencing, mindset change, creating champions and with the help of technology at Expedia Group. In every software company in the world, at the nucleus of it, all we are trying to do is, take a code change and move it to production, faster with quality. There couldn't be any disagreement over this! Sometimes when we repeatedly follow a practice, even when there are new better alternatives, it is difficult to change our mindset because we think ""Why change? it is working"". Moving your pipelines to follow Shift Left is one of them. In US alone, $113B is spent annually on identifying and fixing production defects! Shift Left not only increases developer productivity, but allows you to go to production faster, more frequently and reduce production incidents. End of the day, it makes both developers and customers happy! The biggest frustrations for developers in a team is, CI/CD pipeline being blocked and no one can merge their PR, everyone has to wait for it to be fixed and pipeline becomes green again. And as all the validation and verifications happening to the right side of the pipeline, it is going to take more time to fix issues as well, involving many engineers, because the failure could have been caused by any code change. This is true, especially when an issue happens in production, not only everyone has to be involved to figure out the problem, but there is going to be lot of unhappy customers and loss of revenue. What if you have something where pipeline blockage is not possible. What if you can can run the same set of checks you run in main pipeline but you run them against your branch itself and when you merge your PR, it is already 'production ready', what if every PR can go to production directly? what if you have a mechanism where it actually reduces production incidents ?"
Share case: