Looking at this thread, the most enlightening post is that the OP is most likely referencing interview question. Is this thread really worth keeping for that, especially given the trolling near the top? It's good of you to think of the hypothetical prof, but what's best for The Monastery should come first, and I am not seeing the benefit. But good question!!
| [reply] |
Is this thread really worth keeping
That's the wrong question. A thread doesn't need to justify its worth in being kept. We should not remove a node merely because a few people fail to see any significant value in it. Not only is that just putting the onus on the wrong side of the equation for philosophical reasons, it also just leads to bad decision making. When that has happened in the past, there usually appear several people who saw the value and the node got restored.
Somebody has to justify the (at least somewhat compelling) reason for its removal.
Which is why considering a node with the reason of just "reap" is against documented practices for the use of "consideration".
| [reply] |
Normally I would agree with you, but for edge cases like this I find it far more interesting (and valid) to let the thread stand or fall on its merits or lack thereof.
| [reply] |
I do believe keeping trail of a rather badly executed attempt to cheat is best for The Monastery. I do hope the attempt is found by the interviewer, the culprit is treated accordingly and either eventually gets removed from the pool of (Perl) developers or is forced to learn what he or she is claiming he/she already knows. And it's even possible that a member of Monastery that did not lie in the CV as much as faten daim will get a chance at the interview and get the job instead.
Jenda
Enoch was right!
Enjoy the last years of Rome.
| [reply] |
aye aye captain edit: I feel it is better to not reap HW so profs can google it up. What do others in the monastery think? This assumes it was actual homework -- highly doubtful
| [reply] |
Might be interview material as well. It is the first hit for swissprot_output.html, interestingly enough.
| [reply] |
