Dolly Madison "Divide By Two" Fail

Can't divide by two? Dolly Madison has your back! Only they can't divide by two, either. This is not the best thing I might choose to put in my system. Mathematically-challenged, high-calorie snacks are way worse than just high-calorie snacks.

Let's count the foibles:
  1. If you eat one, it's 200 cal. So the 410 cals on the pack? Either they're expecting a lot of icing stiction to the package, or they expect me to eat the package. One of those alternatives is wholly understandable. The other is slightly alarming.
  2. One roll has no trans fats. Two rolls have 0.5g trans fats. Eat the right one!
  3. One roll has 6g of fat. Two rolls have 11g of fat. Again, choose wiseley!
  4. et cetera

So, I have a math fail, too. I suggested counting the foibles, and stopped at 4. Clearly, my Dolly Madison snack consumption is taking a toll.

Does Anyone Remember How Powerful DNS Can Be?

I'm not talking about the handful of sysadmin gurus. I mean everyone else from developers to the rest of system and application administrators.
You don't need to name a machine after what it does. You can. But you don't have to. And chances are good that if you own that machine for several years, it will become many more things.


What the fudge is a CNAME?

It's a name that points to another name to get an IP address resolution. Think of the phonebook. You look up "Euripidies Flintstones" to find a phone number. "Euripidies Flintstones" would be considered a DNS A record, or a mapping of a name to an IP address.

Now imagine we had a more sophisticated phonebook that knew Euripidies usually went by the less formal first name "Phil." Looking up "Phil Flintstones" would refer you to "Euripidies Flintstones." In this case, "Phil" is the CNAME.

You have a non-production machine that hosts your dev, qa and uat environments for a web application. The box (we'll call the box "bob" for the sake of argument) is older but perfectly serviceable. And you really don't want to rename it for a number of reasons. And that means you already have a DNS A record for bob.domainname. The box name is unimportant. Name it whatever you want. But if you have to access a major resource on the box, create a CNAME for it.

You could put all your environments on different ports. Heck, you could do what most thoughtless folks do and just address it by IP (oooo, now that's not prone to creating extra work down the road!). Or, you could be one of the 1-percent who take this advice.

bob.domainname's cnames:
devweb.domainname -> points to bob.domainname
qaweb.domainname -> points to bob.domainname
uatweb.domainname -> points to bob.domainname

Web apps are really easy for this. With the magic of IP-less hosting, asking the web server to talk to "devweb" will send you to the right web service.

Take a production example. You have a file server already named "myfiles.domainname." You're just big enough that you plan to add separate database and mail servers. But you'll colocate them on the file server to get started.

myfiles.domainname's cnames:
sql-01.domainname -> points to myfiles.domainname
mail-01.domainname -> points to myfiles.domainname

Why bother? Well, you've already configured numerous clients to talk to myfiles for file shares. When you install your mail server, you're going to have to direct them to something. One day, when you create a dedicated mail server, you have to go touch every client to change from "myfiles" to "mail-01." Or you could just edit the CNAME for mail-01 to point to your new mail server when you finally install it.

The database server can be an even bigger deal. You'll probably write tens (or hundreds) of small and large programs that access the database server. If you leave it as "myfiles," all those applications will need to be changed when you install your dedicted database server. Or, you could use a CNAME and repoint it later with a lot less fuss.

You don't need them for every server and every minor case. But they are an immensely useful tool in your sysadmin arsenal.

CNAMEs, folks. It's the wave of the future, only it was envisioned in the early 80s and ignored by scores of IT professionals.

By the way, here's a useful external link with a simple CNAME explanation: http://rscott.org/dns/cname.html

(One caveat... some Windows services rely on more than a DNS name. They expect to find a WINS name as well. While you can create custom WINS entries, and they're usually successful, Windows file services are notoriously picky about the actual system name... thanks Microsoft!)


On Being Action-Oriented...

Quick reflection on being action-oriented...

I did a small, boneheaded thing today. Details aren't important. I just did half of something and forgot about the other half. And it's a task that should be handed by a functional person because it's related to customer config data.

(If you're scrunching your nose and furrowing your brow about that, there's usually a dotted line in larger IT organizations that separate "applications" and "data." I can help you install Excel. I can teach you how to use it. I might even show you a formula or two. But I really should leave it up to you to maintain your own spreadsheet, even if you ask me nicely to tinker with it)

All in all, it's a pretty innocent mistake, and everyone is OK with it. In fact, it was barely more than a fleeting thought in a long conversation.

But it made me reflect on times I've been called on the carpet vs. times I haven't. And the times I've been called to task are almost universally times where I haven't done something (for any number of good or bad reasons).

In other words, any time I've made an error of action, it's generally been forgivable. Good thing to remember.


Tonka Mighty Rescue Vehicle

Found at an antique shop between Peachtree City and Sharpsburg. It's a 1975 or 1976, and it has all three figures and the gurney! Condition is fair, but at least it's complete. If you aren't familiar, the Mighty series are pretty big. This is about a foot and a half long.

Godspeed, Chocolate Cowboy

Seen on I-285 during my commute. I think the picture says it all...


What Started Your Geekery?

From whence came your geekish tendencies? Were they made, or did they just happen? Did they magically manifest in your mind in the womb?

At dinner the other night, we discussed a particularly unpleasant way to be introduced to technology:
A) Go away on vacation for two weeks
B) Return from vacation to find a PC on your desk
C) Find large manual to be read on your own time
(the year was 1992, and this was not uncommon)

My mother looks over at me and my father and says "The two of you taught yourselves. How did you get started?"

My father and I look at each other, the table, back at each other, and shrug. My father says "well, I was just there. I don't really know." Now, he's being a bit modest. He was one of the first people at Delta to have a PC, but only because he bought his own (one PCjr for his office and one for the house in 1984).

I started using the PCjr for word processing, Flight Simulator, Gato and Rogue. I wrote tons of papers in junior high, high school and college, printed in dot matrix goodness.

But it wasn't my fist computer. I had a VIC-20 with cartridges for Gorf, Turtle Programming and a 16KB expander. I also had a cassette tape storage system and a printer, both of which were woefully underutilized.

Prior to the VIC-20, I'd used a TI-99 in 6th grade for some sort of pirate text-based adventure game. I haven't a clue why the VIC-20 had appear where the TI-99 did not, given that the TI-99 was way more powerful. It's not even like I wrote many programs. At geek camp (as I think of it now) in 6th grade, most of our computer skills course consisted of us putting characters on the screen just so we could watch that big, fat VIC-20 cursor "eat" them when we held down the backspace key.

Before that, I had an Atari 2600. Preceeding the 2600 was Asteroids, or as I think of it, the single greatest video game ever. And my freind's Oddesy console... we'd swap his Oddesy for my 2600 for a few days at a time. But is that where this started? I'm not sure that it did.

I think it happened before that. I remember being fascinated by my father's baby blue Smith Corona electric typewriter. It didn't hurt that the kid next door had all manner of cast-off devices from his father's machine shop. Heck, I'm fairly certain a broken Sinclair would have been sufficiently entertaining to me.

I vividly recall the brightly-lit panels in Space: 1999's control center and Eagle. Star Trek was a given, but it was more on par with Emergency! as an adventure show. And I picture in my mind as clearly as if it were yesterday when I proudly announced to my second grade class the fantastic new show premiering that night: Battlestar Galactica.

I could go on for pages (Micronauts, Star Wars, comic books, whatever). Was I made into, or did I just happen to become, a geek?


Windows 7 Beta Oddities

So far, the beta ride with Windows 7 has been clean. Even Authentec stepped up to offer a beta fingerprint driver that was released in the last few days. And Windows 7 even prompts me at that point to say "hey, Hondo, you really should let me fix this device problem for you."

Here are the two oddities significant enough to warrant a mention:
  1. I can't close an Outlook 2003 note. I can make 'em. I can edit 'em. But I can't close 'em without closing Outlook.
  2. Connecting to work via vpn locks out my user account. It's a domain-joined laptop connecting to a Nortel Contivity via pptp and a local Contivity account (the Contivity can use domain accounts via RADIUS, but I don't use that). I don't have to access any domain resources. My account is just instantly locked (which is to say that 7 is accessing a domain resource... I'm just not triggering an event that would do it).


When being #2 is better

Hertz vs. Avis
Coke vs. Pepsi
Pat's vs. Geno's

Those are all competitors where there's a #1 and a #2. Avis coined the phrase "We're #2. We try harder." Coke would have happily invented Pepsi for the rivalry. And the cheesesteak warriors may both claim to be the "King," but the truth is that the rivalry is as much a reason for success. All it takes is one panoramic look from the converging points of South 9th Street and East Passyunk Avenue to see that.

There's a real silver lining to being #2 that we don't automatically appreciate in full. #2 usually means you get back something for what you give up in volume. Real life is rarely a zero sum game.

For example, if you happened to be a wholesaler, and you went from being the #1 supplier to #2 for a high volume retailer, but your actual profit dollars increased, would you really complain? You might if you lost the #1 slot because your service was bad or your people were knuckleheads. That's not the case here. And it's a very odd sort of good news.

Let's see... You could make more money and work less for it. Winner!

(By the way, I've always been a Jim's guy in Philly, I prefer RC Cola and Alamo is pretty much my consistent go-to rental... but I'll save that for a "When being #3 means you're a boutique supplier")