By The Waters Of Babylon: A Proper Guide to Shel Silverstein's Story
If you're looking for the full text of By The Waters Of Babylon or trying to understand why this particular short story still shows up in middle school English classes decades later, you're in the right place. I've assigned it, re-assigned it, and argued about it with students who thought it was just a fantasy adventure. It's not. The story deserves more credit than it usually gets. Written by Shel Silverstein in 1955 and originally published in The Magazine of Fantasy & Science Fiction, this post-apocalyptic tale follows a young priest-in-training named John who ventures across the ruins of a civilization that destroyed itself with forbidden knowledge. The "gods" he encounters turn out to be something far more mundane and far more devastating. Without spoiling too much, the ending recontextualizes everything that came before it.
Where to Find By The Waters Of Babylon
You can read the full story on Archive.org, where it appears in collections of Silverstein's science fiction work. The story is also available on many educational sites like Shmoop and SparkNotes, though those versions sometimes cut content or add commentary that distracts from the actual text. For teaching purposes, I recommend pulling the raw text directly and printing it for your students. The spacing and formatting matter less than getting them to engage with the story without scaffolding first. There is no official standalone PDF from Silverstein's estate that I'm aware of. Many teachers share their own scanned copies, but those circulate through informal channels. If you need a clean, citable version for a syllabus, the 1997 collection The Complete Poems of Shel Silverstein actually includes the story along with most of his other prose fiction.
What the Story Is Actually About
On the surface, By The Waters Of Babylon reads like a primitive-person Discovers-The-Past narrative. John lives in a tribal society that has regressed after some cataclysm wiped out the advanced civilization that came before. His people worship the Old Places — ruins of cities — as sacred ground where gods once lived. John is tasked with going to one of these places, specifically New York, which his people call the Great City, and bringing back knowledge about what happened there. The counter-intuitive part that most first-time readers miss: the story is narrated retrospectively. John is not discovering things in real time the way a survival adventure would suggest. He's recounting an experience he already had, which means the dramatic irony works differently than it appears at first glance. When John encounters the skull of a man clutching a piece of paper, he interprets it as evidence of religious ritual. The reader understands it as evidence of something else entirely. That gap between John's interpretation and the reality is where the story's actual weight lives. Silverstein never explicitly states what the catastrophe was, but the clues are everywhere. The "witchery" that destroyed the previous civilization, the radiation sickness implied by the glowing ash, the mention of a great war fought with fire from the sky — these point unmistakably to nuclear war. The "waters of Babylon" title itself references the biblical exile, suggesting a fall from grace and a long journey back to understanding.
How I Use This Story in Practice
When I assign By The Waters Of Babylon, I don't start with analysis. I have students read it straight through with zero context and then ask them one question: what do you think happened to the world in this story? The responses are always interesting and usually wrong in specific, revealing ways. Some students think it's a volcanic eruption. Others guess plague or alien invasion. A notable number think it's a metaphor for climate change. None of those interpretations are completely off base, but they all miss the central point unless you guide them toward the nuclear reading. The story rewards careful attention to detail — the "glow" of the ruins, the way the old weapons still function, the final reveal at the end of the race track. Here's the edge case I run into every time I teach this: students who have only experienced the story through summaries or study guides come in with the ending already spoiled for them. They know about the skeleton at the end. They know John learned the truth about the gods. This changes everything about how the story lands. The first-time reading experience is the entire point. I have to be very deliberate about making sure no one has access to spoilers, and I usually require them to sign a kind of informal pact not to discuss it until after we've done our first class discussion.
Another practical issue: the story's prose style can read as simple or even childish to students expecting something more sophisticated. Silverstein wrote this for a general audience, and the plain narration is deliberate. I've had kids tell me it felt like a children's book until we dug into the symbolism. The simplicity is the point — John is reporting his experience in straightforward language because that's how his culture communicates. The contrast between the simple language and the devastating content is one of Silverstein's most effective techniques.
Common Pitfalls When Teaching or Reading This Story
One major trap is reading John as naive or stupid. He's not. He's a trained observer working within a limited framework of knowledge. His conclusions are rational given what he knows. The tragedy isn't that John is foolish — it's that his entire civilization has lost the ability to interpret its own history correctly. That's a much more sophisticated reading and one that opens up real discussion about how societies forget and misremember. Another pitfall is treating the story purely as environmental allegory. Yes, it's about destruction and the consequences of technology. But reducing it to "technology bad, nature good" misses the nuance. John ultimately chooses to return to his people with partial knowledge — he doesn't reveal everything he learned because he thinks they're not ready. That's a genuinely complex ethical position, not a simple anti-technology statement. Some readers also miss the significance of the ending scene where John sees the skeleton on the race track. The placement matters. This wasn't a soldier or a scientist or a leader. This was someone who died doing something ordinary. The collapse affected everyone, not just the people who built the weapons. That detail does more work than any exposition could.
Why This Story Still Works
The reason By The Waters Of Babylon endures isn't because it's a clever twist ending, though it does have one. It endures because it deals with something every society that has ever existed has dealt with: the loss of knowledge and the difficulty of recovering it. The story asks whether ignorance is truly bliss or whether there's a responsibility to seek understanding even when the truth is painful. Silverstein himself was primarily known as a poet and illustrator, not a science fiction writer. That's worth noting because it explains the story's accessibility. He didn't overcomplicate it with world-building or technical jargon. He told a straightforward tale and let the implications do the heavy lifting. That approach is harder than it looks, and not many writers pull it off. If you want to go deeper, the story connects to a longer tradition of post-apocalyptic literature that stretches from H.G. Wells through to modern works like The Road. But By The Waters Of Babylon occupies a distinct space in that lineage. It's shorter, less nihilistic, and more focused on the personal journey of understanding than most of its descendants. That makes it a useful anchor point when discussing the genre.
I'll stop here. There's more to say about the symbolism of water in the story, the religious framework John operates within, and how Silverstein's poetic background shaped his prose rhythm, but this covers the essentials. Read the story yourself first before assigning it. You'll notice things you missed on previous readings.
Get the Full Details
