Work:
Came in to work this morning (after a
much-needed day off), and discovered that I was expected to
have three server systems installed, configured, and in
place by 10:00 AM this morning, with various extra bits of
hardware expected to be on-hand (little stuff, you know: a
KVM, an 8-port 10/100 switch...stuff everyone has just lying
around, right?). No sense getting mad about it, although the
requestor can kindly kiss my ass, because he'll get it when
it's done, not when it's convenient for him.
Anti-work:
Found a number of excellent resources today,
including Altavista's self-employed
section. They have a nice collection of links regarding
trade/service-mark law, consulting information, and the
like; a good suppliment to the archives over at Monster, and a surprise,
since I haven't seen many new services from them
lately that would pull me to their portal (Google now being my
first-choice search engine, followed by dmoz, Freshmeat, and various online discussion and news sites (although Technocrat
just won't be the
same anymore).
Weblogs meet cross-referencing:
My girlfriend has convinced me of the merits of
a project she wants to take on, and I'm thinking of ways of
tackling the backend. The basic format of the site will be a
weblog combined with a cross-referenced database of categorized
data. I'm wondering if there is any publically-available
code which already tries to tackle this combination, besides
SourceForge (which is
obviously far beyond what I need to do with this
application); something which smoothly integrates the two
ideas. I'm thinking of every "article" being both a
user-commentable item (ie. /. articles), and
categorizable in a hierarchal structure in multiple places,
allowing for a navigable site index as well as references
from one article to either another article, or a category,
easily. Slash and Scoop would seem to
come close, but not having looked at them under-the-hood, I
don't know how amenable their architectures will be to
extension to that. I'm half tempted to write it all myself
(borrowing from other projects), but there are already too
many weblog backends out there already...