I didn't cheat once through a CS degree gained in the early 90's (as my sometimes shabby, sometimes ok results would show), but I was made hard to think about w

I didn't cheat once through a CS degree gained in the early 90's (as my sometimes shabby, sometimes ok results would show), but I was made hard to think about whether a certain incident was cheating or not. One of my final year subjects involved a group project; we had to develop a PDA-type collection of applications, so it fitted well with a group project. The 'calculator' guy never turned up to any programming sessions or meetings aside from the initial one - someone else ended up hacking together his app in the last day - and then 60 minutes prior to the submission deadline. Back then we had to put together a paper project outline and notes, and there were strict requirements for it's submission format; laid out like so, printed like so, index like this, bound like that. If this paper submission was a minute late, we'd be docked 50% (!) of our overall marks. Four of us were panicking, with < 1hr left to submit, our project unprinted and unbound, and us with no idea how to operate the required machinery. The fifth member, our 'calculator' guy, actually shows up, and then proceeded to, unassisted, blitz through the printing, collation and binding of the project. We eventually submitted a minute or two prior to cutoff, and got a good mark; without the 'calculator' guy, who did no programming whatsoever, we would have been in big trouble. I've always wondered if he went on to be the 'binder guy' or 'fixer' IRL after graduating.