At the top of a 2000+ line source file

Some people just want to watch the world burn

Damn (#include).

Thanks to another rant I read these as hashtag include fml

Easy... 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

Or there's no bug and your being trolled

@SCamp Schrodinger's Bug.

At least he warns you

Debug mode was made for this.

That developer has Honest Level: I don't give a damn!!!

@curlyDev good C level might not be enough when its C++

@SCamp oh god

Happy to see C++ in the javascript wasteland:)

@curlyDev do it while crying or cursing the prev dev. XD your choice :P

PS. I always cry. :(

@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.

Vim

You are a honest man , it's kinda rare these days

At least they warned you.
I have seen worse.

+1 for emacs.

+1 for using GNU/Linux