Tech Simple

I have been in so-called high-tech for more than 25 years, and I’ve worked with labor and time-saving software and hardware—and I’ve wasted a lot of time, too, often laboring long days and weeks with little to show for it outside of that ephemeral favorite, the wisdom of experience.

This blog is my celebration of the adage: Keep it simple, stupid. I intend to apply this discipline to technical challenges low and high, in a way that's both clear and entertaining.

We all have to find ways not only to understand the technology that surrounds us, but to bend it to our will, to be masters of our time and talent, and protect our most valuable asset: our time.

Welcome to you, I hope you find the information I post here useful.

Tuesday, February 17, 2009

When to Upgrade Software, Hardware—or Anything Else

It's reasonable to have to pay for upgrades, but you should only upgrade if you require the functionality the upgrade provides.

The only reason to upgrade when you don’t require upgraded functionality is because the current version will no longer be supported. If you upgrade in this case, you aren’t actually upgrading, you’re meeting a support requirement.

Upgrades which increase performance, or correct errors or design flaws, should be called fixes.

It's not reasonable to have to pay for fixes.
Posted by at
Labels: , , ,

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)