Your local repair garage finds out about bad code through great pains.
As I opened the door with a jingle, I noticed immediately that it was a very busy office for an auto-repair garage. I counted about 20 people, many more accountants than you would expect for some guy’s oil change or engine rebuild. There were at least as many computers as people, about one per desk–another tip-off that this wasn’t your average shade-tree mechanic. Not that there were any trees. I was out in the North Dakota prairie country when my car suffered some kind of fuel-injection breakdown and I lurched into this garage.
As I sat in a worn, grease-stained chair waiting for the mechanical diagnostics, they hooked the car up to a large and very odd-looking rack of computer monitors–it looked like a home-brew system. I wondered if there’s some kind of mad IT department at work, renegades from a failed dot-com. Nah, code jockeys never become grease monkeys.
Suddenly, a guy with the name Mike on a patch sewn to his coveralls came into the office and made a beeline toward me. He looked so enthusiastic that I was sure he’d found thousands of dollars of work. One hand trailed about two feet of computer printout; I was certain it was the bad news.
“Look at this,” he said, waving the paper around so that it was impossible for me to read it. “Stupid computer part! Your injection system has a burned controller.”
“Oh, great” I said, “another bad computer. As if I don’t have enough problems with computers and software.” Before I had time to savor the irony, Mike looked at me for a moment, twizzled his bushy red mustache, and asked, “Programmer, analyst, or project manager?” Obviously, Mike was one of those mad IT people who knows something about computing. “Worse,” I said, “computer journalist. I review software and gripe about the industry in print.”
“Wish I could do that,” he said. “Then I could tee off on the fools who sold me a worthless accounting system.”
“Tell me more.”
He crinkled his brow. “Sure. ‘Cross the street there’s a café; we can get coffee there that doesn’t have an inch of crankcase oil at the bottom.” He laughed and immediately set out for the door.
A long path to auto repair
It turned out Mike’s the owner of the “garage.” He’s a graduate of Cal Tech, a first-rate engineer who began his salaried life as a corporate hotshot at General Dynamics. But salaried life didn’t agree with him. Or, more to the point, he didn’t agree with either his bosses or the way projects were handled. He left in disgust, burned out and unwilling to ever again use his talents in the employ of idiots.
He went home to North Dakota, started the repair-service to make a living, and did his tinkering in the off hours. His tinkering: fluid hydraulic systems. Tiny, extremely precise fluid hydraulic systems–the kind that can be used to move sophisticated mechanical devices like airplanes, rockets, and space stations. Mike once submitted one of his designs to NASA, and they approved it. “That,” he said, “was the good news, and the bad news.
“They wanted me to build the parts. Fine, I could do that. Thousands of them. Oh. I’d need some help. That’s when this became a real company. You probably didn’t see it but there’s a 30,000-square-foot building behind the garage. In it are 56 employees working three shifts.” Mike swizzles some cream into his coffee.
“It wasn’t long after I got started on the first NASA contract that I realized we needed some big-time accounting software. So I called this software outfit in Fargo and they sent out a couple of people. I told them, ‘I’m doing work for NASA. I need security, 100-percent reliability, and some specialized accounting.’ ‘Sure, sure. We can do that.’ It was brand-name software, and I bought it. They installed it, although that took more than three weeks longer than they said it would.
“It wasn’t long before we started making a list of things that didn’t work. One of my employees showed me how to get into the system without a password. One day the server died; no big deal, except the software quit in the middle of a transaction. It couldn’t rollback, rollover, or whatever. We lost some critical data on a $300,000 NASA contract. You can’t imagine what I had to go through to make NASA believe that the computer software ate it.”
“NASA has its own problems,” I said. “Like crashing the Mars Lander because some programmer didn’t know the difference between miles and meters.”
Lost in space
Mike flashed a wry smile and continued. “NASA requires some special accounting; the software couldn’t do it out of the box–though [the software company] said it would. So I had to have a module written especially for the requirements. That was a nightmare. I found out the guy they sent to get my specifications was a specialist in agricultural software. Really. The first version they produced didn’t run. The second version ran, but had unreliable summaries. The third version ran and was accurate, but it couldn’t handle the confirmation system NASA requires. What could I do? Nobody in this shop knows Java from a cup of coffee.”
“Roughly how much money were you out by the time this came to a head?” I asked.
Mike scrunched his face in thought. “About 200 grand.”
“A lot of money for your size of operation.” I said.
After a moment, Mike nodded.
“Many companies in the software business make their profit from fixes, maintenance, and upgrades,” I told him. “They have little incentive to give you perfect software. What did you do?”
Mike grinned. “Used some NASA muscle. They had a Colonel somebody–a lawyer–call the vendor and the local representative. That got serious conversation going again.”
“I’ll bet. A lot of small firms can find larger organizations to give them some weight in these problems.”
“Basically, we had them start over. I admit, even if it’s commercial software, don’t let them just waltz in and go live with it–like we did. The second time around we agreed to some additional payment, but we demanded a demonstration of operation first. We also sat down and prioritized our expected functionality: Know what has to work and stick to your guns about it.”
I asked Mike if he had expected the software to be flawed. “I’m an engineer,” he answered. “I like perfection. I know you can’t get it. They could do better, though.”
Yes, they can. I informed him that some software companies are changing not only their attitudes but also their pricing structures. Instead of paying up-front for software of unknown quality, you lease it, pay in installments–or quit paying if you aren’t satisfied. I also told him that some software companies are trying to combat problems caused by the complexity of software by using new diagnostic tools. I don’t think Mike was convinced that he can expect all shiny new apples in the barrel.
“You know,” he said, “if I were talking to other small companies, I’d say they should always expect to pay more than the listed or quoted price. Add 25 to 35 percent to your budget figure. If you can’t afford it, do less–or do nothing.”
He added, “Oh, by the way, we can have the part for your car in about two hours; it’ll cost you 50 bucks or so.”
I was floored, not at the price of the computer gizmo, but by Mike. “How do you have time to work in the garage and talk to folks like me?”
He laughed. “I try to make an appearance, from time to time. I like to remind myself what service is about.”