Problem of communication as code changes over time

Two simple and fundamental steps that can be taken to avoid the message being lost over time, comes to mind.

1) Write JavaDoc: For example, for a method, the javadoc should contain the 'intention'; what the method is supposed to do, plus it's limitations. This should make it easier for a new developer to get started with the method and make any changes without messing up the expected outcome.

2) Conform to the fundamentals of Object-orientation. Overload/override instead of changing method signatures. Conform to interfaces (interfaces must be implemented in the first place). These are just a couple of examples and there are a whole lot of them.

Office documents embedding other objects

Create a MS Visio diagram, copy it and paste it on MS Word.

How does this work? Here's a theory.

The Visio diagram that you copied is embedded as an OLE (or whatever that MS calls it) object into the Word document. The picture to be rendered (view) is seperately created as a EMF (Enhanced Meta File, the native format for graphics in Word documents, WMF is also an option) and embedded. The left overs of this process can sometimes be seen as "foo.emf" or "bar.emf" in the C: drive.

The OLE object can be edited later by double-clicking on it.

A forum

We could really use a web forum at CG. There are a lot of information that gets lost in the emails.

Tips and tricks, announcements, iddy-biddy details about stuff.... well there's certainly a lot of things that could be put on a forum.