Earlier quoted context omitted.
> Surely you shouldn't need to struggle in the dark so much to learn. You have it all wrong, IMO. Successfully clawing their way out of the dark is by far the most important skill they're learning.
I recently had to write a scheduling algorithm for our home-grown operating system. I was running into some very difficult to debug issues, so I asked my TA for help. They had no clue and told me to consult the professor. The professor wouldn't help. Our textbook offered no guidance. We're not allowed to discuss projects whatsoever with other students. So after north of 5 hours spread over a few days of trying to fig…
There is a reason why operating systems and compiler classes are notorious.
However, if 5 hours debugging is too much, I'd get out of the field now. Try debugging something for MONTHS while your bosses are all hanging over your shoulder.
In addition, 5 hours spread out is a problem. Subtle bugs require intense focus and you should be doing 5 hours per session. You have to inload and control a lot of details, most of which are irrelevant, in order to find the thing that really matters.
I really wish I could teach a "debugging class" where I hand groups real code with frustrating bugs. Unfortunately, no CS department would ever let me teach it as it would destroy enrollment.