Overlord - Iteration 1

Program Structure:

- overlord.rb: contains my controller code; my aim was to keep this as light as possible.
- bomb.rb: my aim was to keep the state and behavior of anything related to the bomb in this class.

I used Twitter Bootstrap for the design of the front end. I will improve the look and add client-side validation for the user code input after this review. I wanted to submit a pull request for the bulk of the work as quickly as possible.

Test Structure: I wrote Cucumber features for the integration tests and used RSpec for the unit tests on the Bomb.

Thoughts:

1. In Bomb#analyze_user_code, I couldn't figure out a way to avoid the case statement, so I apologize. :) Please let me know if you see another way.

2. I used Ruby 2.0's Keyword arguments for my class definitions, so line 20 of overlord.rb is rather long. I can't see a way around this.

Thanks!



Does this mean that I can turn a bomb from exploded back into activated? That's confusing.