Building an airplane was nothing compared to shepherding…
““Building an airplane was nothing compared to shepherding research through Langley's grueling review process. "Present your case, build, sell it,= so they believe it" --- that was the Langley way. The author of a NACA document --- a technical report was the most comprehensive and exacting, a technical memorandum slightly less formal --- faced a firing squad of four or five people, chosen for their expertise in the topic. After a presentation of findings, the committee, which had read and analyzed the report in advance, let loose a barrage of questions and comments. The committee was brusque, thorough, and relentless in rooting out inaccuracies, inconsistencies, incomprehensible statements, and illogical conclusions obscured by technical gibberish. And that was before subjecting the report to the style, clarity, grammar, and presentation standards that were Pearl Young's legacy, before the addition of the charts and fancy graphics that reduced the data sheet to a coherent, visually persuasive point. A final report might be months, even years, in the making.””
About This Quote
This interpretation was drafted with AI assistance. It is one reading of the quote, not the author's own explanation.
Technical reporting demands rigorous scrutiny, relentless questioning, and clear communication to survive expert review.
In simple terms: Technical reports face tough review.
Key Takeaway
Prepare thorough, clear documentation.
Themes
science
communication
rigor
Mood
analytical
determined
Type
inspirational
philosophical
When to use this quote
- research proposals
- grant applications
- technical manuals
- policy briefs
Key Concepts
engineering
peer review
Questions to Reflect On
- How do you balance thoroughness with efficiency?
- What strategies improve clarity under scrutiny?
A Different Perspective
Overly detailed scrutiny can delay progress and stifle innovation.