The Man Page Nomad of Nebraska: A Weekend With the Last Consultant Who Reads the Whole Manual

Dale Kowalski's office is a 2014 Subaru Outback with 210,000 miles on it, a cup holder full of Pepto-Bismol, and a laptop that has outlived four national elections. He drives it across Nebraska, Iowa, and occasionally into Kansas when the money's right, showing up at feed co-ops, regional banks, and one very confused ethanol plant to fix servers that no living employee understands.

He is, as far as we can tell, the last of his kind: a consultant who reads the entire man page before editing a single line of config.

The Method, Such As It Is

Here's how a Dale job works. He arrives. He shakes hands with whoever drew the short straw. He asks for the conference room, a pot of coffee, and — this is the part that baffles his clients — the documentation.

Not the wiki. Not the README someone wrote in 2019. The actual manual, printed if necessary, which he reads like a paperback thriller, dog-earing pages and muttering things like "huh, that flag's been there the whole time."

"People think reading the docs is slow," Dale told us somewhere between Grand Island and a failing BIND deployment. "You know what's slow? Spending eleven hours guessing. I read for two, I fix in one. My competitors guess for three days and bill you anyway."

It's hard to argue with the math. Dale bills $400 an hour and turns down work constantly.

Job One: The Bank That Forgot Its Own Cron

Our first ride-along was a community bank in Kearney whose nightly batch job had been failing for five weeks. Three contractors had poked at it. Two had proposed "a full cloud migration," which in bank-speak means "we don't know either."

Dale read the cron man page. All of it. Then he read the crontab, then the shell script it called, then — because the script used a flag he hadn't seen in a while — he read the docs for that too.

The fix took nine minutes. A daylight saving time edge case, documented in a paragraph that one of the previous contractors had literally been staring at, in a browser tab, when Dale walked in.

"He had it open," Dale said, packing up. "Open! The answer was on his second monitor. He just didn't read past the first Stack Overflow answer."

Job Two: The Ethanol Plant Incident

The second job is the one Dale will tell at bars until he dies. A plant control network, a daemon written in 2003 by a contractor who has since retired to Florida and, per Dale, "absolutely cannot be bothered." No source code. No comments. One man page, in a binder, with coffee rings on it.

The daemon was dying every 72 hours like clockwork. Previous consultants had thrown monitoring at it, restart scripts at it, prayers at it.

Dale read the binder. Twice. On the second pass he noticed a footnote — a footnote — about a file descriptor limit on Solaris, which the system had been migrated away from, but whose limits had been faithfully recreated in a compatibility config nobody remembered adding.

Raised the limit. Daemon's been running for fourteen months. The plant sent him a ham.

The Question Nobody Wants to Say Out Loud

Dale is 63. He mentions retirement the way other people mention the weather — casually, often, and with a twinkle that suggests he enjoys the reaction. When he goes, a decade of institutional knowledge across three states' worth of unglamorous backend infrastructure goes with him.

And here's the uncomfortable part, the reason this piece belongs in War Stories instead of some misty retirement tribute: nobody is lining up to replace him. The junior devs we talked to at the bank were bright, fast, and armed with AI assistants that could scaffold a Kubernetes cluster in seconds. None of them had ever read a man page. One asked us, sincerely, what a man page was.

Dale's take is gentler than you'd expect. "They're not lazy. Nobody ever told them the manual was the shortcut. We had nothing else — dial-up cost money, so you read what you had. They've got infinite everything, so they've learned to skim. Skimming works until it really, really doesn't."

What He's Leaving Behind

Dale's parting gift to the region is a one-page document he hands to every client on his final visit. It says, in full:

1. Read the manual before you change the thing.
2. Write down what you changed and why.
3. When it breaks at 2 a.m., the answer is usually in paragraph nobody read.

That's it. That's the whole succession plan.

We asked him if he was worried about the generation coming up behind him. He thought about it for a long time, watching the corn go by.

"Every generation of sysadmin thinks the next one's doomed," he said. "The init war guys thought systemd kids were doomed. The systemd kids think the AI kids are doomed. The machines keep running either way. Somebody always reads the manual eventually — usually around hour eleven of the outage."

Then he pulled over, because we'd arrived, and somewhere in Iowa a daemon was about to get fixed the old way: slowly, correctly, and with full documentation.

Godspeed, Dale. The ham was well earned.