Debugging in computer programming is defined as a process which involves a step-by-step approach to isolate problem area(s) and then determine a way to either fix them or come up with a workaround. A very common approach which is adopted by developers when debugging is print statements. Lesser known as the “poor man’s debugging technique”, this is quite useful since you can print everything under the hood to get a deeper dive on the variables while you try and isolate the problematic line or a section of code.
Being a developer at heart, I’ll start with a rant
Business requires a new product to go to market. Some developers have just completed couple of proof of concept (POC) or a Minimum Viable Product (MVP). There is a nervous meeting room discussion on “vendor-wars” – how do we win this business from the client?