Remaining abstractions for complexity and change rate test-driven - red test

The first 90% of the code accounts for the first 90% of the development time.  The remaining 10% of the code accounts for the other 90% of the development time.
		-- Tom Cargill
Test-driven implementation with instanceof
- since we have getters, instanceof for now is best
- implementation is in ifs on complexity / change rate using ternary op
- green tests, all tests working
- cut doubles - we have parametrized test for whether quadrants are
  detected well, we don't need four specific test where one parametrized
  is enough

We are Microsoft.  Resistance Is Futile.  You Will Be Assimilated.
		-- Bumper sticker