Difference between revisions of "Model Essay Policy"
From Coder Merlin
| Line 10: | Line 10: | ||
* The essay must be pushed to GitHub on or before the due date | * The essay must be pushed to GitHub on or before the due date | ||
* For all outlines and drafts, use a single document, labeled as '''E'''''nnnn''.txt, where ''nnnn'' is the number of the experience. | * For all outlines and drafts, use a single document, labeled as '''E'''''nnnn''.txt, where ''nnnn'' is the number of the experience. | ||
** Tag the final version of your outline as "Outline" | |||
** Tag the final version of your first draft as "Draft I" | |||
** Tag the final version of your essay as "Final Draft" | |||
Revision as of 17:39, 14 December 2019
Within these castle walls be forged Mavens of Computer Science ...
— Merlin, The Coder
Overview[edit]
For those of you traveling our journey with a guide, below is a potential essay policy. Be sure to ask your guide for confirmation and/or variations from this policy.
Rules for Essays[edit]
- The essay must be written in plain text using emacs
- Use two carriage-returns between paragraphs; do not use carriage-returns within a paragraph
- The essay must be stored in your Journals directory
- Be sure to site all sources, listing each at the end of the document
- The essay must be at least 1,000 words (and no more than 1,250 words)
- The essay must be pushed to GitHub on or before the due date
- For all outlines and drafts, use a single document, labeled as Ennnn.txt, where nnnn is the number of the experience.
- Tag the final version of your outline as "Outline"
- Tag the final version of your first draft as "Draft I"
- Tag the final version of your essay as "Final Draft"
