Udemy
    •  
    •  
    •  
    •  
    •  
    •  
    •  
    •  
Turn what you know into an opportunity and reach millions around the world.
Learn More
Your cart is empty.
Keep shopping
Step up your coding with Continuous Feedback
Rating: 4.5 out of 5(21 ratings)
452 students

Step up your coding with Continuous Feedback

How to know more about your code, and know it earlier
Created byRoni Dover
Last updated 11/2023
English

What you'll learn

  • How to collect important information about your code
  • Tracing fundamentals and comparison to debugging
  • Using observability data to improve your code
  • OSS and free toolings

Course content

2 sections3 lectures1h 30m total length
  • What is Continuous Feedback and why should developers care?33:06

    We'll start with a short introduction to Continuous Feedback and how it can transform how we write code.

  • Not an OTEL 101: Getting info about code29:29

    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.

Requirements

  • Java Develpers

Description

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.

Who this course is for:

  • Software developers (senior and junior) interested in standing out with new skills and practices