Gaa, I forgot to log in before posting that.

Anyway, feel free to reach out to me if you have any questions about getting going on iOS programming.

"App" is to "Application" as "Droid" is to "Android" and "Sudafed" is to "Pseudoephedrine". All are made-up abbreviations that were invented exclusively for use as trademarks, and in all three cases, there are still unprotected generic terms available to describe the broader markets in which these products compete. There is compelling evidence that Apple was the first to use "App Store" to refer to their "Electronic Marketplace"; they were certainly the first to trademark it. The fact that there are other companies selling similar offerings does not make these "App Stores", just as the fact that someone's pizza stand is small and crude does not make it a "Pizza Hut".

There's one part of this "the 'Close Door' button is disconnected" legend that really bothers me: the purported behavior is so trivially easy to test, but we keep falling back on "Otis Elevator engineers confirmed the fact", even though this is precisely the type of appeal to authority that we are all so quick to condemn when we observe it elsewhere. Several commenters have pointed out that they don't see this behavior in the elevators they encounter - so isn't it about time that we all did some rigorous scientific analysis?

Here, I'll start.

My own experience suggests that the close button often works, so that's the hypothesis I'm going to test. The elevator in my building is a Kone (unfortunately, I have no other information about it - no serial number was listed, and the State of Georgia doesn't seem to post elevator inspection details online).

After the doors first opened and I walked in, I observed a roughly 5 second delay on my stopwatch before the doors attempted to close. The same delay-before-closing was present when I called an elevator but did not step on, and when I took the elevator to a different floor, whether or not I stepped off. The delay before closing was reduced to three seconds for subsequent closing attempts if I interrupted the first closing of the doors with my arm. These measurements served as my baseline for subsequent testing.

I began a fresh test by stepping out of the elevator, letting the door close, and then calling it again. Upon entering the elevator, I immediately pressing the "Door Close" button without first selecting a floor, and observed the door closing immediately after. The same behavior occurred when I selected a floor before pressing "door close", but no change from the baseline was observed when selecting a floor without pressing "door close".

Conclusion: For this particular elevator model, the "door close" button does indeed cause the doors to close sooner.

I don't have a way of quickly determining whether there are, in fact, elevators out there that have intentionally disabled close buttons, but I've got a working theory about where this legend is coming from.

First, every time I've heard the claim that the "Door Close" button doesn't work, it has come from an Otis Elevator representative. It's quite possible that this is a claim that is only true for Otis elevators, but is only reported because there's very little news in putting on a ThyssenKrupp representative saying, "Our 'Door Close' buttons actually work!"

Second, I have been in elevators where selecting a floor would automatically trigger a door close event. It's plain to see that with this design, a door close button is redundant - but it's also easy to imagine a customer refusing to buy an elevator without a "Door Close" button. Adding a nonfunctional button allows the sales team to get that extra checkmark on the feature list, and also makes for a great story about "dumb management decisions" for the engineers to pass around.

I'd encourage you all to experiment with this on your own to see if this also applies for other manufactures. If you e-mail me your observations (peter@stormlash.net), I'll tabulate the data and provide it to anyone who is interested. I recommend the following test rubric:
1) How long does the door take to close when no buttons are pressed?
2) Does the time for the door to close decrease when a previous close attempt has been interrupted?
3) Does "door close" cause this time to decrease when no floor is selected?
4) Does selecting a floor cause this time to decrease?
5) Does pressing "door close" with a floor selected change anything?

Within computing, "kilobyte" has always been an ambiguous term - not only was the meaning of "kilo" ambiguous, but "byte" could refer to anywhere between six and nine bits. This wasn't cause for concern as long as systems were internally consistent, so engineers continued to use the term due to the utility it offered. This consistency is no longer possible since computers are now key components in communication systems which have always interpreted "kilo" as a SI unit.

There's a strong parallel here to the "nautical mile", which was developed because of its tremendous utility in navigation, but which is confusing to those who don't realize that "mile" means something different on a boat. If you transfer your GPS unit from your car to your boat, which type of "mile" should the device use? If you copy a 10 GB file over a 8 Mb/s data link, how long is the transfer going to take?

Computer specialists can be expected to understand the special meaning of "kilo" in certain contexts, but what of those who work outside the field of computer engineering? The modern computing experience is built on tiers of abstractions that allow the "experience" of using a computer to differ greatly from how the computer is actually designed (e.g, file sizes are already given as "quantity of information stored" instead of "disk capacity consumed"), so it's reasonable to use the word "kilo" the way 95% of the population already understands it.