Skip to content

Instantly share code, notes, and snippets.

@dbc-challenges
Created December 3, 2013 19:58
Show Gist options
  • Save dbc-challenges/8139ec054bdac4f59549 to your computer and use it in GitHub Desktop.
Save dbc-challenges/8139ec054bdac4f59549 to your computer and use it in GitHub Desktop.
Phase 0 Unit 4 Week 2
=begin
As you are debugging, ask yourself:
* Do you have enough information to decipher the problem?
* Is the error message referencing a line in your file, or a different file?
* Is there a methodology that you are following to systematically tackle these bugs? What is a step by step approach?
###2) Decipher the bugs
For each bug (there are three initial bugs that cause interpreter errors), answer the following questions:
--- Bug 1 ---
* what is the exact description of the error?
* what is the exact line number the error is appearing?
* before you fix the bug, what do you think is causing the error?
--- Bug 2 ---
* what is the exact description of the error?
* what is the exact line number the error is appearing?
* before you fix the bug, what do you think is causing the error?
--- Bug 3 ---
* what is the exact description of the error?
* what is the exact line number the error is appearing?
* before you fix the bug, what do you think is causing the error?
###3) Pass the tests
--- Last Bug ---
The last bug isn't causing interpreter errors, but it's causing the output of the program to fail the RSpec tests.
When you solve the error, describe what is happening as clearly as possible:
###4) Review your process and methodology
* What were your steps to tackle this problem?
* Write down the processes you followed that could be applied in other debugging situations.
###5) Submit and Reflect
Review other solutions and the canonical solution listed on the "Review and Reflect" tab.
Take a moment to reflect on the canonical solution and the solutions of other students. Add any insights to your gist to help distill your own process here:
=end
###Include your final code below (with driver code and expectations!):
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment