Apropos of "effectiveness"...

To say I am not a slave to checklists and procedures when it comes to getting work done is not to say that I do not use checklists and procedures. I do. However, I particularly do not like being in a situation where I am powerless to change said checklists and procedures because someone else "owns" them.

But I have already digressed. That is a rant for another day.

As for the stuff I do "own," I've noted, over the years, that a sure way to tell that your procedures, etc. require revision is when you find yourself consistently either checking items off by rote or ignoring them altogether.

And I suspect, when I see this occurring elsewhere—such as in documents I'm working on—the same need for revision is true as well, albeit the onus for suggesting this to be the case lies somewhere "above my pay grade."

That said, I need to get back to work.

Cheers...

The sounds I like to hear least...

It occurs to me that folks who put together various visual entertainment packages ought to be able to come up with sounds, e.g. telephone notifications tones, doorbells, that are significantly different from those commonly encountered out here in Real Life.

Granted, the telephone notification issue is easily addressed by changing the default tone on one's own phone. Changing the doorbell tone, however, is not so easy, with the result of having both dogs tear toward the front door, barking for all they are worth, whenever a ding-dong identical to that of our own doorbell is heard from the television. Training the dogs to not bark when they hear the doorbell would not entirely alleviate the problem, since (a) a human within earshot of The Tube (and not following what's going on) might be induced to go to the door for no good reason and (b) I happen to like it when the dogs yap like that.

Don't mind me. I'm still coming off of turning around three assignments since this morning. :^)

Cheers...

What a difference some documentation makes...

There is a feature in org, under emacs, that allows one to "capture" the properties of items in the form of an ASCII table. This comes in particularly handy when it comes to invoicing work, except that the documentation for said feature doesn't go much past providing the keychords to press to activate the capturing process, while what is captured, exactly, is not really what I need.

So I went off and tracked down a piece of code called org-collector.el that has at least a modicum of "this is how to use it" documentation, and lo!... suddenly, I've captured data that's much closer to what I need.

I call that progress, especially as the end of the month approacheth!