There's a difference between cheating because of time constraints and cheating because you can't comprehend. I've worked with a developer who cheated durring school and his resume looked great - GPA, etc. When working with us, he didn't know much and would ask basic questions (Google-able questions). Eventually it was discovered that he was basically outsourcing his projects from work because he didn't know how to do them - no really, he had someone else write code for him outside the company. So when he was explaining the code, he crashed and burned.
I personally "cheated" on projects in school because I didn't have enough time to get them done (work full time + school full time = not enough time). So when I "borrowed" code for something like a QuickSort (HeapSort, etc), I would at least go through it to understand it and generally after taking one stab at it by myself first. And I wouldn't do a direct copy/paste, I would at least make it "my" code.
I digress; my point is that "cheating" isn't the end of the world if the "cheater" is competent. And I agree with this message's parent. In a corporate environment if I can find code to get the job done quicker instead of writing code for the sake of writing code, then do it - as long as you're not breaking a copyright.
One more case in point. I spent 20 hours learning Service Broker (don't hate me for mentioning a MS product), I could have written my own queueing technology in 60 hours (that would have holes). It's the same but different.