Optimization Idiots

I am trying to get a programming task done using a version of BASIC that produces super-fast code but has a crummy debugger. Execution speed is a big deal for what I’m doing, and I already know how to use this compiler, so I don’t really want to switch. And I don’t particularly like Visual Basic — the obvious alternative — because it’s relatively complex and probably doesn’t produce code that runs as fast.

However, VB has an excellent debugger, and right now I am dead in the water because I can’t figure out how to get a particular bit of code to run. I assume that there is a subtle syntax error or variable mismatch, but my debugger doesn’t provide enough info to diagnose such problems without a lot of trial and error. I don’t think I would have had such a difficult time if I were using VB.

So the tradeoff is between the time I spend debugging and the time I save by using the fast-executing code generated by this hot-shit compiler. Maybe there would be no problem if I were a better programmer, but I’m not, and I’m not sure that I wouldn’t have been better off overall if I had used VB from the start.

I’m also not sure who is the idiot here. Probably it’s me. The compiler designer is merely doing what he does best, he represented the product accurately, and I chose to buy it, so I can’t blame him. But maybe I shouldn’t have been so attracted by the siren song of fast code at the expense of easy debugging. (And maybe I should have realized that a specialized product designed by an individual is likely to have flaws reflecting the designer’s strengths and weaknesses. For example, a brilliant designer of compilers might see less need for a first-class debugger than would a marginal programmer like me.)

Compilers are like vehicles and other technology in that speed is not necessarily the most important feature from a user’s perspective. Speed needs to be balanced against ease of use and other characteristics, and each user will have his own preferred set of tradeoffs.

Creepily-Out-of-Context Lawn Ornaments Dept.

eek!

Why Do We Hate Voicemail “Customer Service” Systems?

Automated phone systems that provide assistance to customers should at most play quiet, light music or sound a mild tone every ten seconds or so, when they put you on hold. That way you can continue comfortably to do what you were doing, and put the phone on speaker or hold it on your shoulder, until someone picks up the other end of the line. The too-frequent alternative subjects the caller to repeated recorded messages that are useless beyond the initial iteration and needlessly interrupt thereafter. It’s even worse when they vary the recordings, especially to advertise something. Then not only are you forced to wait, you are periodically distracted and must process messages for products and services in which you are not, at the moment, even slightly interested. Who enjoys such an experience? It’s like being transported to the hospital while being subjected to a sales pitch for the ambulance attendant’s auto-repair business.

But the most annoying business voicemail practice is the one where the chirpy recorded voice suggests that if I am really in a hurry I should consult the company’s website. At this point I am ready to yell something rude, both because this kind of announcement is a plainly hostile attempt to make me go away — Our time is more valuable than yours! — and because it ignores the possibility that I am calling precisely because I couldn’t find what I needed on the Web site, which is usually what happened. So they are doubly incompetent. They should be soliciting (and using) my feedback. Instead I get the feeling that I am calling one of those old-fashioned businesses where the phone rings for ten minutes straight while the guy at the counter gabs with the mailman.

The people who design these voicemail systems should consider the possibility that abusing captive callers may antagonize some of them into doing business elsewhere. It certainly has had that effect on me. And the way for a business to deal with this situation is not via the default, Dilbertesque response of making voicemail so burdensome that using the company’s Web site becomes the lesser evil. It is to improve the Web site to the point where customers will want to use it, will enjoy using it. Some companies have caught on, but many continue to act as if they think they’re doing customers a favor by answering the phone. I have a low threshold for avoiding such companies now, and I’ll bet that a lot of other consumers do too.

[I wrote the first draft of this post while on hold.]

No Way

nope

December 7, 1941

Remember Pearl Harbor.