WorldWide Drilling Resource

The Good, the Bad, and the Ugly Computer by Britt Storkson Owner, P2FlowLLC In previous articles I’ve maintained it’s often better to have no computer than to have an unreliable computer or one which costs more in time and effort than you would have without it. Computers are sup- posed to do some of the work for us and free us to do other, more sophisticated tasks . . . not cost us time and money trying to deal with a computer which is flawed in one or more areas, or unsuited for the task at hand. How can you tell if a computer is flawed or unsuitable, and what constitutes a “dealbreaker” when it comes to purchasing a computer or computer software? Number one on my list are computer commands or other conditions which make it possible to “lock up” or otherwise compromise the computer and require a reboot. I encountered a computer command in the software I was using that, in the instruction manual no less, cautioned the user never to invoke a certain com- mand while the computer was doing a specific task. Look, this isn’t the 1980s anymore. When computers first came out, “locking up” was a problem and part of the growing pains most new technologies go through, and we could accept it then, but not now. Computers have dramatically improved over the years, and the computer manufacturers have figured out how to solve those problems. So we should not have to deal with them anymore. Why anybody buys computers or software that “locks up” from any condition aside from extraordinary events such as a lightning strike or physical damage, is beyond me. Nothing encountered during normal use or operation should cause a computer to lock up. Factoring in human behavior patterns, the problem with telling an operator not to do something will often motivate them to do it just to see what happens. Like the Far Side cartoons some years ago where one of the characters says, “I wonder what this button does” . . . We all know the scenario. Someone ill-advisedly presses the button just to see what will happen. It’s not right, but it is human nature. The computer and software have to be better than that. When writing software, you don’t allow the operator to “mess it up”. You just don’t let it happen. Another problem is what I call the “detached developer” syndrome. Several years ago I was asked by a client to “fix” his computer control system. The computer control system worked, but it did not work well and was not reliable. He asked me to contact the manufacturer and see if I could come up with a fix for his existing system. After several hours of trying to find some- one who knew about the system and could help me fix it, I gave up. Then I realized this was not an accident or oversight by the manufacturer. Most likely, they know their product was flawed. Why would someone who produced a flawed product want to be identified with the product? Serving the Drilling Industry www.starironworks.com 257 Caroline Street Punxsutawney, PA 15767 800-927-0560 • 814-427-2555 Fax: 814-427-5164 Need something special? Talk to us - we’ll make it happen faster than you think. Storkson cont’d on page 20. 8 MAY 2017 WorldWide Drilling Resource ®