Grace Hopper — "I've always objected to doing anything over again if I had already done it once."
I've always objected to doing anything over again if I had already done it once.
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
"From then on, when anything went wrong with a computer, we said it had bugs in it."
"The trouble with people is, they don't want to think."
"I don't know what the future holds, but I know who holds the future."
"I'm not a computer scientist. I'm a mathematician. I just happen to work with computers."
"Never, never, never take the first no. There are a certain number of people in business, industry, and government who always say no the first time you suggest something new, because they're lazy... Bu…"
Details
Expressing her drive for efficiency and automation, which was central to her work on compilers.
Date: Unknown
GeneralVerification
Unverifiable
Found in 1 providers: gemini
1 source checked
Understanding this quote
What it means
Refusing to repeat completed work isn't laziness — it's efficiency. This quote captures a drive to solve a problem once, then systematize or delegate that solution so human effort moves forward rather than cycling back. It rejects redundancy as intellectual waste. The underlying principle: if a task is worth doing, it's worth making replicable, so the next instance requires no human effort at all.
Relevance to Grace Hopper
Hopper built the first compiler in 1952 specifically because she found it absurd that programmers rewrote identical mathematical routines by hand repeatedly. She argued computers should handle repetitive work — that was the entire point. She then co-developed COBOL so business logic written once could run anywhere. Her career was a sustained campaign against manual repetition, making this quote the guiding principle behind her entire body of work.
The era
In the 1940s and 1950s, programming meant writing binary or assembly instructions by hand for each machine — no abstraction layers, no shared libraries, no reuse between computers. Every calculation was rewritten from scratch. Hopper entered computing at Harvard's Mark I during World War II and spent the following decades watching this inefficiency persist industry-wide. The era made repetition feel inevitable; she spent her career proving it wasn't.
AI-generated insights based on extensive research and information for context. Factual errors? Email [email protected].