What we can learn from software version numbers

Just the other day, a successful doctor called our office and asked, “What version number is Curve Dental on?”

The dental software consultant on the other end of the line was surprised by the question. Gathering his thoughts, he replied, “Doctor, we don’t have version numbers. We have only one version.”

“So, when do you provide your customers with upgrades?” the doctor asked, it being his turn to be surprised.

“All the time,” the consultant replied. “Whenever we build something new, make something better, or fix something, it immediately becomes available to all of our customers.”

“Oh, I don’t know if that’s such a good idea,” the doctor replied.

The consultant hesitated. “Why is that?”

“With that many new upgrades, I’d continually hassle with installing them,” the doctor explained. “My IT costs alone would be through the roof!”

To this the consultant chuckled. “Let me explain, sir: Because our software is on the cloud, you never hassle with upgrades. Whenever you use the software, the newest features and enhancements are always available. You never install upgrades.”

If software versions could talk

Frankly, these kinds of conversations remind me that there’s much work to be done to undo the grip of those peddling out-of-date software. Strangely enough, after I learned of this conversation, I saw hoopla surrounding the latest release of one of these older systems. If that version could talk, this is what you’d hear:

“It’s been a long wait.” A new version represents months and months of work. The number of months since the last upgrade, in this case, was more than 12. On the cloud, the story is much different. Additions and modifications are added as soon as they become available. As an example, we make changes to the system every week, sometimes daily.

“The list of new stuff is short.” Given the time that’s passed since the last version, the actual list of new features, enhancements, and fixes is surprisingly short. I believe that older dental software is starved for innovation - not for lack of want, but because the code base is brittle and difficult to work with. Perhaps more time is required to maintain the software than ever before, leaving little time for serious R & D.