Things that are apparently hard
Aug. 20th, 2007 12:08 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
- Keeping an accurate "new voicemail" flag on a mobile phone. (See Note 1)
- Sending a text message from a phone. (See Note 2)
- Monitoring the temperature at a data center and keeping the A/C running. (See Note 3)
- Receive and file paperwork, first entering it on a computer database. (See Note 4)
- Render a web page. (See Note 5)
Note #2: As long as I've been using SMS, it has failed to send about half the time. The signal bar will show full strength! yay! Then, when an SMS is sent, the phone will tell me that the message in fact cannot be sent. A few minutes later, caught in a lie, the phone admits to having no signal at all and starts trying to find one.
Note #3: Thermometers are cheap. So are loud bells. Summer happens every year! So why is it always the customer who discovers it's 80 degrees Fahrenheit inside? Isn't this job #3 after "not on fire" and "power on"?
Note #4: You're an insurance company. What is it you do there, exactly?
Note #5: When the page causes a browser to look up DNS for five or six ad services, and won't render the page until this is done, DNS then blocks and the viewer either never sees the page at all or gives up in disgust after a minute or two. I can't see how this benefits the advertiser or the website owner or anyone, really. Why even use hostnames? Why a duck? Why not a chicken?