week_4

Ruby Algorithms

So you've done some preparation on Ruby, and have probably been wondering "Why did we have to do all those exercises before Phase 0 if we weren't even going to start with Ruby?" Well, now is your time to get back to it while using the blog and skills you learned in unit 1.

This week you will be working on writing command-line programs focusing on algorithms and basic testing. Some challenges will also have tests already developed using RSpec (a tool for testing ruby code). You will learn how to run these tests on your computer and read them to figure out what the errors are. NOTE: You are not expected to write RSpec in Phase 0, just read it. RSpec is designed to be readable.

Install and read a bit about RSpec before you begin. If you have trouble, ask for help on the google+ community.

**Please make sure to follow each step we ask you (in order): write driver test code, pseudocode, initial solution, refactoring, reflection, and review.

This week you get a bit more choice on which challenges to do. If you want to go above and beyond, do all of them!

Challenges

1. Mathy Challenges Select 2 of the challenges
2. Homework Cheater Select 1 of the challenges
3. Group Research Methods
4. Separate Numbers with Commas SOLO CHALLENGE
5. Pad an Array
6. Cipher Challenge Pair with a person in your accountability group
7. Refactor Select 1 of the challenges
8. Technical Blog
9. Cultural Blog

Submitting your work

This week you will be storing your reflections in the challenge files in this repository.

• Fork this (phase_0_unit_2) repository by clicking "Fork" at the top right of the page.
• Under settings (in the right navigation bar) check the box next to "issues" under "features." This will allow people to give you feedback.
• Open your GitHub desktop app. Find the phase_0_unit_2 repository and click "clone to computer."

When you make updates to the files on your local repo, you should commit your work the same way you did for your github.io and phase_0_unit_1 repo through the app. Include a commit message like "added pseudocode and initial solution for add it up."

NOTE: Sometimes we will make changes to the original repository to clarify instructions. You will need to fetch these changes from the master branch when we announce changes on the google+ community.

• If you are doing this from the Github Desktop App, follow these directions.
• If you are doing it from the command line, follow these directions.

You will want to run and modify all files from your local repository on your computer. Use the terminal to navigate to the 'my_solution.rb' files or the spec files.

When you make updates to the files (or add a file), you should commit your work the same way you did for your website through the app. Include a commit message that describes what you've changed.

You need to submit your work through a form (to be released) by Sunday at 11:59pm. Expect to submit the links from your repo for each challenge above.

Remember your Unit Goals!

• Pair at least once this week with a member of your accountability group. You need to pair 4 times this unit
• Give feedback for each person you paired with. You need to submit at least 5 pieces of feedback in this unit (4 for peer-pairing, and 1 GPS)
• Rate at least 7 pieces of Meta Feedback on Socrates. *You need to rate 20 pieces of feedback per unit.

Resources

These are for reference if you want some additional sources.

• Introduction to Refactoring
• Ruby for Newbies
• Ruby Variable Scope
• GangesLearning (Videos)
• The Well-Grounded Rubyist (Book)