Andreas Aronsson

These two are terrific and should be spoon-fed to anyone who neglects the importance of OOAD:
http://web.abo.fi/~peholmst/DecouplingJavaClasses.pdf
http://www.mockobjects.com/book/
Plenty useful.

Also this is a goldie:
http://www.javaworld.com/javaworld/javaqa/2000-03/02-qa-innerclass.html?page=2

It's been a bit too long since I did a post so I thought I'd post some thoughts about the creation
of software and cooperation in a small group with tools we're using like UML, design patterns
etc. I'm assuming that a sufficiently thorough analysis has been made and that the group comprises
about two to four developers. This would be the optimal course of action for my personal taste and
knowledge level at this time.

What I experience when I grasp a subject or when I discover that I've achieved some level of mastery at something, that's how I percieve what happens. First contact with a software project or product is often daunting in my mind. There are so many details that your working memory rapidly becomes overloaded. After time, your brain manages to do what it does best; filtering the avalanche of data we're exposed to and effectively extracts only what's needed for the conscious part of the mind to make sense of the object of our interest.