Why businesses want us to outright ignore best practices

We’ve spent a good many pages now discussing how value can be perceived and multiple examples inside a company of different types of value. We have explored A/B testing and how quarter-driven results can dramatically shorten A/B testing implementation time for developers introducing higher risk to code stability. And finally, we took some time to have code reviews and merge requests. So why did these subjects come up before we got to the heart of what this chapter is about? Great question – without understanding these subjects, we have no base to provide an understanding of what goes wrong in the development process.

The truth about the ownership of a developer’s time

I made this mistake early on in my career – thinking that developers and their managers own their own schedules. I thought by speaking with the development team, I could ask them to assist with reliability and observability tooling...