- BlackBerry Storm vs. the iPhone
- Digg's Kevin Rose: "We have to do better"
- Blogger warns: "Nortel doesn't make it out alive"
- Financial quagmire bringing out the scammers
- Verizon plays with the wrong e-mail addresses
Newsletters | Podcasts | Chats | Opinions | RSS Feeds | This Week In Print | IT Careers | Community | Reports | Downloads | Slideshows | New Data Center
Partner Sites:Application Performance Solutions | App Performance | Networking Solution | SafeGuard Enterprise Solution Center | SOA | Test your Web Filter | Value of WDS
Mark Gibbs shares Web site tips and provides advice on getting the most out of your apps.
Today I want to berate Web applications developers: Ladies and gentlemen, why do you not pay attention to the damn obvious when you let your creations loose on the world?
I’ve written before about Web applications and sites where there’s a serious lack of basic data that provides credibility – for instance, putting a date on a blog posting or a Web site article or giving the version number of the product or service you’re covering. What annoys me about this is simple; you have to give readers benchmarks to position your comments in time and understand where and to what your comments relate to, but the negligent omission of both data points is a recipe for failure.
But leaving out the basic data is nothing to the far more egregious and negligent omission of not handling site exceptions. In this newsletter I was planning to write about a scheduling service called Scheduling.net.
Scheduling.net is a service that claims it can manage scheduling for up to 40 employees over up to seven shifts. The problem I found was that the service seemed to be having major problems with every form I filled in for registration and login (I tried both Firefox on OS X as well as Firefox and IE on Windows).
Over a period of about three hours, for every form I submitted the service returned the peculiar error message “onComplete Expetion Handler 0 undefined.” Now, of course I understand that new services can experience problems, but guys, at least make sure that you know when things are screwed up for over three hours and do something about it. Oh, and make sure you spell your error messages right!
But Scheduling.net is not the only culprit. I look at what seems to be an endless parade of Web applications, and for many there’s an obvious lack of care that just amazes me. This is a basic quality control issue guys! When you get your spelling or grammar wrong it is bad enough, but when your service generates exceptions on something as basic as registering or logging on you have really screwed up big time.
So, here’s my list of things you have to do to be taken seriously:
1. Check your spelling and grammar. It really isn’t hard to find someone who can proofread.
2. Make sure that your site shows dates and/or version numbers when you are discussing a product or service.
Mark Gibbs is a consultant, author, journalist, columnist and blogger.
Partner Content
CA Network & Voice Resource Center
Comprehensive Network & Voice Management Visit CA Network & Voice Management Resource Center and get insights into industry best practices, information that helps you to address your challenges.
CA Network & Voice Management Resource Center
Managing Voice Over IP for Successful Convergence
Voice over IP (VoIP) has much to offer in cost savings but some customers have concerns about VoIP call quality compared to the quality of traditional voice services. This white paper will help you learn how to take the right steps so that voice quality is assured.
Managing VoIP for Successful Convergence
The Changing Face of Network Management
Managing your network is serious business. This paper discusses the benefits of integrating configuration change-awareness into your network fault management solution
Download Whitepaper
Comments (2)
loose vs. loseBy Anonymous on July 16, 2008, 11:37 amThat's hilarious. "1. Check your spelling and grammar. It really isn’t hard to find someone who can proofread." Oops...failed number one.
Reply | Read entire comment
loose vs. loseBy Anonymous on July 16, 2008, 10:03 amGet it right yourself! The misuse of the word loose when you actually mean lose is one of my pet peeves! ID10T! Or, maybe you did it on purpose to piss me off...
Reply | Read entire comment
View all comments