1130
submitted 11 months ago by willya@lemmyf.uk to c/programmerhumor@lemmy.ml
you are viewing a single comment's thread
view the rest of the comments
[-] e0qdk@kbin.social 112 points 11 months ago

Rule 9 from Agans's Debugging: If you didn't fix it, it ain't fixed

Intermittent problems are the worst...

[-] marcos@lemmy.world 34 points 11 months ago

The problem is, how do you fix it if you can't make it break?

The worst thing is when somebody comes to you saying "yeah, I had this problem yesterday, but it's working now".

[-] ryannathans@aussie.zone 1 points 11 months ago

You should have a unit test you can run until failure

[-] folkrav@lemmy.world 6 points 11 months ago

Fully agree, but they're usually kind of annoying to track regardless. On the opposite side, sometimes even getting it to trigger on purpose to be able to add a regression test can be pretty tricky, depending on the cause. Timing or time/date based stuff is a common culprit...

[-] ryannathans@aussie.zone 5 points 11 months ago* (last edited 11 months ago)

Don't tell me about time and date, I am still recovering from some moron that used datetime.now() for some unit test data setup and sometimes two records (which needed to have the same time) had very slightly varying time which caused all sorts of intermittent test failures that were very tricky to nail down. Database triggers were failing causing failures in all sorts of tests in a random fashion

this post was submitted on 11 Oct 2023
1130 points (100.0% liked)

Programmer Humor

32058 readers
1540 users here now

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

Rules:

founded 5 years ago
MODERATORS