Some undocumented, never touched, 15 years old recursive function at the core of our business model suddenly stops working in a niche scenario, debugger is not available and I have to find out why.

Time to do paper debugging ✏️📃

.

Who needs a debugger when you have print statements?

Just read the code and the bug should be obvious.

@Oktokolo it’s javascript

@Lensflare In that case type checks have to be added to the start of the function to make sure, the input triggering the bug is of the expected type.

After that in-brain static analysis can be performed as usual, because the language literally doesn't matter when you actually do a full static analysis of all execution paths yourself (which i definitely don't do for 99.999% of the code i write).

@Lensflare AAAAAAA AAAAAAAA
AAAAAre you sure there is NO debugger? None? null? !1?

Oh also, step 1 REPRODUCE THE DAMN ISSUE

@melezorus34 I didn’t say there is no debugger

@Lensflare oh yeah. Op did. Sorry, I'm just exhausted

If you already isolated the issue to this particular function. Extract the function write table driven tests for it until you find the issue or have full line coverage. If you have full coverage and the undesired output is still not present you need to do every combination of lines possible. If it still does not occur it's likely not that function.

ITT

> me, whining about a complicated task

> people, telling me what I should do, and "what I should do" is exactly the reason why I'm posting this in the first place

@IHateForALiving
> is dev
> stucc

dun't care, want it done by previous year

@IHateForALiving yeah fuck your life

fuck my life indeed