Programmer Humor

32558 readers

437 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

cat_programmer@lemmy.ml

687

Sounds great in theory (programming.dev)

submitted 1 year ago by gogosempai@programming.dev to c/programmerhumor@lemmy.ml

72 comments fedilink hide all child comments

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

[–] ahal@lemmy.ca 14 points 1 year ago (1 children)

It's also great for bug fixes. Write that sucker first and you have an easy way to reproduce the issue and check whether it's fixed.

[–] CoderKat@lemm.ee 10 points 1 year ago

Yeah, I'm constantly recommending junior devs to use TDD specifically for this. I don't recommend it for anything else. If they don't write the test first, it's possible that the test will end up testing the wrong thing and thus they can't be sure they really did fix the bug.

Sometimes it's hard to tell where to write the test ahead of time, so sometimes a slight variation I do is to write the test after (usually because it was such a struggle to figure out where the bug is), but when I'm testing it, I'll comment out the fix or whatever and make sure the test fails.