Evolutionary firmware design

Many years ago, I worked with a firmware engineer. We'll call him 'Bill'. 'Bill' was an interesting character, for he was fond of saying provocative things in order to observe your reaction.

I walked in to Bill's office one day, and he was sitting there with his feet on the desk, leaning back in his chair. Hands clasped behind his head. I'd have thought he was napping except I noticed that he was staring at the ceiling.

"What's up, Bill?", I asked.

Bill replied: "Oh, I'm working on the firmware for the new color printer, and I'm thinking about what to do if someone opens the cover in the middle of a print cycle. It's giving me fits."

He continued: "Sometimes I wish humans were descended from dogs instead of apes." He paused.

"Why's that, Bill?" I asked, taking the bait. By then, I was on full alert.

"Maybe then they wouldn't be messing around, pushing buttons when they shouldn't." Bill said. Clearly, this was the punch line he was waiting to deliver.

"Yeah", came my immediate reply, "but then, you'd be sitting here, pondering what to do when the user urinates on the printer with the power on."