Skip to content

Instantly share code, notes, and snippets.

@slugbyte
Last active April 22, 2016 21:14
Show Gist options
  • Select an option

  • Save slugbyte/d00a12adbd693b9572b972e3885972e7 to your computer and use it in GitHub Desktop.

Select an option

Save slugbyte/d00a12adbd693b9572b972e3885972e7 to your computer and use it in GitHub Desktop.

grading check list

BEFORE YOU START

  • create folder for grading all student work in your section
  • create directories for each of the students in your section

Checklist

  1. did they answer all the questions in there comments on canvas
  • if no
    • dont grade and ask them to answer the quesetions and resumbit
  1. clone the students repository
  2. check for passing linter
  • if yes
    • keep grading
  • if no give a look over the reset of the document
    • if they tryied give them up to 5 points and ask for a resubmission
    • if they they did not try give them 0 points and ask for a resubmission
  1. Write positive github comments for student work that is done well
  2. check for Meaningful variable names
  • are the variable names following best pratices: cammel case
  • do they describe the data they are storing
    • if no leave a comment on their pull requst commit message on github and deduct point
  1. check for Meaningful function names
  • are the function names following best pratices: cammel case, or fisrt capital letter if constructior
  • do they describe the action they preform
    • if no leave a comment on their commit message on github and deduct a point
  1. check for Well-Factored functions
  • is there code well-factored based on how much they know about functions up to this point.
    • if no leave a comment on their pull requst commit message on github and deduct a point
  1. check for Meaningful project structure
  • are the foler names and file names toughtful and following best pratices
    • if no leave a comment on their pull requst commit message on github and deduct a point
  1. check for appropriate level of comments
  • were their comments meaningful
  • were their comments excessive
  • are they lacking comments where they could be used?
    • where they could improve leave a comment on the github commmit message and deduct a point
  1. check for commented out code
  • if they had it
    • leave a comment on the github commit message and deduct a point
  1. check for propper git workflow
  • did they have a meaningful commit message
  • did they have propper use of branches
  • did they have reasinable number of commits
  • did they have a gitignore
  • if no deduct a point and leave a comment
  1. check for Late work
  • if the assinment was submitted late deduct two points
  1. check for Bonus points
  • if they achieved a bonus/streach goal from the assingment that specified a number of points to add award them the appropriate points using your best judgement
  1. Record total points on canvas
  2. Write a response to stents observation on canvas.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment