When Software Requirements Go Wrong
Not wanting to discourage his initiative, I asked him if he would make the install more professional by getting rid of the randomly launching command prompts. I assumed my intent was clear: customers were installing our software on critical servers, and so the initial user experience should do nothing to betray their confidence. “Sure,” he said. The next day he dropped off a disc containing his new installer. Upon clicking on the install icon, a big black window appeared on my screen, like a shade pulled over my monitor. Upon looking closer, the black window did not quite cover the entire screen, and so I could occasionally see the edges of random command prompts launching behind it.
His solution was brilliantly devious and profoundly awful. He had met the requirement of getting rid of the command prompts by launching a single window with a black background that obscured (mostly) his messy install. But he had clearly subverted the unstated requirement: to make a professional install.
After a few more tries, his agent eventually made its way to our customers through professional service engagements. Not long after we replaced this stop-gap agent with a polished and professional one developed by my team. I took no chances on the install for this agent though, and wrote it myself. ;)