What's your worst debugging experience?

I just had it today and yesterday when I tried to connect to an aws postgres rds..... 😭😭😭

every day is my worst debugging experience. Trying to decode thousands of abbrevations which made sense only for few minites until the guy who invented them didn't forget what they mean.

@Murder Gosh😳

When the debugger shows wrong values stored in a variable because it failed to take the one with the same name from the current scope of the breakpoint and confused it with some other scope (probably).

If you can‘t trust your debugger, then all hope is lost.

SSH Hopping.

When your upstream is really less than modem and you need to type very carefully cause the lag between input and display is high.

... But very useful when combined with an SSH Socks Proxy.

It gets even less funny when the multiple hops include ancient SSH, so you'll have to write the proxy jumps without -oProxyJump.

Funny times.

External Firewall -> internal server (bastion) -> separate second firewall for different network -> intermediate server -> target server (can only be reached via intermediate server, intermediate server is a bastion server).

... Dig deep xD

Had a project I was working on and for two days straight could not for the life of me figure out why it was throwing an error. Nothing made sense. Turned out to be a rogue comma which was hiding so well in the code it was hard to see. So, f’ing annoying I didn’t spot it. Changed the line height and letter spacing after that.

Remote desktop on tech support's mac with a 6 hour jetlag to troubleshoot the automotive hardware systems of an angry customer threatening to rip apart the contract they had with our company because quite frankly, the system we had the misfortune to inherit and work on was a pile of racoon crap.

Tech support was also threatening to leave the company if we did not do something right now.

I am pretty sure I became an alcoholic after that.

A tie between trying to figure out what the F is slowing my job down in AWS Glue with neither access to a dev endpoint nor ability to see the Spark DAG, and trying to rebuild a Scala application so it uses string manipulation and regex instead of NodeSeqs for changing XMLs because the libraries we built in house were hot garbage and jacked up the namespacing on the nodes