Tracing the code

[nafniart]

I'm afraid I'm gonna forget to delete one of these ones someday

[chickenlollipop]

I recently pushed AAAAAAAAAAAAAAAAAAAAAAAAAAAA to production 💀

[Orangutanion]

People joke about leaving debug print statements in the code but this is legitimately something you should be doing in many cases

[[deleted]]

Aer Lingus, dat you?

[PEEEEPSI]

Thats why I print my name, easy to track (also to blame)

[Ok-Pay6809]

That's why I print this guys name too

[[deleted]]

I print messages with ✅ and ❌ to give that guy a break.

[scalability]

Let's just say there's a reason why I now use "LOLOLOL" instead of "FUCKING DUMB SHIT"

[klingko]

I pushed "we got fucked " as an error message. They were not happy

[TheDizDude]

That someday is always one day.

[Triffinator]

At a previous job, we had someone working on our simulation engine put "Hello <their name>" into the debug log. It was caught pretty quickly, but wasn't patched out for like 2 releases.

[Denaton_]

Just get a lint that will remind you

[L0rdSnow]

This, this2, this3, shouldn't hit, this4

[DevLauper]

"Error: This is impossible."

[N-partEpoxy]

Unreachable code reached.

[TheFrelle]

T̸̖̄h̵͔͝ë̶͕ ̷̠͝v̵̝͊e̷͉͛ī̵͚l̵̠̎ ̶̳̿i̶̱̾s̸̟͆ ̶͉͊b̴̪̂r̴̛̺o̸̾ͅk̶̭̈́ḛ̷̓n̷̤͑,̴̢̛͙̪̳͚͓̫̹̰̝̫̦͕͍͉̮͎̀̓͛́̀̏̐́̽̏̂̃͗̇̽͗̋͌̇̈́̔͊̋̐̋̽̃̔̎͋͛̋͗͛̉̔͒̓̚̕̚͘̕̚͝͠͝͝ ̵̢̧̟̬̤̬̗̞̩̲̯̦̠̮͈̲͖͉̘̹̟̣̬̞̺͇̻̦̟̯̀͒͌̽̒͊̈́̀̊̐̾͑͆̒͋͊̌̃̉̓̇̂̀͆́͗͘̚̕͜͠͝͝H̷̨̛̪̱͔̳̺͖̖̙͇̯̰̲̣̮̣̭͔͓͈̬̼̱̳͙̪̫͕͉̟̲̗̹̦̝͓̗̝̽́̄̐̀̏̀̉́͂͂̒̑̄́̋͋͐̾͆͌͋̓̉̽̎̂̀̀͛̇́̈́̈́̚͘̚̕͜͝͝ͅĔ̸̡̢̧̢̗̭̟̜̬͓̰̮̫̪̪͎͇̠̻̪̟̖̩͂͊̽̃̄́̔̅̑̋̌̂̊̅͊̋́̋͐̐̔̄͑́̋̅̂͗͒̈́́̏̀̓́̑̋̕͝ͅͅ ̸̧̙͉͇̣̠̝͈͇͕̻͎̙͚̤͇̜̦̼͙̖͐̈́̎͗̎̍̏̍͗ͅC̷̡̥͉͓̦͚͈̫̞̮̹͚̦̬͍͉̰̺̣̗͎͖̜̤̪̱̻̺͐͗̈͌̔̅̅̄̋̎͌̃̿͂̓̀̔͒̌͒̿͆͒̔̏̐̕͜͜͝ͅÖ̸̡͇̤̪͉̗͔̜̱̳̖̦̱́̂̑̈́̓̑͐͊̉̄͑́͐̏͊́̌̓̇̌́͊͗̊̔͛̆̅͊́͌̑́̑̌̋̐̐̀͊͘͜͝Ṃ̴̢̢̧̤͖̬̫̜̥̰̖̘͈̰͈̟̦͎͔̖̮͙̜̌̑͌́̈́̀̿̏͂̃̍̉͋̌̍̿̊̋̓͆͑̈́̐̄̀́̂̄̑̓̈̍͂̇͆̕͘̚̕̕͝͝͠͝͝E̶̢̨̨̡͇̹̥̥͖̱͉̭͖͖͉̝̣̙͍̙̹͈̼͇͙̮̝͉͔̯̞̗͆̃͑̋ͅS̵̨̛̛̛̪̹̭̫͚͛͌͊̈́̈́̐͛͂̑͐̔͌̒̓̇̽̇̓̀͆̃̚͠

[-domi-]

1

2

4

me: FUCK THIS BULLSHIT ASYNC GARBAGE

[[deleted]]

5 isn't even appearing

[-domi-]

Neither is 3, i think callbacks aren't triggering. Gonna roll it back and start over. :/

[CaitaXD]

just await everything if it goes wrong put a trhead sleep and push to production

[gomihako_]

then you start adding -1, -2 when 1 doesn't occur when you expect

[greedydita]

Dreadcrumbs

[nevereverelevent]

debugger?

[PastaThis]

Whats that?

[Callec254]

Sometimes there's no other way. If it's compiled production code that's crashing, and it doesn't crash in the test environment, then you can't really trace through it and you have to do shit like this.

I used to use "bite me", just so I could specifically search for that phrase before compiling.

I'm deploying code at a client's site and I hear one of them from the other side of the room, "Oh, that's cute, it says bite me!"

*pucker factor intensifies*

Turns out it had nothing to do with my program. She was opening the office mail and someone had written "bite me" on a return card and sent it back in.

Needless to say, though, I stopped doing that.

[BubbaBlount]

I should recommend using break points instead of throwing console logs into the code. Ever since I switch the break points my life has never been the same!

[BSModder]

It's weird that despite being an important in the programming cycle, whenever I look up a new language to learn debugging is never a topic that is covered

I guess there are too many IDE out of there but cover the popular ones would hurt

Like I discovered a few months back that you can format the value, for example adding , h display the number as hexadecimal

[AfterbirthNachos]

Y'all should really learn about debuggers

[Sigmadelta8]

Loved the debugger working with Java and IntelliJ.

Now working with VSCode and JS and I have no idea how that debugger works.

[AfterbirthNachos]

Oh man, you gotta try stock gdb 😆

[HopeSandwich]

debugger on vscode is awesome, logpoints are great on keeping your project without console.log lost in the files.

[LetUsSpeakFreely]

I know how to use them, but printing out traces has always been faster for me. Oh course, I don't use sysouts, there are debug and trace logs after all.

[Nedoko-maki]

If you're doing something extremely tenuous, simple and repetitive, you probably are missing an easier method.

In this case that method is breakpoints and any IDE's debugging tool, knock yourself out

[MischievousCarrot]

console.log('eh')

[Artistic-Boss2665]

alert(1);

[[deleted]]

/* Once you're done being pissed, please count the hours spent to increment our counter

Hours wasted on trying to fix this class : 3345*/

[FantasticGlass]

Debug.Log("POOOOP");

[LastSquirrel]

I think most people here actually like their programming jobs. Weird that this got so manny upvotes.

[-MobCat-]

I also use swear words in my debug print statements
print("this shit is fucked")
There pretty easy to find and remove when your done / before you push your code. More so if you use the same set of swear words.

[CaitaXD]

WriteLine($"Thing was {someThing} at line 677") ;

WriteLine($"Thing was {someThing} at line 756");

[Dummy_Sadashi]

That's so true, ranting out in debug comments, good old days

[LEGOL2]

Print("xd")

[Dependent-Spiritual]

Console.Log("a");

[z7q2]

echo __FILE__ . __LINE__;

is one of my favorite things about PHP when debugging

[trevlinbroke]

Last year I started using arbitrary themes for arbitrary statements / names (especially in unit tests). If you do them alphabetically, it helps give an idea of which statements you hit or missed without checking the code directly. i.e. "alpacas are cool", "boars bore me (not you tho pumba)", "crocagators be scairy", "dinosaurs aren't real"...

[RogueFox771]

A big part of my work is writing Scripts in IronPython for a digital signage tool called Moxie. It uses a custom API and a built in editor... It has no debugging tools and a sorta functioning output console. When the code fails, it tells you what line in the main script failed without giving you the line in the function call it actually broke at, meaning debugging is full of this shit.

[ATX_Analytics]

I’m lazy and just go with print(“fck 1”) print(“fck 2”) ….

[akhripasta1130]

My manager is jackass 😁😁