This week's book giveaway is in the Mac OS forum. We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line! See this thread for details.
I often have problem with refactoring some one class which has a lot of nested classes for example in Swing application. What is your advise: strict encapsulation that lead to very long code in one file or extracting nested classes to seperate files and keep references between them?
subject: Clean Code A Handbook of Agile Software Craftsmanship - nested classes