Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail From: Novice Newsgroups: comp.lang.java.programmer Subject: Re: Aspect questions? Date: Wed, 29 Feb 2012 14:54:54 +0000 (UTC) Organization: Your Company Lines: 30 Message-ID: References: <4f4a6b1d$0$290$14726298@news.sunsite.dk> <4f4ac151$0$291$14726298@news.sunsite.dk> <4f4ad9ff$0$292$14726298@news.sunsite.dk> <4f4c3df1$0$281$14726298@news.sunsite.dk> NNTP-Posting-Host: Dmxgbnvd+eoRDUV2lwYf7Q.user.speranza.aioe.org X-Complaints-To: abuse@aioe.org User-Agent: Xnews/5.04.25 X-Antivirus-Status: Clean X-Notice: Filtered by postfilter v. 0.8.2 X-Antivirus: avast! (VPS 120229-0, 2012-02-29), Outbound message Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:12527 Patricia Shanahan wrote in news:CaCdnXluDfclPdHSnZ2dnUVZ_gmdnZ2d@earthlink.com: > On 2/28/2012 12:04 AM, Lew wrote: > ... >> You illustrate one way in which programming is a matter of art. > ... > > When it does come down to an art, after applying whatever science I > have available, I often resort to the "What is easiest to document?" > test. For example, I like a method for which it is really easy to > write a Javadoc comment, especially the first sentence. > > To apply this to a packaging issue, try to write the Javadoc > description(s). > > If you find yourself, within one package, having to say a lot about > some particular subset of the classes, consider making that subset a > separate package. The subset has a lot of commonality or interaction. > > If you find yourself doing a lot of cross-referencing between package > descriptions, or repeating a lot of material, you may have divided > things up too much. > I like this approach. As someone who often starts with comments and then writes code, this appeals to me. -- Novice