Programming Horror

1883 readers

1 users here now

Welcome to Programming Horror!

This is a place to share strange or terrible code you come across.

For more general memes about programming there's also Programmer Humor.

Looking for mods. If youre interested in moderating the community feel free to dm @Ategon@programming.dev

Rules

Keep content in english
No advertisements (this includes both code in advertisements and advertisement in posts)
No generated code (a person has to have made it)

Credits

Icon base made by Lorc under CC BY 3.0 with modifications to add a gradient

founded 1 year ago

MODERATORS

Vacant@programming.dev

The switch-case starts on line 83. (programming.dev)

submitted 11 months ago by PoolloverNathan@programming.dev to c/programming_horror@programming.dev

8 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] driving_crooner@lemmy.eco.br 6 points 11 months ago (3 children)

Any guide on how to write effective logs? I'm starting to write scripts to automate some processes at my job and want to start logging the process to debugging or troubleshooting in the future.

[–] nolefan33@sh.itjust.works 10 points 11 months ago (1 children)

The most useful thing you can do for simple scripts is never use the same log string in two locations in your code. If you reuse strings it can become very confusing where a specific log line printed from. In addition, write logs that let you trace the execution of the program, down to some kind of identifier that allows you to determine (for example) the exact iteration of a loop that caused an error.

[–] apd@programming.dev 2 points 11 months ago

I'd use logger that prints the file and line number when logging, to avoid the question of: "where is the log coming from"

load more comments (1 replies)