Blogs by topic JavaOne and user bboyes
| • Accessibility | • Ajax | • Blogging | • Business | • Community |
| • Databases | • Deployment | • Distributed | • Eclipse | • Education |
| • EJB | • Extreme Programming | • Games | • GlassFish | • Grid |
| • GUI | • IDE | • Instant Messaging | • J2EE | • J2ME |
| • J2SE | • Jakarta | • JavaFX | • JavaOne | • Jini |
| • JSP | • JSR | • JXTA | • LDAP | • Linux |
| • Mobility | • NetBeans | • Open Source | • OpenSolaris | • OSGi |
| • P2P | • Patterns | • Performance | • Porting | • Programming |
| • Research | • RMI | • RSS Feeds | • Search | • Security |
| • Servlets | • Struts | • Swing | • Testing | • Tools |
| • Virtual Machine | • Web Applications | • Web Design | • Web Development Tools | • Web Services and XML |
JavaOne
I say yes, we must -- if we want shared code to be easy to understand and use. And isn't that the whole point of a code-sharing community?
Well-written and documented code which has problems can be fixed by the community. Undocumented code is not only hard to use (maybe impossible), but cannot be maintained. So isn't conformance to some minimal coding standards essential for making this community a success.
It's 10PM and we're wrapping up the first day of the first-ever Java Community Leader's Weekend.
