Does anyone hate debugging something for a couple of hours just to find out it was you misspelling something that somehow managed to not cause an error?

Also what are the worst things to have that cause a error? Like dependency being outdated and not being notified etc.

Last week I spent an hour trying to find out why an app returned an error message instead of the expected result. About half an hour in we discovered that the result was indeed ok, but somehow the error branch was still taken. It took us a moment to find that the constants representing success and fail were set to the same value.
On the plus side, the next time that error showed up we only needed five minutes to find it.

@korrat if you get something wrong you have more chance of remembering it, Can be useful.

@ForgottenR4 Sadly, it always takes a while to figure things out the first time, when you don't know what you're looking for yet. That's why making a variety of mistakes is helpful because you teach yourself a lot of errors and how to find and fix them. Then, when you (or anyone else) makes them again, you have experience to fall back on.

Simple things like what you're talking about often feel worse because our need to be in control and do everything perfectly is violated. Fortunately, fixes are often very simple, so we can tell ourselves that fixing it was easy instead of how stupid we are.

Also, welcome to devrant.

You could actually stop after "Does anyone hate debugging". Yes, ugh, debugging can be such a huge time sink.

The worst error causes are class loader problems in Java. If a string is suddenly not comparable to a string... or a piece of code throws NoClassDefFoundErrors for a class that is happily in use in the rest of the code... you're in for some digging.

My kingdom for a semicolon not out of place.

FUCK.

Every time I mention semicolons I have to insert a fuck or two now.