I quite liked the guidelines in that blog post. I don't do exactly that myself, but as rules of thumb they aint bad! But like a few folk have pointed out, it's

I quite liked the guidelines in that blog post. I don't do exactly that myself, but as rules of thumb they aint bad! But like a few folk have pointed out, it's about personal style, background and context. One thing I like to do is use naming of Packages & Namespaces to tell a story about the system. So, you can look at the packages and understand what the important aspects to the system are. Example: - Spidering - Feeds - Pages - Control - Indexing - Strategy - Scheduling - Lucene Also, when you return to a code base years later, you can scan the namespace story to get a reminder of the key areas of the system.