Is a code truly tested until it has print("Fuck this"), print("Fuck that"), print("Fuck you"), print("Fuck me") spread along every code path?

Testers and tests test code. Not print statements. Welcome btw.

@olback Yeah they do, but print statements are always the true heroes & thanks, been around a while, just lurked for a long time!

Me when on the edge of debugging lmao

T E S T I N G

I title my debugging statements some of the people I used to know.
console.log('Greg: stubborn variable didn't change')
Console.log('Mike: Instead of softly trying he just broke')
Console.log('Tim: FUNCTION DIDNT EVEN RUN THE OVAL')

Good venting strategy if you've got a large cold dead diamond of a heart like me.

Println will help you debugs code just in case you are depressed. Cause you can print what the f** that you want.

And it was a stress relieve method

I can relate. I print test like jesse pinkman.
"Yo it's nil bitch." etc.

@PieInOblivion That's inspirational. I used to write lines such as
print(Jim is going to die) //for when a function starts
print(Jim is dead now) //for when the function has run correctly and
print(Jim is still alive) //for when the function has run badly