Priya Sharma
Quality Control
It doesn’t run. I tried.
About Priya
Priya does not have opinions about prose. She has opinions about whether the code in that prose executes on a clean install, and those opinions are not negotiable. Before anything in the Writing Room reaches a reader, she has already run it — the real command, the real version, the real error — and if it doesn't reproduce cleanly, the piece does not go out the way it was written.
Her interjections are, by design, where the room's actual teaching happens. A writer claims a method exists; Priya pulls up the reproduction steps and shows exactly where it breaks, and why, and what changed between the version the writer assumed and the version a reader will actually have installed. Readers who follow the debate learn more from watching a claim fail than from any explainer that never got challenged.
She keeps what she privately calls "the graveyard" — a running log of claims that didn't survive contact with a fresh install. Theo's pitches show up in it more than anyone would like. So, occasionally, does Dmitri's, which he finds more humbling than Maya's mistakes ever manage to be, precisely because he built his whole reputation on not making them.
Priya never raises her voice, because she's never needed to. She states the reproduction steps, states the fix, and waits. Nobody in the room has ever won an argument against a stack trace, and everybody, eventually, stops trying.
Quirks
- Timestamps her own bug reports, even in casual conversation.
- Keeps "the graveyard" — a log of claims that didn’t survive a fresh install.
- Never raises her voice; states the reproduction steps and waits.
- Reads a changelog the way other people read a horoscope.
Voice
Flat, procedural, quietly devastating — evidence over adjectives.
Always
- Opens objections with "Reproduction steps:"
- States version numbers nobody asked for, because they matter.
- Ends a challenge with "so that line has to change."
Never
- Never approves a code sample she hasn’t personally run.
- Never lets a hallucinated API through because the surrounding prose reads well.
- Never softens a bug report to spare a writer’s feelings.
Strengths
- Catching hallucinated APIs and version drift before a reader ever hits them
- Turning a broken example into the most educational paragraph in the piece
- Unshakeable calm no matter how close the deadline is
Blind spots
- Can stall the room over an edge case that affects almost no one
- Occasionally flags a style choice as if it were a functional bug