787 setback

"Research is what I am doing when I don't know what I am doing."

(W. VonBraun)




Jim




"John Gaquin" wrote in message
. ..

"Chris" wrote in message

Bit of a bummer though.

"Jim Macklin" wrote in message

That's why they test.

If everything were to work perfectly the first time, they wouldn't call it
"development".

"Matt Whiting" wrote in message
...
Chris wrote:

Oh well, perhaps Boeing are going to fast in the development of the 787.
http://www.tulsaworld.com/BusinessSt..._E1_Boein52489

Or perhaps this is just the normal course of events in developing a new
design.

Read some of the detailed stories about Kelly Johnson and the SR-71
development.

Chris wrote:

Oh well, perhaps Boeing are going to fast in the development of the 787.
http://www.tulsaworld.com/BusinessSt..._E1_Boein52489


The chem trail generators failed. The new airplane cannot be certified
until they work as designed.

Matt Barrow wrote:

"Matt Whiting" wrote in message
...

Chris wrote:


Oh well, perhaps Boeing are going to fast in the development of the 787.
http://www.tulsaworld.com/BusinessSt..._E1_Boein52489

Or perhaps this is just the normal course of events in developing a new
design.


Read some of the detailed stories about Kelly Johnson and the SR-71
development.

I've read Kelly's book and also Ben's book. Something else you had in mind?

Matt

RST Engineering wrote:

"Research is what I am doing when I don't know what I am doing."

(W. VonBraun)

I'd add that Research is what you are doing when you don't know what you
are doing or why you are doing it.

Development is when you know why you are doing something, but still
don't what you are doing.

Engineering is when you know both why and what, but aren't sure about
when. :-)


Matt

In article ,
Matt Whiting wrote:

RST Engineering wrote:

"Research is what I am doing when I don't know what I am doing."

(W. VonBraun)

I'd add that Research is what you are doing when you don't know what you
are doing or why you are doing it.

Development is when you know why you are doing something, but still
don't what you are doing.

Engineering is when you know both why and what, but aren't sure about
when. :-)

When I started working in a Research & Development department, my boss
told me that it was alright to discuss the project with anyone in the
company except the Marketing Department. When I asked why Marketing, he
replied, "Because Marketing will try and sell it before we can have it
read for production."

"Chris" wrote in message
...
Oh well, perhaps Boeing are going to fast in the development of the 787.
http://www.tulsaworld.com/BusinessSt..._E1_Boein52489
were they using wet lay-up or pre-preg?

john smith wrote:

In article ,
Matt Whiting wrote:


RST Engineering wrote:


"Research is what I am doing when I don't know what I am doing."

(W. VonBraun)

I'd add that Research is what you are doing when you don't know what you
are doing or why you are doing it.

Development is when you know why you are doing something, but still
don't what you are doing.

Engineering is when you know both why and what, but aren't sure about
when. :-)


When I started working in a Research & Development department, my boss
told me that it was alright to discuss the project with anyone in the
company except the Marketing Department. When I asked why Marketing, he
replied, "Because Marketing will try and sell it before we can have it
read for production."

True, but that is basically marketing's job. Having seen both extremes,
it is better to sell it before it is ready, than to have it ready and
not be able to sell it.

Matt