Many times the toString() format is dependent on how the developer wants to see the state. I've seen formats to accommodate Swing, console, the debugger, and log files. To help format Value/Transfer objects consistently, I use a utility method that employs reflections.
A certain degree of copy and pasting occurs with every development project. The problem is many times overlooked, or missed during code inspection. Simian helps stop some of this monkey business by searching through text files (like Java and C#) and identifying duplications.
With the right incentive, the unattainable can be attained
I recently attended a talk by Dr. Don Batory, on Generative and Component-Based Software Engineering. The goal of generative is to increase the productivity, quality, and reduce time-to-market in software development. [ Who's not trying to do this? Isn't this why Java was invented?]
One developer, 2 modifications
A developer has made 2 modifications, one to a client class, and a second to component classes. The client and component classes are packaged separately, but deployed together. When the developer tries to run the application, a "NoSuchMethodError" exception is thrown.
When reading ASP.NET and Struts: Web Application Architectures, I was expecting to see a comparison of the 2 web techniques, ASP.NET and Struts. Instead, a continuous theme of why .NET is better than J2EE underlies the article.
There are many ways of getting started on a new piece of Java Technology. Developers do searches on Google, check their favorite online publication, go to Amazon for books, view tutorials on java.sun.com, etc… But, one source that is frequently overlooked is the specifications.
Getting C/C++ developers to adapt new coding conventions can be frustrating to a team lead and other Java developers. Coming from a C/C++ and Microsoft background, my style was somewhat different from Sun's guidelines. I found that I was reformatting code all the time to my own convention.
I wager I can walk into any Fortune 500 Company, pull a module of code, and discover that there is no corresponding unit test. Furthermore, the module most likely will not follow the company’s coding standards.