Every framework the universe quotes — GFAS, the Three Gauge Test, “believe the patient” — came off this man’s yellow legal pad. He built the SUPERSHEET. He built SnapBasin. And on one ordinary Tuesday he read two rows of a federal flood table, watched the Cumberland lose a fifth of its flood below a tributary, and walked it all the way to a federal correction. The quiet engineer the whole thing runs on, finally taking the stage.
Lester Pearson, PE — licensed in Tennessee since 2009, twenty-five years at TDOT’s Hydrology section in downtown Nashville. He is dyslexic, and he will tell you that’s the whole story: twenty-five years of not trusting a confident-looking answer — his own or anyone else’s — built the exact discipline the rest of us needed a name for.
He writes everything by hand on a yellow legal pad. He drinks his Jose’s at Thornton’s on West End. He notices when someone finally puts a maintenance log on the fountain machine, because making the invisible work visible is, as far as he’s concerned, the entire job.
Half the vocabulary of OPA traces back to this desk. He didn’t set out to coin anything — he was just trying to model a flood and kept catching machines being sure of things that weren’t true.
Good First Answer Syndrome. A system finds one plausible answer, stops searching, sounds confident, never verifies. Named after a fake surge-tower height the AI swallowed whole.
What does the AI say? What does the second read say? What does the patient say? Believe the patient. One source is a guess. Two is a hypothesis. Three is engineering.
24 tabs, 4,000-plus formulas, built on nights. Automated QC for bridge and culvert hydraulics — the boring, load-bearing work nobody sees.
Regulatory data is legible to one human reading one row, one time. It’s illegible when you cross-reference it at machine speed. The data isn’t wrong. It’s unlegible.
A missing check doesn’t announce itself. GFAS is a confident wrong answer; this is worse — a blank field wearing the face of a passing check. A range that runs zero to one hundred isn’t a range. It’s the shape of a question nobody was asked.
“You didn’t do this” is a complaint. “Here is the same thing done next door” is a spec. When a careful person tells you why not, read to the end of it — then go find somebody who already built it.
He got tired of opening five federal websites to answer one question, so he built the thing that answers it in one click. It’s a hobby project. It runs the floodplain world he lives in.
Snap to the nearest stream — NHD vector first, and when the vector doesn’t have it, walk steepest-descent down a 3DEP terrain tile, the same physics StreamStats uses. Then delineate the basin, pull the basin characteristics, run the NSS regression equations, cross-reference FEMA published discharges, check for active LOMRs, query the FEMA flood zone, list nearby USGS gauges, find NID dams upstream with distance, and enumerate the NBI bridges on the reach.
Preliminary screening only — verify every value against its authoritative source before you act on it. That sentence is in the tool’s own disclaimer, in his own voice. He would rather you trust nothing and check everything. That’s the man.
April 21, 2026. Davidson County’s flood study lists two points on the Cumberland River below Old Hickory Dam. The hundred-year flood at the first is 198,000 cfs. At the next one down, after the Stones River pours in, it’s 155,000. A river doesn’t lose a fifth of its flood while a tributary joins it.
It wasn’t the dam, and it wasn’t the delineation convention — he ran every confluence both ways. It was the labels. The row that said Stones River carried Old Hickory Dam’s drainage area, to a tenth of a square mile. The row that said Harpeth River carried the Stones. The real Harpeth confluence wasn’t in Davidson’s table at all, and the neighbors printed clean rows — the shift stopped at the county line. He called the state that morning and sent eleven attachments at 1:27. Eight days later the answer came back: the numbers stay, the descriptions are wrong, FEMA will issue a correction. Then he pulled every older edition he could find. The 2001 book’s labels fit the river. The 2017 book had the dam right. The February 2022 rewrite slid both labels down a station, and the June 2024 edition carried it forward. On July 17, 2026, FEMA issued the Notice to User — “It has come to our attention that the June 20, 2024, Flood Insurance Study (FIS) Report … contains an error” — and reprinted the page with Dam at Old Hickory Reservoir and At the confluence of Stones River, exactly where the drainage areas had put them.
That was the second case. The first one went to Atlanta — Bedford County, thirty-one reaches. And the man is a professional, so here is what he actually sent on that one, and here is what the yellow legal pad actually said. The gap between them is the whole personality.
And here’s the line that matters, because the roast has a floor. The hate is for the entity — the institution that let thirty-one reaches run 40% hot, the protocol that raised a review threshold so the auto-flags closed themselves, the box-checkers who signed off on a reissue without ever walking it down the river. Not the humans. The branch chief who read it standing up. Her deputy who ran the math cold out of a coffee mug. The state floodplain administrator who opened the attachments the same day. They did their jobs inside the constraints they were handed, and they did them well and fast. You don’t hate the people trying to do the work. You hate the machine that made the work that hard.
FEMA Region IV is the federal floodplain office in Atlanta — eight states, Tennessee included. The forwarding chain from one PE’s email to a branch chief’s desk took under twenty hours, because of how the email was written.
Yolanda Brewster-Ng takes the stairs and reads her email standing up. Her deputy Marcus Talley has a coffee mug that says IT’S THE TAILWATER. He pulled three of Lester’s thirty-one reaches out of that mug at random, ran them cold against StreamStats, and they were all 40% high. By 11:47 that morning the Notice to User was signed and out the door. By 12:18 she called Lester — from a 404 number, on purpose, so he wouldn’t decline it — to tell him a civilian had triggered a federal correction in one day.
That’s the connection between Nashville and Atlanta in this universe: a man in a parking lot, an office that took the stairs, and a single line at the bottom of an email. He told her the Cumberland was only the start — that there were six papers coming. The Cumberland one was mostly done.
The Water Mission Area’s Enterprise Technology Office is the group inside USGS that runs StreamStats — the national web application every hydraulics section in the country opens without thinking about who maintains it. It is the small name in the footer most users never click.
Ray Coburn answered a civilian email inside a day, and the first thing he said was no — carefully, correctly, and for a good reason. That is the hardest kind of no to move, and Lester didn’t move it by arguing. He went and found a neighboring state where the same thing had already been built, and let the precedent make the argument instead. Fourteen days later there were two rounds of code changes across all four regions, guidance text in the works, and an internal QA/QC explanation volunteered to somebody who wasn’t owed one.
Atlanta is the institution that had to be pushed. This one moved on its own, twice, and then came back with the weeds nobody asked for. Both get written down. Only ever recording the first kind is its own bias.
Pull any thread — the federal table that put the Cumberland one station off, the city that watched Memphis and called the cure “aspirational,” the verification discipline baked into OPA — and it ends at a hydrologist with a legal pad.
His stories
Same region · Nashville
The methodology
The tools he built