This speaks to the general boring middle that hits many successful software projects. There's a point where it's simply about iteratively improving it while kee

This speaks to the general boring middle that hits many successful software projects. There's a point where it's simply about iteratively improving it while keeping it running 99% of the time. It's unglamorous, monotonous and boring, but it's wildly important to the continued success of the project. Who can blame engineers for not being interested in trudging through the boring middle? Interestingly sometimes efforts to keep engineers from leaving, like splitting an application into 100's of micro services, can actually undermine the entire business. Kind of fascinating if you think about it. A person in charge may be so afraid to lose an employee they fail to see that the very efforts to keep them may derail the success of the business.