Some parts of the book

Before I have a chance to comment, Charlie confidently states, "Everybody knows that projects don't finish on time or on bud- get, and if they do it means they had to compromise on content. Especially in systems programming or product design."

"That is not necessarily the case," I say. "Occasionally, there are design engineering projects that finish much ahead of time, significantly under budget and deliver more than was prom- ised."

Those with any experience working in or with design engi- neers, which means about half the class, find it hard to believe such a claim.

"In the early fifties," I continue, "the Russians announced that they, too, had an atom bomb. That came as a total surprise. It became apparent to the U.S. that it had to find a way to moni- tor what the Russians were doing in their vast Asian territories." "That's how the space satellite program started," one of the students guesses.

"I'm afraid that at that time satellites were to be found only in science fiction books," I have to disappoint him. "But, jet air- plane technology was rapidly developing. One reputable engi- neer, Clarence "Kelly" L. Johnson, suggested building a plane that could fly at altitudes above the ceiling reached by fighter planes. Do you know how much time it takes to develop a new airplane? I mean from concept to an operational weapons sys- tem?"

"Over ten years," Brian says confidently. "I served in the Air Force."