What's the longest you've ever been stuck trying to fix a bug or figure out how to build something? Just curious before I bash my head into my keyboard.

At least 3 days.
You just gotta find something else to work on, and then suddenly the solution will hit you.
Good luck :)

@JTBringe thanks. Been stuck for a couple days and it's just annoying.

Not really stuck but the most elusive bugs took 1.5 and 2 years before finding the cause.

Both where intermittent, one we just never managed to recreate (that one still bites us about once every month). The other just was to complex.

With a node tree of up to 2500 nodes before rendering, debugging it step by step was just not possible.

Both for time reasons but also because the debugger usually became unstable after 20-15 minutes of stepping through code with a 200 level deep stack trace (recursive functions).

Only actually found the solution once a colleague managed to find a two element example that triggered the bug.

Not so much a bug as "what the hell was this dev thinking?", has taken me a good week or two to sort

Hours between two datetimes as Epoch in Oracle SQL respecting daylight saving; took three months as I worked on it on and off again.

@JTBringe yep totally a good idea to break away from the frustration,

I had one bug for an iOS app on iPad that never got fixed so I made a work around instead

I think majority of the bugs that took me a long time I just did work arounds lol

Took me about 2 1/2d to find an off-by-one error