Debugging by Hypothesis



When bugs arrive there are many things that might have cause them, and actually we spend more time trying to find the bugs than coding [1].

If we would put in one sentence, debugging It is a two step process, first the location of the failure and then the fixing of the issue. The debugging process relies on developers questions but also relies on tools and approaches.

Modern debugging tools employ sophisticated mechanisms to help answering this question, however sometimes, actually most of the times, it is not enough just to use tools to find answers, it’s actually necessary to use several approach/more than one sometimes, to find the causes of issues.

1.Try and fail approach

For small development problems, the try and fail approach is effiencient and ok. However, to bigger problems we need to change the way to solve them actually.


1. Why? Chain of failure.
2. What? Related to entity level.
3. Whether? Set of events on the

3.Hypothesis thesis

The questions can be used combined with hypothesis testing, which is a quite interesting and reliable approach to solve problems on code that you know and code that you don’t know.


[1] How Did the Failure Come to Be? Mohammadreza Azadmanesh and Matthias Hauswirth. CoCos’17, October 23, 2017, Vancouver, Canada.





Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s