Week 02 Assessment

Guidelines

• Make sure your git is configured correctly, If you are not using your personal laptop, please do the following :

1. Check there’s no previous git config git config user.name git config user.email
2. If there’s a config you need to remove it: git config --global --unset user.name "previous_name" git config --global --unset user.email previous_email
3. Now you need to add your config: git config --global user.name "your_name" git config --global user.email your_email
4. open keychain, and check if there is any github account, and delete it.
5. Now you can fork, clone and commit safely.

Assessments are meant to give you and RBK staff an idea of how well you understand, or can figure out, the material that you covered recently.

• Turn off all communication devices such as your phone, email, Slack, etc.
• Fork this repo and clone down your fork to your laptop.
• Commit working code early and often (at least after every prompt). You are graded on your commit messages in addition to the code that you write

[When this code is committed it will] Complete the basic-iteration prompt

• Do at least a little work on every prompt, even if you only leave comments that describe your intent. Leaving a prompt blank is tantamount to failing a prompt. You'll get much more credit even for writing comments or pseudo-code that describe your intent
• You must submit a pull request for all assessments on time (guidelines for how to submit a pull request are below). Give yourself several minutes to do this at the end of the time allotted for the assessment
• The help button is available to you during assessments, how often you use it is up to your own discretion
• After completing the assessment, if there are any prompts you felt you did not do well on, or, that you would not know how to assess whether or not you did well on, make plans to improve your skills on that topic as soon as possible.

Using and Referencing Outside Resources

Each prompt contains a list of outside resources you are allowed to use to support your work on that prompt. Using any other resources, online or otherwise, including previous class materials, or, communicating through any mechanism with anyone other than Hack Reactor staff during the assessments is academic dishonesty and is cause for immediate removal from the course. If you have any questions about whether a resource is available for use, or if you are in need of support, submit a help request.

Submitting Solutions

Solutions are submitted via Pull Request. Follow these steps:

1. From your fork, select Pull Requests and then create a New pull request.
2. STOP. Before you Click to create a pull request for this comparison you must adjust the target branch (aka base branch) to be your username. Once chagned, the pull-request heading should look like this:

hackreactor:username ... username:master

3. Copy and paste the completed Grading Outline into the comment block of your Pull Request.
4. Click Send pull request

NOTE: Only submit one pull request per assessment. You can feel free to continue working on the content and can submit another PR after our incredible Instruction Team has completed reviewing your work (which takes about a week), but submitting multiple PRs greatly complicates our review process and subverts our ability to observe your work in the context of specific time constraints.