Code Smells: Identify & Refactor

[antfarmar]

The current first-iteration playable implementation has the following Code Smells:

Application-level smells:

• Duplicated code: identical or very similar code exists in more than one location.
  • e.g. Not many reusable methods/interfaces were used. Unity API was used directly most of the time for familiarization.

    Class-level smells:

• Large class: a class that has grown too large. See God object.
  • e.g. GameManager currently knows & does too much.
• Lazy class / Freeloader: a class that does too little.
  • e.g. AsteroidBehaviour subclasses really don't do much at the moment.

    Method-level smells:

• Long method: a method, function, or procedure that has grown too large.
  • e.g. See duplicated code above. Most solutions were written with a direct approach.

[antfarmar]

The current implementation has been largely refactored. :melon: The code smells may now be on the opposite side of the spectrum. :rainbow:

[antfarmar]

Issue may be reopened when glaring code smells are identified and require resolution.