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
-
curlyDev4727yEasy... Take all functions break them by functionality on paper and then read the code.
It sounds hard but its not its mostly time consuming depending on your c level it will take 4 5 hours at best. -
This is the part where you set it into debug mode, and it should stop where the bug occurs.
or buckle down and comment the shit out of everything -
yzhea21957y
-
curlyDev4727y@yzhea i had a notepad with 100 functions name and next to them comments ...
Been there done that. Its just a waste of time and sometimes the dev isnt to blame but stupid deadlines and managers who let any monkey to decide what "the plan" should be like.
Always write code like if the next who reads it is a psychothic murderer who knows where you live.
At the top of a 2000+ line source file
undefined