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.

Showing posts with label work. Show all posts
Showing posts with label work. Show all posts

Friday, June 1, 2018

Simple Pleasures Are the Best

Years ago, when my dad was in his seventies, I tried to teach him how to use a computer.  He was overwhelmed by what was for him a serious challenge.  This was long-enough ago that there were still dedicated "word processors," units which looked like a computer keyboard and monitor, but which had only one function — to create documents.  Learning how to use them was far easier than learning to use a computer and all it's distracting features, even in those days when they operated in a relatively limited field of effort.

My father tried, but a word processor was not for him.

I realized that the only technology my father might appreciate, even master, would be the closest technology to the manual typewriter he'd been using his entire adult life, a machine which would mimic his old Royal's features.  I was happy to show him how to work an electric typewriter, and he took to it like a fish to water.

I believe that one should consider before racing to adopt the latest technology, particularly if you are efficient using the technology you're used to using.  You should account for the expense, time to adjust, retrain, and even the loss of some aspect of your current process that you might come to wish you had retained, for whatever reason.

I posted about whether or not to agree to software updates years ago.

Be at ease with your own expert notion of what's comfortable for you.

Always use the simplest effective technology.

Thursday, January 19, 2017

The Best Prescription

It may be better for your own mental health to ascribe human qualities to your computer’s performance.  For example, saying, “My computer’s in a funk today, not getting much done,” suggests that you should just be patient, perhaps try tomorrow when the machine’s feeling better.  While on the other hand, treating your computer’s performance as a technical issue—which of course it is—may have you spend the rest of your day trying to solve a problem which might just go away on its own after the computer has had a good night’s sleep—technically, a reboot.

Friday, May 8, 2009

Blogging Hiatus

Please read today's post on my Meta blog, which explains my recent absence from these pages.

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.