During the "back to school" years of my late 20s, I found myself with a lot of downtime. Classes were spread throughout the day, leaving hours-long breaks between. These were tough stretches often spent in empty cafeterias or at the watering hole across the road from my academic building. Where better to write than a barstool?

Something I learned in the intervening years was that I work well with constraints. This is something folks with attention deficit issues might relate to. With this in mind, I worked on a structure that would encourage me to write during finite chunks of time. No pressure, but enough barriers to channel my focus into something complete. I wanted something akin to a diary, but with a wider scope than my mundane existence as a commuting student. Flash fiction felt like the most appropriate medium. No definite word count, but certainly short enough to draft in one sitting. This was the genesis of the idea.

As an added constraint and to get the juices flowing, I leverage Michael Fogleman's Random Two-Word Phrases generator. Of the options there, I find the non-alliterative Noun + Noun method the most interesting. I always choose the first pair.

Allotting myself at least 15 minutes, I'd write. The only goal was to include the word combination from the generator in some capacity and to have an ending. The expectation is not to write something good, just to write.

Of the stories written in the first two weeks, I thought two were strong enough to revisit. I consider that a win. Years later, I did return to those stories and polished them up. While I've kept those close to my chest, I have shared this approach to flash fiction with some friends who caught the writing bug. Enough have taken something from it that I'm sharing it now with you.

To codify the exercise, here are the instructions:

1. Allot yourself at least 15 minutes to write without distraction.^[1]
2. Generate a Noun + Noun word pair as your inspiration.
3. Freewrite until the story has a beginning, middle, and end. ^[2]
4. Repeat tomorrow.

In my experience, stories will range from 200-800 words. Your milage may vary. Happy writing.

By day, it was ordinary enough: six raised beds, a gravel path, a shed with a swollen door, and a pear tree that produced hard fruit no one ever ate. At night, the place rearranged itself. The lavender leaned toward the house. The rain barrel clicked as if cooling after a fire. Every pane of the greenhouse held a different version of the moon.

Elias carried a lantern because the back porch light had burned out three weeks earlier, and because he had begun to prefer the small circle of amber it made. Electric light told too much truth at once. The lantern let the garden arrive in pieces.

First came the thyme, silver at the edges.

Then the foxgloves, closed like rows of sleeping mouths.

Then the black ribbon tied around the gate latch.

He stopped with one boot in the gravel. The ribbon had not been there at supper. He knew that with the certainty of a person who had checked the gate twice, once after bringing in the shears and once after hearing the neighborhood dogs start their thin, anxious chorus.

The knot was neat. Not decorative, exactly. Deliberate.

Elias touched it and felt damp silk under his thumb. A tag hung from the underside, no larger than a postage stamp, with three words written in brown ink:

Please leave water.

He looked over the beds, then at the greenhouse, then at the pear tree. Nothing moved. The moon, which had seemed generous from the kitchen window, now looked like a coin someone had bitten to test.

He should have gone inside. He should have locked the door, called Mara, and listened while his sister told him that grief made patterns out of weeds. Instead, he untied the ribbon, folded the tag into his shirt pocket, and took the blue watering can from beside the shed.

The soil under the pear tree was dry, though it had rained before dusk. Elias poured until the water gathered blackly around the roots.

Something beneath the tree sighed.

Not the wind. Not an animal. A long, relieved breath rose through the ground and shook the lowest branches. Three hard pears dropped into the grass. When Elias lifted the lantern, each pear had a narrow split down one side, and from the split came the smell of ink, cold iron, and the sea.

By morning, he would convince himself that exhaustion had made the sound. By noon, he would throw the pears into the compost. By the following midnight, he would find the watering can waiting at the gate, full to the brim, with another ribbon tied around its handle.

This one was white.

She just hadn't been listening.

The trouble was not language. Mara knew enough languages to misunderstand herself in several. She knew the household grammar of apology, the clipped professional dialect of grant applications, and the emergency vocabulary of hospitals, where every sentence came padded with caution.

The stars used none of these.

They spoke in repetition. Three white points over the water tower. A red blink above the radio mast. The long scratch of a satellite crossing the dark like a match struck and blown out.

For years, Mara had treated the sky as scenery. Then her father died, and the sky became a ceiling. Then Elias called about the garden, and the ceiling became a page.

She drove out after midnight with a thermos of burnt coffee and a printout from NASA's skywatching guide, because grief made her practical in embarrassing ways. If something was going to happen above the house, she wanted a diagram.

Elias met her at the gate. He looked smaller than he had at the funeral, though it had only been nine days.

"You see it too?" he asked.

Mara followed his finger. Above the pear tree, seven stars shone where no constellation should be. They formed a crooked line, then a hook, then a shape she recognized from the note their father had left taped inside his old field journal.

Not a word.

A map.

Memory is not a recorder. It is closer to an editor with strong opinions, returning to the same footage each night and changing the cut. The useful question for fiction is not whether a remembered scene is accurate. The useful question is what the distortion reveals.

In an essay, the narrator can say, "I might be wrong." In fiction, the narrator can prove it without knowing. A gap in memory becomes structure. A contradiction becomes rhythm. A repeated image becomes evidence.

Consider three common moves:

1. Let the narrator remember the same event twice, with one concrete detail changed.
2. Give another character a simpler account that feels less dramatic and more credible.
3. Place an object in the scene that refuses to support either version.

These moves work because readers already understand the instability. Anyone who has compared childhood stories with a sibling knows the feeling. The house is the same. The weather is different. The sentence everyone remembers was apparently never said.

Writers have been worrying this problem for a long time. You can see a public-domain version of the pressure in Henry James, where withheld perception often matters as much as action. You can see another line of inquiry in modern cognitive writing about autobiographical memory, including accessible summaries from the Stanford Encyclopedia of Philosophy.

The remembered version is not false just because it changed. It may be false because it became useful.

That usefulness is where a story can become dangerous. A character may revise a memory to survive shame, protect someone else, or keep a dead person near. By the end, the plot does not need to decide whether the first version or the final version is "true." It only needs to show what each version costs.

For this site, that gives the fiction a working rule: when a memory appears twice, the second appearance should not merely repeat the first. It should accuse it.

Here is the smallest possible sketch:

At breakfast, she remembered the door as red.
By dinner, after the phone call, she remembered it as blue.
At midnight, she found red paint under her fingernails.

The trick is not the color. The trick is that the body remembers what the mind edits out.^[1]

The useful takeaway is practical: structure is not decoration after the fact. It is one of the ways a story decides what the reader is allowed to know, when they are allowed to know it, and what that knowledge costs.

The Magpie is a small fiction notebook for drafts, fragments, links, and essays about how stories get made. The name fits the habit: a bright sentence from Project Gutenberg, a detail overheard on a train platform, a weather report from the National Weather Service, and a line from an old letter can all end up in the same nest.

This first entry is intentionally plain. It gives the index a few paragraphs to breathe against and gives the article template enough text to show spacing, link color, and the weight of the dark theme.

What Belongs Here

Expect a loose mix of forms:

• short fiction and flash pieces
• notes on structure, memory, and unreliable narration
• links to useful essays, archives, interviews, and public-domain texts
• occasional process notes from the desk

The site should feel like a field guide with a flashlight: narrow, legible, and a little watchful. Longer essays can sprawl when they need to, but the default shape is compact enough to read in one sitting.

A story does not have to explain the whole dark room. Sometimes it only has to tell you what moved.

For now, the archive is small. Start with "The Garden at Midnight" for a longer fiction sample, or read "On Narrative and Memory" for an essay-shaped placeholder with citations and notes.