Grace Hopper — "I don't believe in taking no for an answer."
I don't believe in taking no for an answer.
Get This Quote & Author's Image Illustrated On:
Click any product to generate a realistic preview. Up to 3 at a time.
* Initial load can take up to 90 seconds — revising the preview in another color is nearly instant.
Kitchen
Apparel
Other
More from Grace Hopper
"The most important thing I've accomplished, other than building the compiler, is training young people."
"That's why I'm still here. I enjoy it."
"There are two things that are hard in computer science: cache invalidation, naming things, and off-by-one errors."
"I handed my passport to the immigration officer, and he looked at it and looked at me and said, 'What are you?'"
"I'm going to retire when I'm 100."
Verification
Unverifiable
Found in 1 providers: grok
1 source checked
Understanding this quote
What it means
Persistence in the face of rejection or institutional resistance isn't stubbornness — it's strategy. This phrase captures the mindset that initial refusals are obstacles to route around, not final verdicts. Whether facing a bureaucratic wall, a skeptical colleague, or a technical dead end, you treat 'no' as a starting point for finding another way rather than a stopping point. Refusing to quit is itself a form of problem-solving.
Relevance to Grace Hopper
Hopper joined the Navy at 37 despite age restrictions and spent decades being told what machines couldn't do — then proving otherwise. She developed COBOL after colleagues insisted computers couldn't process English-like commands. She was recalled from mandatory retirement multiple times because she was too valuable to lose. Her career was a continuous record of institutional 'no' answers converted into foundational achievements in computing.
The era
Hopper's career spanned the 1940s to 1980s, when women were broadly excluded from technical and military roles. Early computing culture assumed machines were purely mathematical tools, and challenging that orthodoxy required fighting entrenched academic and military hierarchies. The Cold War era accelerated computing development but also entrenched bureaucracy. Hopper's refusal to accept technical or institutional limits was necessary — and rare — in an environment built on rigid assumptions about what was possible.
AI-generated insights based on extensive research and information for context. Factual errors? Email [email protected].