DeveloperWeek 2020

Over the last decade, software development practices have evolved to provide more automation for build and deployment procedures and to incorporate more testing and feedback earlier in development. This has been a great boon for the speed at which we can deliver changes, but unfortunately 50% of our engineering efforts are still spent on reactive and unplanned work.

In this session, we will explore some techniques that teams who work with JavaScript, Node, Python, Java, C++, Containers, and more have been using to rebalance the equation so they can spend more time on new features and less time on bugs. These teams have integrated solutions to help them understand failure conditions by answering questions like:
* What happened?
* Does it matter?
* Why did it happen?
* How to fix it?

We will discuss some common workflows like:
* How to handle errors in CI/CD builds
* How to embed actionable software quality remediation steps into the SDLC
* How to identify the most impactful code defects and production failures to fix