2

Why is debugging like finding a needle in a haystack, except the needle is on fire, the haystack is on fire, and everything's in JavaScript? If debugging is removing bugs, then programming must be putting them in!

And Git blame? More like Git shame! Every "fix stuff" commit is a reminder that past-me was a jerk.

End rant. Back to code. May the coffee be strong and the bugs be weak. 🐛☕💻

Comments
  • 1
    Needles and haystacks burn in very different conditions, so if they're both on fire then the needle is unlikely to be in the haystack.
  • 3
    Burning the haystack may help you find the needle...
  • 1
    @Ranchonyx i don't think people would find it appropriate to shutdown prod for whenever you're tracking down bugs.
  • 2
    @thebiochemic I was thinking metaphorically, as in "discard current way of thinking, try another way".
    However I'd agree with you.
  • 2
    Juggling between dart, c#, php and javascript, I can say that JS is definitely the worst of them all. Even Jetbrains IDEs who is very helpful on everything, throws their hands up on JS. Their decent intellisense, suggestion and quick documentation literally die when it comes to handling JS. To all of you who work with JS exclusively, good luck!
  • 2
    @thebiochemic make another prod and shut down the first one
Add Comment