How to get better at DEBUGGING.

No video

How to get better at DEBUGGING.

Рет қаралды 937

Күн бұрын

You want to get better at debugging?
In this video I'm presenting the TRAFFIC principle that will help you to get better at debugging and overall implement a system that will make debugging more efficient.
The TRAFFIC principle is a systematic debugging approach, if you want to learn more about it, check out this book amzn.to/3OMfZ1f
(I'm an Amazon affiliate and will earn for qualifying purchases)
#debugging #learnprogramming #coding #softwareengineer
My name is Florian Leitner-Fischer and I'm a computer science professor and software engineer based in Germany. I have experience both in academia as well as in industry managing a globally distributed software engineering team. In my videos I talk about programming, software development, software engineering and computer science as well as the occasional tech / gadget review.
My mission is to help you to take the step from programmer to software engineer and to help you being a better software engineering leader.
My Website: www.leitner-fischer.com

Пікірлер: 3

@spiridonsagirov 2 жыл бұрын

Additionally It's very important to realize that most of this work could be done by testing engineers. Specifically: track, reproduce, simplify and automate, test after the fix and regression test all other scenarios. We need to teach testing engineers to use this technique.

@spiridonsagirov 2 жыл бұрын

Hi! Thanks for an excellent explanation. In my experience the "simplify" and the "find possible origins" steps are actually the same step. The most important outcome of this step is to find what user actions or user inputs lead and don't lead to the reproduction. When this important information is figured out, the simplification comes naturally. An automation ideas usually comes after this simplification is done

@spiridonsagirov 2 жыл бұрын

I would also add the automation of the development environment creation for the problem fixing. As a developer It's always convenient to come to the station with all the source code already checked out and can be build. Where the problem is already reproduced. When all that's the developer should do is to figure out the root cause, change the code and leave the rest of the work to the testing engineer.