Overlord

NOTES: the previous file code_registration.feature was cruft that should have been removed before submission. Gone now.

About: Given(/the bomb is not started/) do

I've changed it to be "given a new session". It's still a no-op though, just because capybara always initializes a new session when used in the way it is here. But, I still though it bears mention in the test because it is a necessary precondition of the test even though it happens to be granted for free. Because it is necessary for the test to be valid, does it make sense to include it even if it gets to be a no-op in practice?

I really liked your advice about using attr_accessor even when intending to override one of the resultant accessors.

About multiline strings: I'm actually using a tactic that Blake suggested he would prefer. His bent is that splitting strings across lines pretty much shouldn't be done. So he advised me to move long strings into a string table where they're not polluting code readability but can also be left unbroken up to reasonable lengths. Would you advise the same?

The only place instance attributes/variables should ever be used as setters(initialized) using the ``@syntax``` is inside of the initialize function;
* if they are intended to be readers( ```@locked && @armed```)
 - elsewhere in your code you are setting these using ``@armed = true/false``, if you intended to set them so often it should likely be an attr_accessor
* if they are accessors(read+write):
 - else where in the code you should get/set these attributes using the implicit format ```(self.)disarming_code = x # the 'self.' portion including paren can be omitted
disarming_code = x # same as self.disarming_code```