But sometimes it works the second time because it loaded something in the bg.
Ofcourse. The first stage is denial.
Due to the non zero ammount of times this happened to me… this is like pressing ctrl+c multiple times to make sure you copied the thing. And then pressing shift+ctrl+c cause you aren’t sure if that works in this terminal emulator.
Or the code you are working on is calling a system that is currently unreliable which you cannot be responsible for.
Fuck test automation, it’s a fucking trap get out of it as soon as you can
The first time, I just saw it’s not working; the second time, I was paying attention to the details to see what specific parts aren’t working and clues as to how/why.
tilts tin foil hat to the left…
Works now 👍
Very true, especially when working with recursion. (Debugging recursion sucks)
Valid. You need to know if it’s a sometimes bug or an always bug.
The truly terrifying outcome is that it works after changing nothing. Sometimes bugs are the most fun to squash.
