77 ms·
I wonder why whenever such a discussion pops up, almost nobody mentions the stacktrace. I've seen so many CS students, who fail at reading that first representa
by rmetzler 10y ago
I wonder why whenever such a discussion pops up, almost nobody mentions the stacktrace. I've seen so many CS students, who fail at reading that first representation of a problem, I really wonder why that is.
Also I like debugging via print much better than with a debugger, because it's easier for me to spot the problem. Breakpoints are great though.
- problems 10y agoThat's not quite the sort or debugging being discussed here though - they're talking general theory of how to think through a problem to locate the issue, which applies to more things than just software including computer hardware, cars, circuit boards, just about any large system really - you do common things like replacing or disabling parts of the system, probing values at certain points, logging values, etc. For the most part, these things have a lot in common, but few people know how to approach such problems. It's interesting that I see them saying "the more talented the engineer, the more likely they are to hit a debugging wall outside of school". I was only ever a good engineer in school because I was able to debug. You don't understand something til you tear it apart.