Print debugging

>print debugging

Attached: 1521350742702.jpg (409x409, 128K)

>i have a job that pays well and you dont

Attached: extremely-smug-anime.webm (344x374, 958K)

>one-man team

Attached: 1513615981341.png (400x333, 91K)

Sometimes you want puts() calls, sometimes you want gdb, sometimes you want valgrind. Depends on what you're doing.

If you're a super elite hacker, you use your own print function , I like to name mine echo, then when you aren't debugging you swap out the function definition with a noop and it all gets optimized out. Because fuck logging and fuck exceptions, we've got shit to do, ain't got no damn time for that bullshit. This style of coding is particularly effective when debugging php on production servers

>not using msgbox() debugging

>down syndrome

debugging

>debugging printers

Attached: 1556224892293.png (787x633, 475K)

>debugging
>not just rewriting bits of code until it works

Attached: 1530236385760.jpg (574x881, 54K)

>js
>leave debuggers in production code

>printing nonsense statements like "hamburger" so that they're easy to find in a stack trace

Attached: images.png (266x189, 6K)

> not using racial slurs as debugging variable names

>not using nigger, faggot etc as debugging statements
>not forgetting to take them out of the final version

>not putting racial slurs in your git commits

>not forgetting to delete comments such as "fix this fucking nigger shit" before reviewing your bachelor thesis code with your advisor

Attached: winwin.gif (718x404, 66K)

I'm doing this. That arcane debugging from c++ is headache inducing. Sometimes you don't even get a proper backtrace for some stupid fucking reason and have to read carefully through every single class doc in your project to find out if you got a type wrong. Fuck this bullshit.

>debugging
Why would you get rid of features that GOD put in the program?

Attached: im king nigger wat 16 color.png (640x480, 34K)

desu i had left commented nigger prints in a uni assignment and the TA never mentioned it to me. They probably dont go through the code if the output is correct, but ever since that scare i now use

>why1
>why2
>why3
on many parts where the bug is likely to be.
Especially when debugging c++, shits a nightmare bros

>Traceback (most recent call last):
> File "", line 1, in
>NameError: name 'debugging' is not defined

based
I love imagining that software I'm running could be quietly whispering "nigger" in the background because somebody forgot to take out a debug statement

he doesn't use C++

Attached: 1540499117966.png (640x640, 121K)

Wow, has anyone ever had that opinion ever? It really is retarded

Attached: 1544032237999.png (640x640, 129K)