https://buy-zithromax.online buy kamagra usa https://antibiotics.top buy stromectol online https://deutschland-doxycycline.com https://ivermectin-apotheke.com kaufen cialis https://2-pharmaceuticals.com buy antibiotics online Online Pharmacy vermectin apotheke buy stromectol europe buy zithromax online https://kaufen-cialis.com levitra usa https://stromectol-apotheke.com buy doxycycline online https://buy-ivermectin.online https://stromectol-europe.com stromectol apotheke https://buyamoxil24x7.online deutschland doxycycline https://buy-stromectol.online https://doxycycline365.online https://levitra-usa.com buy ivermectin online buy amoxil online https://buykamagrausa.net

Month: March 2006

Scrub, scrub, scrub

We’re evaluating consulting firms in support of a multi-million dollar major systems implementation. We had a second round of interviews with one of the firms, and asked for some examples…

We’re evaluating consulting firms in support of a multi-million dollar major systems implementation. We had a second round of interviews with one of the firms, and asked for some examples of functional and technical specification/scope documents they’ve produced before.

Just received them. They were done in MS Word, and the techies were very careful to Find-Replace all instances of the company name the document was originally done for, as well as the various folks on approvals lists, etc. Nice and generic and secure.

Except, of course (and anyone who’s in Security or who’s done much of this sort of stuff can predict what I’m going to tell you), it was all done with Track Changes on, and they never then went through and did an Accept Changes. So when the document was opened by me, in “Final with Markups” mode, all the changes were there, including all the names that were deleted/changed.

Oops.

Granted, I’ve seen other technical types that should have known better (as well as senior IT managers and CIOs) do exactly the same thing, but, damn, doesn’t make me feel at all warm and fuzzy about trusting my project (and my company’s proprietary info) to them.

A word to the wise …

Crossed wires

The danger, in a hectic and distracting work environment, of IMing with one’s wife while making a phone call to a female member of one’s staff is that there is…

The danger, in a hectic and distracting work environment, of IMing with one’s wife while making a phone call to a female member of one’s staff is that there is a finite possibility of greeting the latter with a term of affection that should be (both from propriety and accuracy) reserved for the former.

Not that it actually happened, but … it was close. 🙂

Mistress of her own domain?

Ran across an article the other day about how someone had purchased a domain for his infant daughter, with the idea that, sooner or later, she’d want it herself, and…

Ran across an article the other day about how someone had purchased a domain for his infant daughter, with the idea that, sooner or later, she’d want it herself, and it would be a nice gift to be able to give her (for an $8/yr pittance in the interim).

Made me think. Could do that with Kitten. She has .com and .org and .info and .name versions of her name available.

On the other hand, we have a family domain that she could use.

On the other hand, that may be akin to saying, “But, honey, why do you need your own car? Mom and I can drop you off wherever you want to go in the mini-van!”

Personal domains? Family domains?

And that assumes that she wouldn’t want something fancifully personal — “PrincessKittenyboo.com” or something. Though, one would think, a professional domain name would have some applicability.

On the other hand, mightn’t she want to merge namespace with someone else when she’s older? Until then, wouldn’t using the family domain make more sense?

Is it about sense?

And who knows what the Net landscape will be in 10-plus years? Will personal domains be passé? Will they be legal? Will she even care? (“Daddy, I’d much rather have a node in podspace! That web stuff is so aughty!”)

Musing.

Lent …

… is a good Anglo-Saxon term, relating to the lengthening of days leading into Spring time, and referring specifically to the 40-day season (plus Sundays) leading up to Easter. For…

… is a good Anglo-Saxon term, relating to the lengthening of days leading into Spring time, and referring specifically to the 40-day season (plus Sundays) leading up to Easter. For most Christians (cultural or otherwise), it’s a period of “giving something up,” usually a sacrifice of something that’s not all that good for you to begin with (e.g., chocolate, snacks), though more thoughtful custom simply has one pursuing ways of shaping up one’s life and relationship to God in some fashion, i.e., taking a positive action (more exercise, regular prayer, whatever).

Ironically, though Ash Wednesday is a day of fasting in traditionalist Christian denominations, we’re going to spend it with friends having a nice dinner (after Katherine’s parent-teacher conference).