Model Essay Policy
From Coder Merlin
Revision as of 20:34, 15 December 2019 by Chukwuemeka-tinashe (talk | contribs)
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
- Specifically, the entire text must be stored in your Journals directory. Links to external repositories (e.g. Google Docs) are not acceptable.
- Be sure to cite 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"
Grading Abbreviations[edit]
- B
- (Bibliography) Sources not specified
- CF
- Confusing flow
- FE
- Factual errors
- G
- Grammar
- GA
- Awkward
- II
- Insufficient improvements from previous draft
- LL
- Low Level of Language
- MT
- Missing required topic
- NS
- Non-sequitur
- P
- Overly long quotes / padding / Repetition / Unrelated topics
- PN
- Punctuation errors
- S
- Spelling
- T
- Lack of professionalism / appropriate tone
- UA
- Unsupported arguments
- UC
- Unclear conclusion
- V
- Vagueness
- WC
- Insufficient word count
