We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Practical Debugging - Tips, Tricks and Ways to think

Formale Metadaten

Titel
Practical Debugging - Tips, Tricks and Ways to think
Serientitel
Anzahl der Teile
160
Autor
Lizenz
CC-Namensnennung - keine kommerzielle Nutzung - Weitergabe unter gleichen Bedingungen 3.0 Unported:
Sie dürfen das Werk bzw. den Inhalt zu jedem legalen und nicht-kommerziellen Zweck nutzen, verändern und in unveränderter oder veränderter Form vervielfältigen, verbreiten und öffentlich zugänglich machen, sofern Sie den Namen des Autors/Rechteinhabers in der von ihm festgelegten Weise nennen und das Werk bzw. diesen Inhalt auch in veränderter Form nur unter den Bedingungen dieser Lizenz weitergeben
Identifikatoren
Herausgeber
Erscheinungsjahr
Sprache

Inhaltliche Metadaten

Fachgebiet
Genre
Abstract
Practical Debugging - Tips, Tricks and Ways to think [EuroPython 2017 - Talk - 2017-07-14 - Arengo] [Rimini, Italy] When we write code, oftentimes things are not working as expected. We followed the tutorial and yet we got an error. We introduce a new feature but something else broke. Having to deal with bugs is inevitable. Trying to ""debug"" what happened or what caused the problem can be really frustrating and timewasting. The aim of this talk is go give ways to think & steps to take when we are faced with the process of debugging. The language for the examples is going to be Python & the tools used - from the python ecosystem. The talk will be practical, with a lot of real-world examples. The goal is to cover the following scenarios by showing different ways to approch the problem: You followed a tutorial but it's not working. What to do? You introduce new feature but things broke somewhere else in the project. What to do? You are using a popular 3rd party library but something breaks. What to do? A bug occurs and you have no idea what or who caused it. What to do? You can't fix or find the bug. What now? You want to generalize your debugging skills. How to do that? We will be talking about critical changes, binary search, problem isolation, interactive debuggers, printing, testing, greping and other interesting things