tempting, but no.

[jrtom]

http://www.theregister.com/2004/02/03/us_parents_give_birth/

(And no, it's not the same as naming your kid "[your name], II": "the second of this name" is not the same as "a revised version of".)

Comments

[red-frog.livejournal.com]

Kind of sucks for Kid #1 if he's version 2.0 and the later kids are later versions (presumably with bug fixes and additional features), too.

You do that, and I'm reporting you to CPS. :D

[jrtom.livejournal.com]

Well, according to the articles, the overly proud papa's versioning scheme indicated that it would work the same way as the II, III, IV numbering, i.e., I am version N and I name one of my kids version N+1. Not that that helps much.

If I were his wife, I'd threaten to uninstall him (since version 2.0 is now available, what does she need the now-superseded version 1.0 for?).

Upgrade path?

[red-frog.livejournal.com]

Wow. Incest encouraged by a bad naming scheme.

Re: Upgrade path?

[jrtom.livejournal.com]

Well, incest isn't exactly what I was intending to imply (although I acknowledge that my phrasing didn't rule it out).

Presumably Version 2.0, in my uninstalling scenario, is not assumed to be backwards-compatible; rather than providing all of 1.0's features, version 2.0 reflects a radical redesign with a better idea of the customer's requirements.

Re: Upgrade path?

[red-frog.livejournal.com]

Yeah, but if it's not backwards-compatible, then she can't uninstall in case she needs to use some features found only in v1.

So I think that Mr Cusak is safe. :) He may be Office 97, but, well.

Re: Upgrade path?

[jrtom.livejournal.com]

But this assumes that Ms. Cusack can't find the "missing" features she wants in some other application. Of course, there's the learning curve to consider, not to mention the potential costs involved with switching.

Re: Upgrade path?

[gwyd.livejournal.com]

I immediate thought incest and was seriously grossed out. The bit about backwards-compatability really didn't help either.

That poor child.

BTW. If yours is a boy, please, please, please, please do not name him Trevor, Cameron, Jeff with a "J", Shawn (spelled as written), Jason, or Jared. Trust me on this, I teach for a living.

I would also advise against Ashleigh (any spelling), or Britany (any spelling) for girls.

Re: Upgrade path?

[jrtom.livejournal.com]

Megan's very much into the "let's look at the most common names and not use them", so I think we're safe. None of the names that we've been considering are on your list of ones to avoid, I'm pretty sure. (And I'd have to eviscerate myself with a dull spoon if I named one of my children Ashley or Britany.) But thanks for the warning. :)

Re: Upgrade path?

[gwyd.livejournal.com]

Oh, and there are a lot of Jordans (both genders) out there. This might not be obvious if you are looking around for names.

Re: Upgrade path?

[jrtom.livejournal.com]

Do not underestimate the powers of those who are both (a) obsessive-compulsive and (b) possessed of fast connections. We actually downloaded and parsed the US Census name data. :)

Re: Upgrade path?

[red-frog.livejournal.com]

Geek. :D

Re: Upgrade path?

[jrtom.livejournal.com]

Um, yeah. (Although in truth it was just a spreadsheet, so we didn't even have to write any code to do this, until we came up with a scoring system.) I'm sure all my readers are shocked (and awed) by the extent of our geekitude.