Difference between revisions of "Model Essay Policy"
From Coder Merlin
Line 15: | Line 15: | ||
* 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. | ||
* Commit comments MUST be meaningful | * Commit comments MUST be meaningful | ||
* Tag the versions which you intend for submissions | |||
** Tag the final version of your outline as "Ennnn.Outline" (where ''nnnn'' is the number of the experience) | ** Tag the final version of your outline as "Ennnn.Outline" (where ''nnnn'' is the number of the experience) | ||
** Tag the final version of your drafts as "Ennnn.Draft.#", (where ''nnnn'' is the number of the experience and '#' is replaced by the draft version) | ** Tag the final version of your drafts as "Ennnn.Draft.#", (where ''nnnn'' is the number of the experience and '#' is replaced by the draft version) |
Revision as of 13:51, 25 January 2020
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 outline must include at least twenty bullet points; all of the following rules (other than word count) apply
- The essay must be written in plain text using emacs
- Use two carriage-returns between paragraphs; do not use carriage-returns within a paragraph
- Set fill-column to between 80 and 100
- 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. No fewer than three sources are required.
- The essay must be at least 1,000 words (and no more than 1,250 words)
- There must be a minimum of one substantial revision pushed to GitHub per week (from the week assigned until the week it is due)
- 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.
- Commit comments MUST be meaningful
- Tag the versions which you intend for submissions
- Tag the final version of your outline as "Ennnn.Outline" (where nnnn is the number of the experience)
- Tag the final version of your drafts as "Ennnn.Draft.#", (where nnnn is the number of the experience and '#' is replaced by the draft version)
- Tag the final version of your essay as "Ennnn.Final" (where nnnn is the number of the experience)
Grading Abbreviations[edit]
- B
- (Bibliography) Sources not specified
- CF
- Confusing flow
- FE
- Factual errors
- G
- Grammar
- GA
- Awkward
- IF
- Incorrect file structure
- II
- Insufficient improvements from previous draft
- IT
- Incorrect tagging
- IR
- Inadequate reference
- 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
- TF
- Text formatting
- UA
- Unsupported arguments
- UC
- Unclear conclusion
- V
- Vagueness
- WC
- Insufficient word count