Earlier quoted context omitted.
Good lord, I'm not glad. It was horrible . Because it wasn't about "figuring things out for yourself." I mean, if the answer was available in a programming language or library manual, then debugging was easy. No, the problem was you spent 95% of your debugging time working around bugs and unspecified behavior in the libraries and API's . Bugs in Windows, bugs in DLL's, bugs in everything. Very frequently something ju…
>I'm so happy people today don't suffer the way we used to suffer. TBF Ali bugs in some framework you're using still happens. The problem wasn't eliminated, just moved to the next layer. Those debugging skills are the most important part of working with legacy software (which is what nearly all industry workers work in). It sucks but is necessary for success in this metric.
My point is that I can frequently figure out how to work around them in 5 minutes rather than 2 days, because someone else already did that work. I can find out that a different function call is the answer, or a weird flag that doesn't do what the documentation says, or whatever it is.
And my problem of it taking two days to debug something is eliminated, usually.