wrote test for the one method committed previously (against best
practice) : because it was simple to do and didn't want to forget. note
to self : never do that again (it didn't go wrong but could have).
Next Stages : review all interface specifications for things i might
have missed to implement (like multiple aliased for the same contact)
and start tdd for ContactManagerImpl. note: because i have reached
problems with unit testing at this stage before, I now have to carefully
think ahead how will I structure the information in such a way that is
wholesome, but without spending too much time on it either. Good
starting point is to look at the private method guidelines for the
non-tdd branch of this project. Also, realized that best way to test
private methods is to actually implement them separately as new classes
that are called within the code. This learning curve will help
accelerate the rest of the process. Also started a local file with notes
on ideas of how to increase performance of the whole thing to be looked
at once the basic specs of the program are done (and assuming i have
time for them)