LmtDNE / mid-term

Evaluating how students are doing on all the concepts we've covered so far

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Prep+ Week 3 Self-Assessment "Mid-Term"

Guidelines

  • This "mid-term" is meant to help you assess how well you understand the material we've covered so far in the class, and will cover topics from the first day through to this week. It is still a self-assessment, meaning it is designed to be a gauge for yourself, so you can identify your points of weakness and what to spend extra time outside of class strengthening. We will also be using these assessments as guides to help the instruction team determine how we can best teach the class moving forward for the remainder of the course.
  • You should be able to finish this self assessment within the two and a half hour class period. It is MANDATORY that you push your code to GitHub at the end of the class period.
  • WARNING NO TESTS: As you can see, we haven't provided any tests. This is so that you can practice debugging without them. Copy and paste your code into your Chrome Console for a quick and easy way to test your code.

Grading Outline

Objects:

Functions:

Higher Order Functions:

Concepts:

Self-Grading Process

After you complete each prompt, assign a grade to each item in the above Grading Outline, using this Grading Scale:

Self-Assessment Grading Scale:

Qualitative grade Meaning
Complete You believe your solution to be fully complete and meeting the specified requirements.
Mostly complete Your solution is well on its way to being complete, but you ran out of time or can't remember exactly how to do one particular aspect. You believe anyone who understands the problem well would endorse your solution as the right one, and know pretty clearly how to finish up any last touches.
Significant progress You have the right idea and were heading in a good direction. Covers everything between Mostly Complete and Attempted.
Attempted You were very challenged by the prompt and had trouble making any significant progress on the problem, but wrote at least one meaningful line of code that appears to be a genuine attempt.
Not attempted Whether you've thought much about the problem or not, you have no lines of code to show for the problem. (Note, you should avoid ever getting into a situation where this is the grade you'd give yourself. Make a passing attempt at each problem before going back to complete any one problem.)

Example Submission:

Objects: COMPLETE
Arrays: ATTEMPTED
Functions: SIGNIFICANT PROGRESS

Starting every problem

You are expected to at least start every problem. As with any test, you make the most progress in the first few moments of work on each question, and we don't want you losing out on credit you could collect just because you get fixated on one or two questions. Do an initial pass to get the easiest answers out of your system, then go back and improve anything you can.

Submitting Solutions

VERY IMPORTANT: Before submitting your solutions, find and fix all syntax errors

Solutions are submitted via pushing your code to your OWN FORKED repository. We will take it from there.

Problems

Each assessment contains folders that correspond to the prompts listed below. Complete the instructions in the file README.md within each folder.

About

Evaluating how students are doing on all the concepts we've covered so far


Languages

Language:JavaScript 100.0%