Mike Lynn posted an updated version of his previously posted programming rules. It's a good list. Read it over. Obey.

Hear hear... these are good stuff, as expected (even if the pedant in me is calling out for a spell check ;)...

Abaddon's Programming Rules v2.1

] Editing documents in groups can be a challenge.
] Versioning systems like subversion or cvs help your group
] to keep a consistent copy of your document, but don't
] provide realtime collaboration. Wouldn't it be great to
] edit the same document, live, in realtime, together with
] everyone in your group?

[ I've been using this for a while, just because it's a good text editor, with syntax coloring and such. Hanven't yet had occasion to use it collaboratively, but it seems a really well put together bit of software otherwise. -k]

SubEthaEdit - Collaborative Editing Software for OSX

] TeraScale SneakerNet

hah!

this guy has some interesting points on disk storage.

i think we're getting to a point where user interaction with the disk will be minimal anyway, so i'm not sure access time will be so critical in the future, which underscores Gray's point. When, instead of going to your "Documents/Work/Reports/09/03/" folder and opening a file, you just tell your knowledge management agent that you want your september reports, the underlying data access model becomes less relevant. If it takes a bit longer for the agent to find it and put it RAM, so what. Just means the agent has to be smart about how *it* stores an manages data (probly with a large dbase), which is it's job anyway.

A Conversation with Jim Gray