Background and Context
Grace Hopper gave this account to Lynn Gilbert around 1980–1981, for the interview collection Particular Passions, when she was in her mid-seventies and near the end of a Navy recall that had already stretched decades past any ordinary retirement. By then the landmarks were behind her: the Harvard Mark I in the war years, the first working compiler in 1952, the machine-independent languages that led to COBOL and put programming within reach of people who were not mathematicians. She had every reason, at that vantage, to name the compiler as her monument. Instead she set something beside it — the training of young people — and ranked the two as equals. The remark is not a modest deflection; it is a considered verdict from someone who had built both machines and careers and was in a position to weigh them against each other.
Interpretation
The load-bearing move is the opening clause: "other than building the compiler." Hopper invokes her single most consequential technical achievement only to set it down and reach for something she rates as its peer. The compiler was the act of translation that turned human intention into machine instruction — the thing that let a person say what they wanted and have the machine work out the how. Read the second half of the sentence and you find her describing the same act performed on people. "They come to me… and say, 'Do you think we can do this?' I say, 'Try it.' And I back 'em up." That is a compiler in human form: she takes a junior's uncertain, half-formed intention and converts it into permission, cover, and forward motion. The parallel is almost certainly deliberate in a mind as precise as hers — mentorship as the compilation of potential into action.
Notice how little the method contains, and how much rests on each part. "Try it" is the whole of her instruction — not a curriculum, not a technique, just the removal of the question's paralysis. "I back 'em up" is the load-bearing clause: permission to try is cheap and worth little unless someone absorbs the cost of failing, and she names that as the thing "they need." Junior people rarely lack ideas; what they lack is the standing to risk one, because the downside falls entirely on them. Hopper's contribution was to stand between them and that downside. And the final image — "I stir 'em up at intervals so they don't forget to take chances" — reveals that she understood risk-taking not as a trait but as a habit that decays. People grow cautious as they accumulate things to protect; the mentor's ongoing job, years after the first "try it," is to keep re-opening a door that age and success quietly tend to close.
Current Relevance
The sentence reads now as a rebuke to how mentorship is often practiced and measured. Contemporary organizations formalize it — mentorship "programs," matching software, quarterly check-ins — and in doing so tend to reduce it to advice-giving and networking. Hopper's model is almost the opposite: not counsel from a distance but the active assumption of another person's risk. In a professional culture increasingly organized around individual metrics and personal brand, "I back 'em up" describes a senior person spending their own hard-won credibility to cover a junior's mistake — an act that shows up on no dashboard and is, for exactly that reason, vanishing. Her framing also lands on the modern anxiety about psychological safety: decades of subsequent research (Amy Edmondson's foremost among it) confirm what Hopper stated plainly — that people take the creative risks an organization depends on only when someone has visibly made it safe to fail. She was describing the mechanism forty years before it had a literature.
Impact and Legacy
Hopper's reputation as a mentor is not a retrospective gloss; it was her documented signature in life. She was known Navy-wide for pushing juniors past their own caution and shielding them when it went wrong, and she toured relentlessly into her eighties telling young audiences the most damaging phrase in the language was "we've always done it that way." That legacy is now institutional: the Grace Hopper Celebration, the world's largest gathering of women in computing, carries her name precisely because "training young people" — especially those the field overlooked — was understood to be as central to her as any algorithm. The quote endures because it comes from unimpeachable standing. When most people rank relationships above achievements we suspect consolation; when the inventor of the compiler does it, having built the achievement in question, the ranking carries the weight of expertise.
Contrasting Views or Controversies
- The survivorship reading. Hopper could afford to prize mentoring because she had already secured a monumental career; "the most important thing" is an easy thing to say from the far side of the compiler. For a junior person still fighting for standing, her generosity may describe a luxury of the arrived rather than a strategy for the arriving.
- "Try it" does not scale everywhere. The ethos suits software and research, domains where a failed experiment is cheap and reversible. In medicine, aviation, or structural engineering, "back 'em up and let 'em take chances" collides with the fact that some failures are catastrophic and irreversible — the very fields that built the checklists and rote procedures her spirit resists.
- Backing someone up has a ceiling. A mentor's willingness to absorb risk is bounded by their own finite credibility; spend it on too many juniors, or on one who repeatedly fails, and the shield stops working for anyone. The model romanticizes a resource it treats as unlimited.
Practical Application
- For the individual mentor: Move past advice to cover. The distinctive, costly thing Hopper names is absorbing the downside of a junior's risk — putting your own standing behind their attempt so failure lands on you, not only on them. Ask of any mentoring relationship: whose reputation is actually on the line when this person tries something?
- For the person being mentored: Hear "try it" as an instruction to act before you feel ready — the readiness rarely arrives first. And recognize that the value of a senior ally is not their advice but their willingness to back you, and seek the ones who will.
- For organizations: Reward the invisible work. The senior engineer who covers a junior's failed bet produces nothing a metric captures, yet Hopper ranked that act with inventing the compiler. Build recognition for it, or watch it disappear under individual-performance incentives.
- For anyone growing more senior: Take seriously the decay she named. Caution accumulates with things worth protecting; schedule the deliberate act of "stirring up" — your own risk appetite and that of the people you've raised — because left alone it only ossifies.
Background on the Author
Grace Murray Hopper (1906–1992) was a mathematician, U.S. Navy Rear Admiral, and one of the founding figures of modern computing. She earned a Yale Ph.D. in mathematics in 1934, programmed the Harvard Mark I during the Second World War, wrote the first compiler in 1952, and drove the development of the English-like, machine-independent languages that culminated in COBOL — the innovation that opened programming to people who were not specialists. She served across four decades and retired as a Rear Admiral in 1986, among the oldest officers then serving. Her authority on training young people is earned from the exact seat where the claim is credible: she spent one career translating inaccessible machine code into human-usable language, and a parallel career translating uncertain juniors into people who dared. When the inventor of the compiler says shaping people mattered as much as shaping machines, she is not offering a sentiment — she is reporting a measurement, taken by someone uniquely equipped to take it.