Now, at the bottom of this same window, you should see that the file’s default Character Encoding is Unicode (UTF-8) and that the file’s default Line Ending is Unix/Linux. Double-click Dropbox, then double-click hacker1, and you should find yourself inside that empty folder you created. You should then see the contents of John Harvard’s home directory. Input hello.txt next to Name, then click Home under Places. Select File > Save, and a window entitled Save As should appear. Go ahead and type hello (or the ever-popular asdf) on line 1 of the document, and then notice how the tab’s name is now prefixed with an asterisk ( *), indicating that you’ve made changes since the file was first opened. Clearly the document is just begging to be saved. (Recall that Menu is in the appliance’s bottom-left corner.) A window entitled Untitled Document 1 - gedit should appear, inside of which is a tab entitled Untitled Document 1. Okay, go ahead and close any open windows, then select Menu > Accessories > gedit. Viewing another’s solution to a problem set’s problem and basing your own solution on it. Using resources during a quiz beyond those explicitly allowed in the quiz’s instructions. Submitting work to this course that you intend to use outside of the course (e.g., for a job) without prior approval from the course’s heads. Submitting the same or similar work to this course that you have submitted or will submit to another. Submitting (after possibly modifying) the work of another individual beyond allowed snippets. Splitting a problem set’s workload with another individual and combining your work. Searching for or soliciting outright solutions to problem sets online or elsewhere. Searching for, soliciting, or viewing a quiz’s questions or answers prior to taking the quiz. Providing or making available solutions to problem sets to individuals who might take this course in the future. Paying or offering to pay an individual for work that you may submit as (part of) your own. Looking at another individual’s work during a quiz. Giving or showing to a classmate a solution to a problem set’s problem when it is he or she, and not you, who is struggling to solve it. Working with (and even paying) a tutor to help you with the course, provided the tutor does not do your work for you.Īccessing a solution in CS50 Vault to some problem prior to (re-)submitting your own.Īsking a classmate to see his or her solution to a problem set’s problem before (re-)submitting your own.ĭecompiling, deobfuscating, or disassembling the staff’s solutions to problem sets.įailing to cite (as with comments) the origins of code or techniques that you discover outside of the course’s own lessons and integrate into your own work, even while respecting this policy’s other constraints. Whiteboarding solutions to problem sets with others using diagrams or pseudocode but not actual code. Turning to the web or elsewhere for instruction beyond the course’s own, for references, and for solutions to technical difficulties, but not for outright solutions to problem set’s problems or your own final project. Sharing snippets of your own code online so that others might help you identify and fix a bug. Sending or showing code that you’ve written to someone, possibly a classmate, so that he or she might help you identify and fix a bug. Reviewing past semesters' quizzes and solutions thereto. Incorporating snippets of code that you find online or elsewhere into your own code, provided that those snippets are not themselves solutions to assigned problems and that you cite the snippets' origins. Helping a classmate identify a bug in his or her code at Office Hours, elsewhere, or even online, as by viewing, compiling, or running his or her code, even on your own computer. Communicating with classmates about problem sets' problems in English (or some other spoken language).ĭiscussing the course’s material with others in order to understand it better.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |