if you've run into a bug where it felt "impossible" to understand what was happening -- what made it feel that way? so far I have - you don't understand the system well - your usual tools don't work - it's hard to get information - too many moving pieces
-
Show this thread
-
so many good responses, I especially like: - the bug is intermittent - it only happens on a device you don't have access to - the error message has terminology you don't understand - there's literally no output at all - one of your assumptions is wrong
21 replies 20 retweets 371 likesShow this thread -
more reasons a bug might feel impossible from your amazing replies: - the cause of the bug is something you've never heard of so you can't even search for it - it's VERY SLOW to reproduce and it's hard to stay motivated - the code is not open source
29 replies 14 retweets 257 likesShow this thread
The “wrong assumption” thing can take so many forms. The other day I accidentally gave two tests in a suite the same name and couldn’t figure out why things went so different when I stepped through FooTest with a debugger…
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.