There are a lot of books, articles, and online tutorials out there with fantastic advice on how to make your websites performant. It all seems so easy in theory, but applying best practices to real-world code is anything but straightforward. Diagnosing and fixing frontend performance issues on a large legacy codebase is like being an archaeologist excavating the remains of a lost civilization. You don’t know what you will find until you start digging.
Pick up your trowels and join Katie Sylor-Miller to dig into frontend performance on Etsy’s large legacy mobile codebase, exploring real-life lessons you can use to guide your own excavations into legacy code and discovering how Etsy unearthed new insights into its culture. While Etsy prides itself on its culture of performance, like all cultures, it needs to adapt and reinvent itself to account for changes to the landscape. The company is now making the case for a new, organization-wide frontend-focused performance culture that will solve the problems we face today.
Katie Sylor-Miller is a staff software engineer on the frontend systems team at Etsy, where she advocates for and implements frontend best practices in collaboration with product engineers and designers. She is passionate about frontend architecture, design systems, style guides, accessibility, performance, and teaching others. Katie has written about the engineering side of design systems for the Design Systems Handbook, and she created OhShitGit.com to share her hard-won knowledge of how to get out of your Git messes with a bit of humor (and a lot of swears).
Help us make this conference the best it can be for you. Have questions you'd like this speaker to address? Suggestions for issues that deserve extra attention? Feedback that you'd like to share with the speaker and other attendees?
Join the conversation here (requires login)
©2018, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • email@example.com