I would think it makes a big difference what *size* of program you are
considering.  For huge programs, it's important that the notes be good
enough that other programmers can understand them.  This leads to
standardized notations and a relatively rigorous system -- e.g., UML.

For smaller things, though, it would be nice if people can just scratch
a note here or there.  There are two big ways Squeak already supports
this right now:

	1. You can build partial programs very easily.  You don't have to worry
about typechecking, and you don't have to wait for a compilation cycle. 
If it's a graphical fribwitz, you can even use direct manipulation to
put it together.  Even if it's not, the inspectors are very convenient.

	2. Workspaces can combine commentary and code.  When many people
(including myself) work on a tricky project, they build up a workspace
with code snippets and (depending on the programmer) English commentary.

The snapshot model helps an aweful lot with each of these.


Now, it could well be that a better organizational model is begging to
be put together.  It's a wonderful angle to look into!

One last thing to consider: the attitude of the programmer surely makes
a difference.  Someone's who's not used to tinkering around with
prototypes isn't even going to *try* to use what is there.

-Lex