To help structure your work, here are 22 challenges. They all build on one another. They require you to research things, to get stuck, and to find your own solutions. This is on purpose. A developer is a 'knowledge worker' - someone who will spend the majority of their time researching and learning how to solve problems. It'll suck for a bit, but with practice, you will get faster: and there's no better feeling than finding the answer to a problem that's been standing in your way for hours.

Setting up the project (Git repo)

To complete this challenge, you will need to:

• Create a directory from the command line
• Initialize a git repository within that directory
• Create a README.md file from the command line
• Write a clear README
• Add the README.md to the staging area
• Commit your changes with a clear message
• Push the project to Github.

Converting user's stories to Object-messages tables

To complete this challenge, you will need to:

• Start irb (or any other REPL) from the Command Line
• Set a variable docking_station equal to a new DockingStation object
• Explain to your pair partner what the resulting error means.