Bugs and Errors are common in Software Development. It happens to the best of us. Using the below points will be helpful when you're debugging your code.
Before you look at any logs or monitoring tools, go through the code that's causing the error. If you read through the code, you'll understand it and often times see what it is you're doing wrong.
Use all available logs and monitoring tools. The more information you have, the better you'll be able to understand the problem and resolve it. Modern Browsers, such as Google Chrome, also provide tools for developers to make use of.
You don't want to be sitting for hours, looking at the same line of code and blanking out. Take a step back, take a break, and tackle the issue with a fresh mind.
A second pair of eyes is always helpful, especially if you've developed tunnel vision. Someone else might be more experienced with the issue, or they can present other ideas you've not thought of. Even just thinking about the problem out loud could be helpful.
Going through your latest git commits might will show you what's changed. This is especially helpful with multiple people working on the same project, and it might show you what's causing the issue. You can then Rollback the change or create a Hot Fix for it.
If all else fails, search for your problem using Google or Stackoverflow. Your problem might not be new, and someone else might have already posted a solution to it.
Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.
If you disable this cookie, we will not be able to save your preferences. This means that every time you visit this website you will need to enable or disable cookies again.
This website uses Google Analytics to collect anonymous information such as the number of visitors to the site, and the most popular pages.
Keeping this cookie enabled helps us to improve our website.
Please enable Strictly Necessary Cookies first so that we can save your preferences!