FullStack eXchange 2022
Our talk: Squash All the Performance Bugs: Browser Dev-Tools Your Secret Silver Bullet
UI performance bugs are probably the most frustrating for both application users and developers. For application users they are just a bad experience that can lead users to abandon your product. For developers they are the hardest bugs to detect and ultimately debug––because they're basically impossible to find by just reading the code or running a typical debugger, and don't have any simple workarounds like others.
One of the less glamorous but incredibly useful tools to help catch and squash those elusive bugs before they reach your end user, is the browser dev-tools performance stack, which includes the Networking, Memory, Rendering, Code Bugs, and CPU. This talk will walk through some of the most common pitfalls in UI performance, and some good practices to help you avoid them. You can quickly reproduce these performance issues by calling the DOM and your app directly from the browser console, and running stress tests. Through code examples and a demo, you'll be able to learn some of the best kept secrets, tips and tricks for optimizing and debugging your UI performance for your fullstack apps.
Agenda
Let's face it - now that we're a few years past the whole "shift left" trend, we can honestly say it has largely failed when considering security debt. Instead of solving issues earlier in the cycle, which was at the premise of the “shift left” promise, we mostly shifted the problem left. To date, security has largely been a source of friction between development and security teams––and fostering a proactive security culture among developers is still the holy grail a lot of companies are dreaming about without really managing to reach it. That's because this mindset needs a hard reset. We need to look at security completely differently. Security should not and cannot be decoupled from product quality - notably because developers are measured on code quality and velocity and not on how secure their code is. In the same way that our product's usability is a first-order engineering concern, security should be regarded in the exact same way. In this talk, I'll share some lessons learned and the way to bridge the gap between security and engineering, by changing the way it is viewed and implemented in current processes.
%20(1).webp)
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna