Comments by "" (@adambickford8720) on "STOP LEARNING LANGUAGES | Prime Reacts" video.

But debugging is 10x more than just inspecting variables. Things like dropping frames, changing values on the stack, etc, saves me a ton of time.
127
@suede__ Literally never had or seen that happen. The only thing i've ever had 'fail' due to debugging was timeouts and mulit-threaded code, which is completely expected.
15
@muhwyndham just the fact i can trivially break encapsulation is huge, especially with 3rd party stuff.
4
@chigozie123 i dont have to restart the app server, get things back to the state that the bug appears in, etc. I can just return/change a new value from the debugger, no need to bounce the app. You can also use good old 'printf' in a non-suspending break point; no need to soil the source code. Then, if i don't need it i just disable the breakpoint vs deleting the printf. If i need it back, i re-enable the breakpoint. You can even mange groups of these printf breakpoints in intellij to enable a bunch with one click. The fact i can drop frame in case i manually step too far is a coincidence 👀
1
@CodeFun691 or, just maybe, that's the kind of codebases actual engineers end up with? Why is it the more aggressive they are, the dumber? Its beyond correlation at this point.
1
@vitalyl1327 you might be in some crazy edge case where it's not useful, but for 99.9% of projects it's an unambiguous win. Aggregating and analyzing gigs of logs for simple stuff is easily an order of magnitude less productive in the vast majority of cases. And you missed the point, logging is a small fraction of what a debugger is capable of. Logging only solves that portion with debatable 'gains'.
1
@NeoChromer i honestly feel its insecure devs trying to 'flex' they don't 'need' a debugger.
1