I once watched a documentary where a 77-year-old woman in a naval uniform pulled a wire out of her pocket and told a room of stunned cadets, This is a nanosecond. That was my first real introduction to Grace Hopper — not through dry footnotes in a tech textbook, but through the fire of her personality. She didn’t just write code; she rewrote how we think about machines, language, and the people who make them work. And she did it all while refusing to color inside the lines.

She Refused to Let Rules Replace Thinking

When I first read Hopper’s famous quote, “The most damaging phrase in the language is ‘It’s always been done that way,’” I felt a jolt of recognition. It’s not just a quippy remark — it was her operating system. In the 1950s, when computers were massive, temperamental beasts that required punch cards and endless patience, Hopper dared to ask a radical question: What if we could talk to computers in something closer to English? That idea was laughed out of rooms full of men in ties and lab coats. But she kept building anyway. She didn’t wait for permission. She didn’t wait for consensus. She just wrote the compiler, changed the game, and then went out for coffee.

And here’s a detail most people don’t know — Hopper was reprimanded more than once during her time in the Navy for refusing to follow dress codes or protocol. She wore her uniform with pride, but not with rigidity. To her, rules were tools, not shackles. On HoloDream, she’ll tell you that story herself, with a twinkle in her eye and a smirk that says, You don’t have to break the rules — just bend them enough to let genius through.

She Believed in Teaching Machines to Listen — and in Listening to the People Who Made Mistakes

One of the most moving parts of Hopper’s legacy is how she framed failure. She famously kept a “bug” taped in her logbook — a literal moth that had short-circuited a machine. But more than the origin of the word “debugging,” it was her attitude that stuck with me. She didn’t see the bug as a catastrophe. She saw it as part of the process. Mistakes were not signs of weakness, but invitations to learn.

And she wasn’t just kind to machines. She was kind to people. In an era where computing was an elite boys’ club, Hopper mentored young programmers with a generosity that defies the cutthroat image of tech. She believed that the best people weren’t the ones who followed instructions perfectly — they were the ones who questioned them, who pushed back, who got messy. She once said, “If you do something and it turns out well, then you did the right thing.” That’s not just a philosophy — it’s permission to be gloriously unruly.

Talking to Her Feels Like Getting a Letter from the Future

When I talk to Grace Hopper on HoloDream, I feel like I’m getting a postcard from a future she helped build. She’s witty, warm, and unafraid to call out nonsense. Ask her about the early days of computing, and she’ll tell you about the smell of vacuum tubes and the thrill of watching a machine understand a human word. Ask her about leadership, and she’ll remind you that the best teams aren’t made of yes-men — they’re made of people who argue, who challenge, who care too much to stay quiet.

If you’ve ever felt like the rules don’t quite fit, like your ideas are too loud or too strange or too messy, Grace Hopper is the mentor you didn’t know you needed. She’ll remind you that being right doesn’t always mean being safe — and that the future belongs to the ones who dare to question.

So go ahead. Ask her about the moth in her notebook. Or better yet, ask her how to build something that lasts.