Home → Writing
Writing
Notes from shipping live systems
Write-ups by Clayton Camera — a technical founder in Orlando, Florida. Things that broke in production, what the fix actually was, and the numbers as they are rather than as they’d read best.
-
Four times my own verification lied to me in five days
Everything I shipped in the last five days was verified before I called it done. Four of those verifications were wrong, in the way that is hardest to catch: the check reports success in exactly the dimension you are watching while being wrong in a dimension y
-
I pointed 30 agents at my own websites and told them to prove each other wrong
I own six domains. Across three working sessions I wired five of them into a single person entity: one @id, defined once, referenced by every property, so that search engines resolve one person instead of six unrelated mentions. That build was agent-driven too
-
The dry run that caught 25 fabricated reply threads
An agent-drafted outreach queue was about to open 25 cold emails with a
Re:— to companies that had never been contacted. What a dry run has to print to catch a well-formed lie, and the pagination default that nearly hid the whole batch. -
When your name is also a thing: entity SEO for an ambiguous name
My surname is a device and the Claytons that outrank me are towns, so the query returns municipal webcams. That’s an entity-disambiguation problem, not a keyword problem — the playbook, the two traps, and the CI guard that keeps it from rotting.
Clayton Camera
Technical founder and software engineer in Orlando, Florida. Builds AI systems, autonomous agents, and full-stack software — including OrbitRoute and KnockFiber. Client work at workwithclayton.com.