Time Heals All Wounds.. And Then Kills the Patient
<Previous Next>
Sun May 18 11:47:05 2003
Netdiary updated.

I updated my netdiary code, finally, to do what I've been thinking about for a long time. Netdiary is still an ugly little script, but at least now the output is better. Both versions have a main summary page, which contains the most recent entries. They then have a link pointing to events further back, which in turn point forwards and backwards, all the way back to my first entry, on 2 July 2001 (which, by the way, was actually the continuation of a private journal called my explanatory. That journal was in 2 parts. The (very small) first was lost in a computer glitch, after that, I started it again, and the first entry seems to be 21 June 1997. However, I'm now unsure if I actually have it all -- it only goes to 29 September, and although I know that I didn't use it for too long, I think I might've used it for longer than that. Well, find only found that copy that inspired me to write about it just now. Maybe the below will be able to find a different copy in my backup directory: $ foreach i ( *.tar.bz2 ) foreach? tar tjf $i | grep explan foreach? end

Bleh. Creeping featurism wins the day -- I just thought of something else I'd like my netdiary code to do -- warn me when I have 2 entries with similar titles. Of course, on the client side, everything just happens in a plain text editor, so I need to heuristically decide what 'looks like' a title, and many entries don't, because early on I never really intended for entries to have them. Maybe a good rule of thumb is that if an article has a line of text at the start of the article, with a blank line afterwards, that line of text should be considered the title and handled accordingly. I'll need to see if that rule is well-behaved for my entries. Ahh, the joy of heuristics, where 100% accuracy is unlikely and you're really aiming for 'good behavior most of the time', you're attempting to impose order that's not entirely there to begin with, and usually there are many ways to get the job done, with varying results. It's important for programmers to have mastery of both algorithms and heuristics, which is why programming is both a left brain and a right brain activity, an art and a science. Order and Chaos..

Anyhow, I'll put that feature off for another day. Hmm... the explanatory didn't turn up anywhere else. So, either that's the only copy I have, or there's another copy on one of my CD backups.