This talk will explain and showcase how improving transparency and accountability in development teams can significantly improve the culture in the team and improve the quality of the code that gets released.
It is often the case that a small group of people are the ones who care about errors or performance problems that occur in their web application. This is particularly common in organizations with big ops teams. An unfortunate consequence is that developers often become less careful if they know that when something breaks in their code, someone else will take care of it.
As companies are becoming increasingly aware of the advantages of good collaboration between developers and ops., frequent deployments etc., there is a unique opportunity to change the attitude of developers towards problems that occur in production. A better attitude will make your team fix bugs quicker, write better tested and more resilient code, ultimately allowing everyone to sleep more.
The key to improving the culture in such organizations is to improve transparency and thus increase accountability by way of monitoring and alerting that is accessible for developers. This talk will describe the above problem and ways to increase accountability while trying to stay free of the blame game.