Operations · rights, catalog & records · Remote from Jefferson City, MO
Eight years of catalog and rights administration taught me one habit: a record isn’t reliable until it’s been checked against another source. That habit is the whole job — whether the records are copyright registrations, royalty statements, vendor accounts or customer files.
Systems I administer in
Everything I use →
In rights administration
“A record isn't reliable until it's checked against another source.”
In software
“A feature isn't done until it's tested and confirmed working.”
Those are the same sentence. I wrote one of them about metadata and the other about software, years apart, before I noticed they were the same rule. It’s why I build systems that don’t trust themselves — including the ones I run by hand. That rule is the only thing I’d ask you to judge me on.
Every figure below traces to a record I can produce on request. There aren’t more of them because I don’t have more that are true.
Said up front, not in the interview
I don't write code by hand, and I don't make the specific engineering calls either — Claude Code does. My work is the architecture: I scope the system, set the goals and constraints that shape the technical trade-offs, sequence the build so nothing gets built on a missing foundation, and define what 'done' actually means before anything ships.
I don’t hide this, because a reader who finds it out later reads everything else as inflated. Directing a build well is a real skill and a different one than writing the code, and I’d rather be judged on the one I actually have.