I’ve been a computer aficionado since the mid-seventies. I took classes in computer and programming in high school, although I never followed it as a career path. My first computer was an Atari 800. I spent hours programming and playing games on it. My next computer was an IBM compatible x386. Bye-bye programming, hello computer configuration.
I/O conflicts with every configuration change. Want a modem? Do you have an open I/O channel? No? Can the sound card or graphics card be reconfigured to a different I/O channel? Yes.
The graphics were slow. Well, it seemed fast at the time. 15 seconds to display a moderate sized .gif, bmp, or .tif file. Firing up a word processing program or a game for entertainment went seamlessly for the most part. Occasionally you would find a program that would cause the system to lock up and require a reboot. Sometimes it was a setting inside one of the files that needed to be modified.
From Windows 3.1 until Windows 2000, the joke from the Mac users to the Windows users was, IBM users worked for the OS, while the Mac OS worked for them. Since Windows 2000, rooting around the operating system for what was creating a headache became more of a headache due primarily to lack of practice.
I’ve had many cars. When I hear someone say they don’t build cars like they used to, I usually sigh with relief. I don’t have to tinker under the hood every weekend any more. Oil changes have gone from 3000 to 6000 mile intervals. Tune-ups were done every 15,000 miles with tweaks under the distributor cap at about half that to reset the points. Vehicles today recommend either 50k or 100k miles.
I took a 65 Mustang for a spin around the block back in the early 90’s. I was considering it for a trade on a motorcycle I was looking to sell. The individual wanted the bike and several thousand cash in trade for the car. He wasn’t looking to buy a bike – he was looking to sell a car. One ride around the block and memories started flooding in about the weekends spent underneath the hood. I passed.
My parents are snowbirds. They own a home up north for the summer months, and a home down south for the winter. After some issues with the sump pump, a back-up system was applied that ran on the city water system. When the power went out and the back-up system failed, two monitoring systems were put in place. One of the monitoring systems is a computer that connects to a camera pointed at the sump hole allowing remote access to view the camera.
The drivers for the camera periodically fail. A scheduled event was added to reboot the computer every night at midnight, which would restart the drivers and remote access program. Periodically, the reboot process will not complete, and a trip over to manually restart the computer is in order.
Self-driving automobiles. Are we ready for them? Home Depot, Target and other systems have been compromised on their financial fronts. Recently a story regarding automobile computerized systems being capable of being compromised by hackers ran across my screen. My GPS system more often than not requires 30 seconds to access the address menu. Occasionally the USB system locks up when instantiating the audio file I was listening to.
Don’t get me wrong. I enjoy having a pot of coffee ready to pour a cup when I get out of bed in the morning. I enjoy having an electronic drafting board that makes modifying geometric assemblies and updating drawings within days what used to take months to do manually. When my coffee maker fails, or a change requires a couple of extra days because it required rethinking an assembly approach, or redeveloping some sections – it is just the inconvenience of replacing the coffee maker, or modifying the file structure.
I don’t think I’m ready to put my car on autopilot just yet. After driving for nearly eight hours in one day, I’m leery about simply engaging the cruise control.
Impetus article: CES Preview: Self-Driving Cars, Apple CarPlay and Android Auto Integration to Debut