Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Root56917203dIt was caused by a cosmic ray or microscopic black hole.
ddephor4827203dMultithreading issues. But you can be sure it never works right, it just appears to be right at some point.
kwilliams5689203dI tried to write a unit test for code who's outcome is different depending on what the date/time is on the database server.
PS: I know you would normally isolate the database with a mock, but it was a database function being tested.
Wack6839203dMultithreading or undefined behaviour. Listen to your compiler kids...
atheist2282202dOr uninitialized memory if you're in a language that supports it!
Fast-Nop22249202dIf your code doesn't ALWAYS work, it has a bug, it's as easy as that. Working sometimes or just on your machine doesn't count.