← Back to Off Hours

Trying to Take Notes on Greek Mythology

Myths as Documentation

Whenever I study Greek mythology, I end up taking notes.

Not because I want to, but because I have to. There are too many people, too many relationships, too many overlapping stories to keep straight in my head. And even then, it never quite works. I can’t just write something down and say, “this is the story.” There’s always another version.

It drives me a little crazy. I want there to be a clean version. A single source. Something I can point to and say: this is how it happened.

I want to be able to take clean, simple notes without a maze of conditional branches. I want to draw a family tree and have it actually make sense - to see how everyone fits together at a glance. (Even though I know, realistically, that almost everyone is related to Zeus, which already makes any family tree a mess, regardless of any contradictions.)

But that’s not how it works. Homer tells one version. Hesiod tells another. Playwrights reinterpret things. Different regions tell their own variations. The same figure shows up with different origins, different motivations, sometimes even a different role entirely.

When I write documentation for work, there’s usually one version. Azure can do X, but AWS can do Y. Here are the benefits of each… Here’s how our team prefers to set up a .NET 8 Function Build in Azure DevOps, etc. Sure there may be different ways to accomplish things, but the rules overall are the same.

With Greek mythology, there isn’t a single source of truth. And somehow, after millennia, it all still holds together.


The more I’ve sat with that, the more it feels less like a flaw and more like a different kind of system.

Myths weren’t written as a canonical reference. They weren’t meant to be consistent in the way we expect documentation to be consistent. They were closer to shared context than recorded fact.

They carried meaning, relationships, expectations - just not in a perfectly structured way. If you look at them that way, the contradictions start to make a little more sense.


Take Aphrodite.

Depending on where you are and who you’re reading, she isn’t quite the same figure.

There’s Aphrodite as a more universal force-love, beauty, connection (Aphrodite Ourania). There’s a more civic version, tied to social life and the structure of the city (Aphrodite Pandemos-the aspect that shows up in the Iliad). And in places like Sparta, there’s even Aphrodite Areia-associated with war.

Same name, different emphasis.

Those distinction aspects - Ourania, Pandemos, and Areia - aren’t contradictions so much as lenses. Each version highlights something different about what she represents, shaped by the context it came from.

If you try to write that down cleanly, it’s frustrating. Which one is correct? Which version is the real one?

The answer is: all of them, depending on where you’re standing.


That’s the part that took me a while to get used to. I kept trying to treat mythology like a system with a single source of truth. One authoritative version, clearly defined, internally consistent. But it’s not that kind of system; it’s more like a distributed system.

There’s no central authority enforcing consistency. Instead, there’s a shared understanding that gets shaped and reshaped over time. Different regions emphasize different aspects. Different authors reinterpret the same figures. Stories adapt to fit the needs of the people telling them.

And the system doesn’t break because of that variation - it survives because of it.


From a modern perspective, it’s easy to see inconsistency as a problem.

We’re used to having a single place to look. A document, a system, a source that defines what’s true. When that doesn’t exist, it feels like something is missing.

But in ancient Greek mythology - a system spread across regions, authors, and generations - the goal wasn’t perfect consistency. It was shared understanding.

People didn’t need every detail to match. They needed to recognize the shape of the story, the relationships between figures, and te general sense of what things meant. That was enough to keep everything coherent, even when the details didn’t line up.


I still take notes when I read mythology. I still try to organize things, map relationships, make sense of the variations. That instinct isn’t going away. And honestly, it still bothers me a little that I can’t reduce everything down to a single clean version. But I’ve started to see that frustration differently. It’s not that the system is broken. It’s that it was never designed to work the way I want it to.