in reply to Re: When do you step in, and why?
in thread When do you step in, and why?
Reminds me of what a professor did in one of my college classes, an algorithms analysis class.
The first assignment we received was a problem that many of us wondered why she was giving us so long (2 weeks) to complete, as simple as it sounded: given a group of entries, their weight and values, what was the combination below a certain weight that would give the most value?
It was after she took up our programs that she told us that it was called the "knapsack problem," one of a class of problems called NP-complete, and that one of the data samples had been designed specifically to approach the CPU time limit for users of our user group. After that, most of us never underestimated the projects we were given in that class.
I disagree only in one point-at the point they are in the trap you mentioned that deeply, either they will accept your advice without force, or they will reject it completely, feeling it a challenge to their knowledge that they must overcome without help. Many times they will reach a point at which they will be asking around for help, if they realize how deeply they are in it (and the subject isn't classified or need-to-know, such as the automated system for initiating a SCRAM(1) in a PWR(2) based on instrument readings in something like the last situation given).
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Re^2: When do you step in, and why?
by Anonymous Monk on Jul 21, 2002 at 20:11 UTC |