Building ARCS in the open
A recruiter I did not know messaged me on a Saturday. What came after was a month of the most productive procrastination of my life, and a spell-checker for my own honesty whose first catch was mine.
A recruiter I did not know messaged me on a Saturday, about a company I had never heard of. Nearly everyone archives that message. I ran a ten-minute check instead.
Three questions, no more. Does the sender actually exist. Does the role exist somewhere they do not control. And one thing no script can answer: what is the story with the team. It passed. Honest answers pass, and so do honest gaps, because "I do not know much yet" is harder to fake than a pitch.
Cheap to run, hard to fake. The same instinct that later kept me off a malicious repo started here, on a cold DM.
Then the part that matters. The application itself took two minutes, run right before the call, because the hours had gone into a reusable method, not a document.
This is the unlock most people hold backwards. They use AI to speed up the task, then re-prompt from scratch the next time. The compounding move is the opposite: build the machine once, and make every future task a two-minute run of it. The first one is slow. The hundredth is free.
What happened next looked like procrastination and was the opposite. I kept not-quite-finishing the application because the tools I was building to finish it kept turning into better tools.
My notes started filing themselves: the index rebuilds from the files' own headers, so nothing can quietly fall out of it. The links between notes drew a pyramid on their own, and the single most-cited idea in the whole archive turned out to be cut, do not add. A privacy gate I wrote refused one hundred percent of exports on its first day, correctly, because I had not yet told it what was safe to let out.
Auditing your own month is uncomfortable in exactly the way that makes it useful.
And my favorite, the one I did not design and could not have. The automated check that keeps my public pages honest rejected a commit. Not any commit. The very commit that created my doctrine about drift, because that commit had itself caused drift.
I had built a spell-checker for my own honesty, and its first catch was mine, in the sentence announcing it. There is no better proof that a control works than watching it refuse to spare its author.
The easiest person to lie to is yourself, which is exactly why the receipt has to be able to overrule you.
Receipts, or it did not happen. Not as bureaucracy, but because the easiest person to lie to is yourself, and a dated receipt is the one witness you cannot talk out of it.
Some procrastination is not avoidance. It is your attention reading a window your calendar has no axis for, and the honest move is to follow it and log what you find, not to shame it back into the task.
And your worst critic makes an excellent employee, once you give it a job description. Turned loose it corrodes; scoped to a gate, it is the most reliable colleague you have.