Remember to say "Thankyou!"...
Just a reminder boys and girls: say thankyou every now and again to the people who write the software you use. They will appreciate it.
Just before going to bed last night, I received a nice note from somebody at Wipro who had found a document I wrote useful (he also pointed that a link was broken and included a fix). When I woke up this morning, somebody else had sent a similar note about a different document. Much cheerfulness ensued on my end. :-)
...and try to coordinate your work with others
Unfortunately, also in my mailbox this morning was a nice note from the artist formerly known as gman (now performing daily over here). He politely pointed out that one of the documents I was editing was also undergoing extensive revisions by him and had I read his diary I would have seen that he pointed it out (together with a link to the rewrite) two weeks ago. In my defence, I can only say that that would have required me to learn to read and I don't have those lessons scheduled until next year.
As punishment, I get to merge his changes and my changes and the original document into something coherent. I would like to tell you how much fun that has been today, but it would involve lying and I'm not meant to do that.
My post yesterday elicited a couple of pieces of mail and some feedback here, so I only wasted everybody minus four peoples' time.
haruspex: I saw some OpenDoc stuff a few years ago (on a friend's OS/2 box). The mostly seamless blending of pieces that seemed to promise is part of what I am talking about. However I had not seen CyberDog, so I'll admit my statement that nothing exists properly may have been overdone. However, component technologies (be they OpenDoc parts or Bonobo components or ActiveX objects or whatever) are not quite living up to the image in my head. But it's a good match in some cases and very close to what I am thinking about; certainly a component-based architecture would be part of something like this.
Good Idea of the Week (GIOTW?!)
DV made a really good suggestion on the libxml mailing list today. If a couple of dozen people who use libxml2 regularly all contribute one or two code samples of how to use things, we will quickly develop a large repository of answers to the "how do I do that?" questions. This would certainly be a way for a lot of us to pay back Daniel for his superb work on this library. The code samples are already accumulating.