Completed
- De-obfuscating Code with Source Maps
Class Central Classrooms beta
YouTube videos curated by Class Central.
Classroom Contents
Maximizing Application Performance and Monitoring with Sentry
Automatically move to the next video in the Classroom when playback concludes
- 1 - Intro
- 2 - Sponsor
- 3 - Greetings
- 4 - Defining Sentry's Suite of Features
- 5 - How does Sentry instrument a wide variety of software?
- 6 - Sentry compared to TypeScript
- 7 - Sentry and Privacy
- 8 - De-obfuscating Code with Source Maps
- 9 - Replay.io vs. Session Replay and Sentry
- 10 - Sentry Spotlight and Dev-Time Monitoring
- 11 - Propagating a Trace inside a Database Transaction
- 12 - Sentry Differentiators
- 13 - Sentry Report of Most Common Pitfalls in Apps, like Spotify Wrapped but with Sentry
- 14 - Children and error/stack proximity with Sentry reporting
- 15 - The Apdex as a Performance Metric
- 16 - Performance and Core Web Vitals
- 17 - Cumulative Layout Shift CLS
- 18 - Where does CLS happen in the rendering process and mitigation steps
- 19 - Fonts as a source of CLS, FOUT Flash of Unstyled Text, and FOIT Flash of Invisible Text
- 20 - Free Open Source Project Idea: Tree Shaking for Font Glyphs
- 21 - Replacing fonts when loaded to prevent CLS, FOIT, and FOUT
- 22 - How Sentry helps with Core Web Vitals
- 23 - Sentry Internals: Architecture, Data Stores, Rust
- 24 - Scale Problems that Sentry went through
- 25 - Does Sentry use Sentry? Sentry on Sentry
- 26 - When to Avoid Sentry
- 27 - Sentry Salient Repeating Best Practices
- 28 - Conclusion
