Month: October 2007

What Is the VDOT Thinking?!?

Sometimes you just have to wonder what VDOT is thinking when they build an intersection. (photo)

October 31st, 2007 – the intersection of Ashburn Village Blvd. and Shell Horn Road. My buddy Chris and I are driving, and a van races up next to us in the left turn lane.

I start laughing out loud so hard I almost wet myself while reaching for the camera.

I don’t know what was funnier, the fact that she was totally oblivious to her surroundings until the very last minute and we had to kindly let her over the solid white line into our lane or the idiots in VDOT who put a stop sign in the middle of a left-hand turn lane.

I swear, this picture is not doctored!

Stop Sign in Intersection

Abnormal Urinal Heights

Who on Earth would need a urinal this high? You’d have to pee out of your chin.

So I’m at O’Faolain’s Irish Pub in Sterling, VA and have to hit the little boys room.

The urinals had to been designed by the Thornton Burgess Toiletry Company.

The Baby Bear urinal was at my ankles. The Moma Bear urinal was where you’d expect it. And the Papa Bear urinal was at my chest. Seriously.

Take a look at where would “it” would have to be and use the standard height of a stall’s handle as a reference point.

I guess Andre the Giant was Irish.

Urinal at Chest Height

Appetizer – 300 Pieces?

So I opened the menu, and the appetizer offered 300 buffalo wings. Three Hundred.

Went to lunch at the new Wings’N’Things off Rt. 606. Guess what they had on the menu?

A Platter of 300 Buffalo Wings. And they were serious.

I can only eat six before I’m full. Oh, and the catch, they all have to be the same sauce.

300 Pieces

That’s a lot of appetizers.

Free Air: 75 cents

Shell offers free air, and it only costs 75 cents per 3 minutes.

Marcus and I are driving on Waxpool Rd. in Ashburn, VA and he notices his car indicates he’s got low tire pressure. We look up and see signs all from the main road that the Shell station has Free Air, so we pull in.

However, turns out the “free air” costs 75 cents every three minutes.

Free Air

Only after you read the super fine print, do you discover that the air is free with a fill up. So we did that. And, $48 later, we got our free air.

Come on Shell, that’s a little deceptive.

Four Complaints of Leopard

OS X 10.5 – sweet, sexy, cool… and four annoying problems that are bound to get fixed soon.

Before we begin, let me say that I like Apple and that I had a very smooth transition to OS X 10.5 Leopard. I had the foresight to upgrade all of my applications, thanks to Version Tracker Pro pointing out what needed upgrading. And, I also had the foresight to update Unsanity’s Application Enhancer before doing the OS X upgrade.

Things couldn’t have been smoother. Shortly after inserting the disc, I was running the upgrade, and my desktop, data, applications, and settings were all preserved perfectly. I’ve never had that kind of experience with Windows.

That said, there are four complaints I have regarding Leopard.

UPDATE: Phil Wherry points out that I overlooked the obvious: Command-Drag the .Mac icon off the toolbar. This works with any icon.

Additionally, there’s some serious value in looking at notMac.

One: Dot-Mac is in-your-face. There’s a new icon in the status bar at the top for .Mac, and you can’t get rid of it with the preference pane unless you sign up for a trial account. Then the preference pane gives you the option.

Come on Apple, that’s so unlike like you.

Here’s why I don’t want .Mac in a nutshell: I have Linux, and it does a better job. I can secure FTP, secure copy, and rsync; it has Apache, Lighttd, and a host of other web servers; it has Sendmail, Postfix, and other mail options; it has DNS, ssh, X-Windows and other services; it has Samba; it has multiple accounts, with permissions; and it has far, far, far more than 10GB of disk space. For those of us with Unix experience and servers of our own, we don’t need .Mac, therefore, we don’t want it on our desktops. It comes across as an overly inflated service that can be mimicked by simple services included in the standard install of Ubuntu. And it’s free.

Sure, some people don’t know how to set it up, and they might want it, but don’t force it on my desktop.

Two: The Finder’s Sidebar has much smaller icons. Plus, for example, the desktop icon doesn’t mimic the desktop wallpaper I’m using. I liked large, findable, easily clickable icons.

Three: It feels like it boots slower. Yes, once I’m in it, it feels very snappy. And, intellectually, I know that a one time short wait is worth far more than perpetual ongoing stalls, though emotionally, to be honest, I haven’t gotten used to it.

Four: Stability. Yes, that’s right, I said stability. As in, it has problems.

My first experience was when someone handed me a disk with .JPG images dumped from their camera; a disc verify hadn’t been done, and unbeknown to me, it has a read problem with one or two files. Guess what – when cover flow hits them, it crashes the Finder.

Now, good on you for restarting the Finder, but I’d much rather it didn’t crash in the first place. At least my machine is still usable.

Which, incidentally, is more than I can say for Time Machine. It has serious glitches.

Using a directly connected firewire drive, I backed up my machine using Time Machine. And, as I worked, I let it run in the background.

Two problems there.

One, Spotlight appears to be finding things on my backup and on my main drive. Oh, that may sound handy, but not when you’re trying to launch an application. And certainly not when you right click a file and see two copies of things with the Open With… menu.

Two, Time Machine can sometimes take a good moment to backup the system. Especially if you’re using Virtual Machine technologies and your image file changes; that thing is huge. Time Machine dutifully starts to back that up, so I get up to take a break while it does its thing in the background. That causes the machine to fall into sleep mode, and that’s where the real problems begin.

When you wake the machine back up, Time Machine looks like it’s still backup up, but you’ve got just a spinner doing it’s thing. Worse yet, if you go to start any applications, they appear to start, bouncing the icon in the dock, but then nothing happens.

Almost.

According to both top and the Activity Monitor, a process is started, although the desktop doesn’t show any applications. You can see them with Command-Tab, but you can never get the application to come to the foreground. You can’t quit. You can’t force-quit. You can’t get rid of them from the command line using kill, either. Any open applications you have do continue to run, though.

That’s when you discover that your log has crazy reports about messages being sent to selector 0, and then you find out that Apple / Restart… doesn’t work either. Killing tasks with Command-Option-Esc simply reports “Application Not Responding.”

The solution, known to many Unix folks, is to ssh into your machine from another system, and issue the sudo shutdown -r +0 command. That does work. It also gives the illusion everything was just fine on shutdown, so Apple doesn’t get an error report.

However, don’t use Time Machine, and all is well with the world.

Concluding Thoughts
Does any of this worry me?

No.

I’m certain that other users are experiencing the same thing and deducing what causes the behavior, and that everyone is filling out the report-this-problem-to-Apple dialogs that appear.

Most certainly, Apple with issue a patch or two, and by 10.5.1 or 10.5.2, all will be well, and applications will come out with minor updates to fix problems. All will be well soon enough, and each of these problems will get addressed.

While minor bumps are expected with any major new release, this is certainly a much better experience than what happened with us and Vista.

I’m sticking with OS X 10.5 to ride it out, but to my Mac friends and followers without solid Unix experience, I’d say don’t let go of 10.4 just yet. One more pass from Apple’s magic wand is still needed.

ASIDE: Third Party App Problems Encountered So Far
SnapZ Pro is using CGSCreateCString, CGSCreateBoolean, CGSReleaseObj, and CPSPostKillRequest; these are obsolete and degrades system performance.
Parallels is using a forked process, when it should be using exec().
Firefox is reporting memory deallocation issues.
Version Tracker Pro crashes when it quits.

UPDATE 27-NOV-2007: Well, those smaller icons have grown on me. I’m liking them now, and before where they just sat there, I’m using them more often. Booting still seems a bit slower, but realistically, I don’t now, and never did, really have to reboot the Mac.

Furthermore, as I write this, 10.5.1 has come out, as well as many package updates. Version Tracker PRO works fine, Firefox has had an update, as have a number of utilities. I’d have to sat the Mac is quite usable and stable.

My recommendation is not to do an Update, but either an Archive and Install, or a migration from another machine/backup. This seems to clear things up quite well.

A lot of people seem to be treating this as a bash the OS post. It’s not. It required some serious digging to find stuff that was a little off. Unlike Vista, which instantly tried my patience and provoked my anger for many months.

Reasonable Trial Durations: 30/30/30

I’ve come up with a way for trial software to be fair and recover lost sales opportunities. The secret: 30/30/30.

30/30/30While doing Java development, I was looking for a new IDE for Windows. Naturally, my hunt ended with IntelliJ, with Eclipse and NetBeans close on its heels.

What started the whole chain of thought for me, though, was IntelliJ’s trial period. Frankly, I really respect a company that has enough faith in their products that they let you use them, unencumbered, for a month in order to make an informed purchasing decision.

Oddly enough, though, it wasn’t enough. Allow me to explain.

The purpose behind a trial period is to allow end users to “log enough flight time” with the product that they know whether or not it meets their needs.

And here’s the problem. I have an existing code base of inter-related projects that I need to import into the IDE. And, since this is for work, my schedule is fairly swamped. I can only come up for air to do an evaluation once every week or two just for an hour or so.

What inevitably happens is this: I install the software, validate it installs, then a week or so later, I try to import; it fails, so I table the project until I have more time. A week or two goes by, and I try again, getting closer. Then, when I come up for air and try to get a bit further, the evaluation period is over. I’ve realistically had about less than three hours using the software, and none of it in the IDE writing code.

This happened to me last year as well.

And, what’s the natural conclusion at this point? I don’t know if it will meet my needs or not. Thus, a purchase doesn’t happen.

From marketing’s perspective, they think that the following scenario is the norm: a user downloads the project, tries creating a project, slings a bit of code, gets married to the IDE, and is willing to pay to keep the experience. In fact, I’ve done just this, and I really love IntelliJ.

But, no matter how much love I have for the product, if I can’t move our corporate applications into it from an existing source base, I can’t justify the site-wide purchase. End of story.

Oh sure, I could talk with the kind folks at JetBrains and ask for an extension, and I’m sure they’d give me one.

But that isn’t the point.

Being a software provider myself, I see this as a generic problem. What if I want to produce trial software that’s fair. I can’t have my customers not being able to make a well informed decision for running out of time.

Here’s my solution… 30 days, 30 invocations, 30 hours – Whichever Comes Last

Here’s how it works:

  • You’re guaranteed at least a month of physical time.
  • You’re guaranteed at least 30 invocations.
  • You’re guaranteed at least 30 hours.
  • When all three of the above goals are hit, stop the trial.

Implementing this isn’t be hard at all. It’s also quite fair and balanced.

If you are doing real work, making use of the application for 30 days, then you’re going to quickly chew through the 30 invocations and 30 hours.

If you have just haven’t even tried the software enough, you get 30 attempts.

Finally, the 30 hour rule recognizes if you haven’t had time to actually experience the software.

I’d like to see vendors start taking this approach. It’s a good one, too. It would certainly result in more sales.

Sticky Fingers: Logitech Mouse

Ok, not making this up. It’s been so long since I used my home Windows system that the plastic on my mouse is decomposing. Literally. Not the rubber. The plastic housing. The hard plastic.

This will give you an idea of how long it’s been since I’ve used Windows at home.

I had to hook up an LCD monitor to the Windows box, boot the system, and install a pile of updates [1 WGA; 34 express; 2 custom]. However, something else gave me a true sense of the time that had passed: when I moved the mouse, I felt something oily and sticky on my thumb. The plastic mouse had degraded.

Upon closer inspection of my Logitech iFeel MouseMan (M/N: M-UN53b; P/N: 830445-0000), the thumb button had ooze dripping on it.

Where did it come from? The answer was obvious. There was a thumb print above the button, where the hand naturally rests.

Apparently the natural oil in my hand left a finger print on the mouse. Undisturbed for so long, the plastic broke down and started becoming liquid mush in that one spot.

I’ve never heard of a mouse breaking down like that, but I’m holding the evidence in the palm of my hand.

Now, the larger question: do I buy a new mouse? Nah, Windows isn’t worth the pocket change or that level of effort to me anymore.