1. A DELICATE LOOK AT STEALING CODE By your beloved librarians

2. IS THIS HOW YOU ACT WHEN CREATING A CODE FOR CLASS?  Why? CODE

3. Why Not… Get caught and get an F for your “effort” You could get into a lot more trouble!

4.  He said he only wanted to take “open source” files in which he had been a creative part, but WHOOPSIE! He accidentally took more than he intended. (Graybow 2009).  His dashing good looks will no longer be enjoyed on the dance floor.  THIS COULD BE YOU! “OOPS!” DOESN’T CUT IT

5.  10% or less of a code can be used as long as it is CITED.  If it is open-source code, you can use it as long as it is CITED.  If it is copyrighted, you must get permission and make sure it is CITED. CODE GUIDELINES  Many developers say you should learn from others’ code, but NEVER copy it exactly. Use it as a spring-board for what you want to do. It’s like paraphrasing in a paper or using elements of an artistic style in a painting. NEVER, NEVER, NEVER copy pictures or format!

6.  You MUST put credit in a comment tag at the end of the code, and it should include the person or company that created the code. Use the coding:  For example:  You MUST also create a References page with all borrowed materials in APA format, BUT... CITATION REQUIREMENTS

7.  NOODLETOOLS is the answer to your needs for quick, painless, APA format! NOODLETOOLS DON’T WORRY, BE HAPPY

8.  Graybow, M. (2009, July 6). Update 4-ex-goldman programmer out on bail in theft case [Newsgroup message]. Retrieved from http://www.reuters.com/article/idUSN0626817420090706  [Sergey aleynikov dancing] [Edited Photograph]. (2010, February 13). Retrieved from http://assets.nydailynews.com/img/2010/02/ 13/alg_sergey_aleynikov_vid.jpg REFERENCE