Operations | Monitoring | ITSM | DevOps | Cloud

Sentry

[Live workshop] Fix Your Frontend: JavaScript Edition

Join the team behind our JavaScript SDKs for a live session as they share practical tips to make debugging more tolerable. We’ll walk through everything from setting up and configuring Sentry to trace errors and identifying slow code. Whether you’re new to Sentry or a long-time user, there will be something for you. This session will cover: Setting up and configuring Sentry for frontend projects How to trace frontend errors back to backend issues Analyzing web vitals to identify performance bottlenecks Using session replay for better user insights.

Why Clean Architecture makes debugging easier

Let’s start with things we already know - complex projects are inherently hard to debug. The more complicated they are, the harder it is to debug them. The size of the project naturally defines complexity’s lower bounds, but even the smallest projects can become unnecessarily complex and messy if you don’t pay attention to how you structure them. Though we can’t eliminate complexity, we can manage it effectively with the right approach.

Debugging with Sentry and Expo

Sentry is a debuggability platform that provides real-time insights into production deployments with info to reproduce and fix errors, crashes, and slow code. We are very lucky to welcome Krystof Woldrich from Sentry to join the stream and live demo some debug magic. From the Expo side we will have debug wizard and father of Expo Atlas, Cedric Van Putten. The two of them are going to show a complete debug flow.

How to Improve Your React Debugging Process

In this guide, you’ll gather how to identify and solve the most common bugs and performance issues. We’ll cover debugging client-side React, if you have a React app that uses server-side rendering, you can also look at our Node.js debugging guide or on-demand workshop. In the below sections you’ll learn.

Everyone needs to know how to trace

It’s a bold claim for me to say that every developer can benefit from something 40% of them haven’t heard of, but hear me out. I was among the 40% who didn’t know tracing existed until this summer. Still, I spent the last three months learning why it’s critical to a developer’s workflow and the different ways developers pragmatically use it. In this blog, I hope to show you that you can benefit from tracing regardless of your stack, role, size, or project.