Website uses cookies. Cookies remember your actions and preferences for a better online experience. We don`t share information with third parties without your knowledge.
Sometimes a huge error message appears on the screen instead of the expected result, and you can't even imagine what went wrong. Usually it's not as bad as it may seem at first glance, but lack of experience can noticeably increase the time to find and solve the problem.
In this BizUPLab publication we will tell you about two simple ways of finding and debugging an error that can be applied in any programming sphere and with any language. They will help you to maximise the time to find a problem and stop being afraid of errors even in programming languages new to you.
In this BizUPLab publication we will tell you about two simple ways of finding and debugging an error that can be applied in any programming sphere and with any language. They will help you to maximise the time to find a problem and stop being afraid of errors even in programming languages new to you.
Two easy ways to find a bug in your code
Reverse method
When using this method, you should think like a compiler or interpreter, but in the opposite direction, i.e. read the code backwards. An error did not appear out of nowhere - certain calls or operations led to it. Since modern programs have more than one thousand lines of code, it is an extreme case to start searching from the program's start point. Usually it is faster to rewind the source code by 5-10 calls and start from there. As an example, BizUPLab Budapest programmers cite the division by zero error. The error itself is as clear as possible: you cannot divide by zero. We read the code above and see what manipulations were performed with the variable that suddenly became equal to zero, do not hesitate to go to the methods that interacted with this variable and see what could have gone wrong there.
If you have the opportunity to use stop points, that's great: we can safely rewind to the beginning of the function and keep a close eye on the changes in the variable. As soon as we find the place where the variable has suddenly changed, it means that we have localised the error. All that remains is to fix it.
This approach is applicable to any error, but it requires some understanding of both the programming language and the software product architecture. Sometimes the intertwined calls are so complex and intricate that you cannot do without basic knowledge.
When using this method, you should think like a compiler or interpreter, but in the opposite direction, i.e. read the code backwards. An error did not appear out of nowhere - certain calls or operations led to it. Since modern programs have more than one thousand lines of code, it is an extreme case to start searching from the program's start point. Usually it is faster to rewind the source code by 5-10 calls and start from there. As an example, BizUPLab Budapest programmers cite the division by zero error. The error itself is as clear as possible: you cannot divide by zero. We read the code above and see what manipulations were performed with the variable that suddenly became equal to zero, do not hesitate to go to the methods that interacted with this variable and see what could have gone wrong there.
If you have the opportunity to use stop points, that's great: we can safely rewind to the beginning of the function and keep a close eye on the changes in the variable. As soon as we find the place where the variable has suddenly changed, it means that we have localised the error. All that remains is to fix it.
This approach is applicable to any error, but it requires some understanding of both the programming language and the software product architecture. Sometimes the intertwined calls are so complex and intricate that you cannot do without basic knowledge.
Universal method
But what to do if you need to quickly fix an error in an unknown project or if you are not familiar with the language in which the programme is written. In this case, the universal method will help you. However, you will need to know how to operate algorithms since this is the universal language of all programs. This skill will help you quickly orientate yourself and still find the fault.
The universal method of error search is actually very similar to binary search: you should divide a conditional code fragment in half and perform necessary operations that will help you understand the real state of affairs.
For example, you have the same error of division by zero but without specifying the place. There may be a great number of such places, so it is difficult to check each of them for a potential error. But you may write a ‘special’ error, that is, you may make a clear error that will definitely break the programme execution.
For example, it may be an invalid character or an incorrect operation. And then it is the same as in a binary search:
Such a simple division of code chunks will very quickly allow you to localise the error you are looking for and start analysing it.
These two simple approaches can help you to deal with any problem when writing code, BizUPLab company managers advise. The backward method will help you to find the exact place where everything went wrong, and the binary division will quickly narrow down the search of this place in the code. Naturally, these approaches are not a panacea, but they are an excellent start and a great foundation for further development of your own methods.
But what to do if you need to quickly fix an error in an unknown project or if you are not familiar with the language in which the programme is written. In this case, the universal method will help you. However, you will need to know how to operate algorithms since this is the universal language of all programs. This skill will help you quickly orientate yourself and still find the fault.
The universal method of error search is actually very similar to binary search: you should divide a conditional code fragment in half and perform necessary operations that will help you understand the real state of affairs.
For example, you have the same error of division by zero but without specifying the place. There may be a great number of such places, so it is difficult to check each of them for a potential error. But you may write a ‘special’ error, that is, you may make a clear error that will definitely break the programme execution.
For example, it may be an invalid character or an incorrect operation. And then it is the same as in a binary search:
- if your ‘special’ error appears earlier than the error you are looking for, it means that the problem is somewhere further down the code;
- if your error has not appeared at all, it means that you have already jumped over the problem.
Such a simple division of code chunks will very quickly allow you to localise the error you are looking for and start analysing it.
These two simple approaches can help you to deal with any problem when writing code, BizUPLab company managers advise. The backward method will help you to find the exact place where everything went wrong, and the binary division will quickly narrow down the search of this place in the code. Naturally, these approaches are not a panacea, but they are an excellent start and a great foundation for further development of your own methods.
We help business people manage their resources efficiently and systematically achieve success.
1114 Budapest, Bartók Béla út 66. 3. em. 4.
info@bizuplab.com
info@bizuplab.com
Contact Info
Copyright © BizUPLab, 2023 - 2025