
We'll start with a short introduction to Continuous Feedback and how it can transform how we write code.
OpenTelemetry is a great technology that super easy to activate and use to collect data from Java applications. In this second segment of the course, we'll leave the Powerpoint for a while to see if we can setup a working environment to experiment with.
What do you know about the code changes that were just introduced into the codebase? When will you notice if something goes wrong?
Continuous Feedback is a new dev practice that aims to make practical usage of code runtime data to shorten the feedback loop during development. OpenTelemetry makes it possible with great library support and a standard spec for tracing, metrics, and more.
By practicing CF, developers can increase productivity with shorter feedback loops. Getting access to data about their code much earlier, detecting and resolving issues in shorter iterations, as-they-code.
In this course, we'll look past the novelty of using OSS observability tools and technologies, to discuss how we can actually make them useful for developers. We'll look at the benefits of enabling OpenTelemetry collection for dev and test data and examine OSS tools to help analyze the application runtime. Throughout the talk, we'll go over code examples of common anti-patterns, code smells, hidden errors, and other types of problems that this untapped source of data can reveal.
Ultimately, the goal should not be simply observing the application or creating nice-looking dashboards. Rather, success is in leveraging observability data in order to achieve a more effective dev process and write better code.