Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
Voxera113888yWell. If you have a console to write to it is one way that often works.
Often use it when I have no other information.
Preferably with some relevant output that could catch errors not including code not running, like finding out where a list suddenly is empty.
But if a console is not available I have started using redis pub/sub for similar output and it actually is very helpful when debugging is impractical. -
when debugger is not na option, writing things on console is one of the methods that i would use..
-
I tried using a debugger several times but I find it less intuitive than printfs in good spots.. I have yet to learn how to efficiently use a debugger maybe
-
I don't know... This is usually my last resort, but... I have used it in a LOT of occasions. It is not an efficient way of finding errors ( overhead of writing additional code on almost every other line) but it does work...
My manager believes every bug can be solved by adding a thousand printf(s) and checking which part of the code isn't being hit. How do I politely tell him to get his shit straight? 😂😂😂
undefined