3 ms·
I've been in a situation at a job where we were trying to debug some code, not ruby, but still written very concisely and clever. To even have a chance of debu
by LandR 2y ago
I've been in a situation at a job where we were trying to debug some code, not ruby, but still written very concisely and clever.
To even have a chance of debugging it we had to pull out more variables etc so we could breakpoint each part rather than it being this complicated one liner.
After they debugged it, and fixed it, I watched them rewrite it back into the complicated one liner because it looks nicer...
I just don't get it. It's like they just didn't see the pain they went through.
We built our own hells.
- rezonant 2y agoWas there some kind of side effect that prevented you from simply using the debugger to evaluate parts of the statement to interrogate the results?