Debug like a Pro
The majority of engineers either debug using print()/NSLog, or utilise debugger for po command and ordinary breakpoints. However, Xcode and its debug tools give way more power, starting from the LLDB command language and runtime breakpoints logging to Instruments for performance and CPU investigations. I will cover the best practices, talk about most recent changes from WWDC 2018 and show quite a few examples, where meaningless at a first sight error message can be expanded to a call to action using proper debug tools. By the end of the talk, everyone should learn how to debug like a pro.
What does this talk cover?
Xcode debugging beyond print() and po: the LLDB command language, breakpoints that log at runtime, and Instruments for CPU and performance investigations, including what changed at WWDC 2018.
Where can I watch it?
The Swift Heroes recording is embedded at the top of this page. There's also a second edition, Debug like a Pro v2, with its own page and slide deck.
When an app is slow or crashing in production, this is what I get hired to fix - Instruments traces included.
App Performance & CrashesSimilar Talks
Modern devices are way more powerful for users to notice a difference between bubble sort and merge sort. Or not? Should everyone know how to implement Ukkonen's algorithm if they develop a weather app? What's the "Big O" of your average app and how to determine it?
The second part of a thorough introduction into iOS Security, from various pentesting techniques, to possible flaws to use-cases and tools.
Debunked the "iOS is secure by default" myth in 90 minutes. Walked through real pentesting techniques, tools, and war stories from the security trenches.
What teaching iOS at a Russian university taught me about learning. Turns out developers and nomads have more in common than you'd think — we both carry only what we need.