Starting today you can subscribe to a daily or weekly emailed newsletter from java.net with a summary of our front page.
This is a great example of why we should follow Kathy Sierra's advice about talking to our customers in Have your developers seen a real customer in the wild? I don't like to get site updates in email. I prefer to subscribe to blog feeds. So we launched java.net with blog feeds and folks who liked receiving their news that way worked with us to help us improve the way they looked and behaved. The blog also was the lead article on the home page so we figured that people who didn't use newsreaders could still find the piece on our site.
But, we were told, the daily blog helps some people decide whether they will even come to our site. Others told us that they don't feel engaged in a group or community without getting regular email. The good news for us is that it was easy to implement. The Collabnet side of java.net includes mailing lists. We ran a couple of days of trials before announcing it and we will provide a more clear page for subscribing to the mailing lists and RSS feeds.
The Daily Update is sent weekdays with a summary of the items new to the front page. Again, because I'm not a fan of html email, this is plain text - if you feel strongly that it should be html we may revisit this issue. The daily piece includes bullet points with the news items and upcoming events as well. Where the daily blog has links to all of the stories, the email version contains a link to the front page and to the daily blog (which is formally known as the Editor's Notebook).
The Weekly Update will be sent Fridays. Initially, these will just be taken from the daily update but provided for those who don't want email every day. The weekly update will not include the news or event items as they may no longer be relevant. You can take a look at the archives before deciding to subscribe.
All java.net members can subscribe to the email updates for the site at the java-net Mailing Lists page. The lists are javanet_Daily and javanet_Weekly.
In Also in Java Today, when you are working with measurements in Java it would be nice to be able to not just say the length is 5, but 5 whats. Does the number 5 indicate a number of inches, feet, kilometers, or lightyears? In " Apples and Oranges and the Java Units Specification", Ori Kushnir looks at JSR-108 and presents introductory code examples for working with units and dimensions.
Martin Fowler blogs about the links between object-oriented development and iterative and incremental development. He argues that "there's technical reasons why objects encourage IID, but also there's social reasons. The leaders of the OO world pushed IID right from the beginning, which is why it's no surprise that the leaders of the agile movement almost entirely are OO people. When the leadership embraces both movements so fervently that has an effect on the whole community."
In Projects and Communities, the JXTA community's James Todd writes "Some of our Sun JXTA team members will be at LinuxWorld January 21-23 talking about the technology at the Sun booth. If you're in the New York area, please stop by and let us know what you are up to."
Last month NetBeans community representatives were elected to the new NetBeans' Governance Board. The winners are java.net blogger Vincent Brabant, David Strupl and the Sun appointed member Zaheda Bhorat.
In today's Weblogs , John Reynolds leads with Debugging tales - 'Improbable' != 'Impossible'. He tells (in great detail) of an episode in debugging and emphasizes that we should Try the easy things rather than discussing them. He explains, "The rub is in determining what is improbable rather then impossible. Knowing your system well can be a double-edged sword. On the one hand it quickly helps you identify probable causes, but on the other it can lead you to dismiss options too quickly. I think that's what happened to us. We talked ourselves through a trivial test rather then performing the test."
Richard Monson-Haefel's post Groovy, Baby! is about "an awesome new scripting language for Java called, Groovy [which is] a beautiful language and fairly easy for Java developer to learn." Richard writes that "Groovy is not a replacement for Java