Your Apex class has a sharing posture. You just haven't declared it.
I was reviewing a service class in a mature org. Clean code, well-tested, passing all the gates. Then someone asked: "Is this running with or without sharing?"
SHORT-FORM
Short Reads.
Principles and dispatches. Pointed pieces you can finish in a minute.
Type a concept, topic, or phrase — results ranked by semantic relevance
Killing Secrets in Packaged Apps
There is a specific feeling when a security review comes back with "hardcoded credentials" in the findings. Not embarrassment exactly. The slow realization that you already knew, somewhere, that the way you wired that callout was always going to end here. Temporary became permanent. And now it is a blocker.
A converged router is a strong opinion about a world that moved
My router spent a month learning which model to trust. Then one of them got silently updated, its accuracy fell off a cliff, and it kept sending work to the dead arm because three weeks ago that was the right call.
A conception-evidence matrix for solo inventors
Most solo inventors misunderstand first-to-file the same way: they think the clock starts when they had the idea. It doesn't. Under the AIA, the clock that matters is when you file.
Healthcare file-upload integrity with platform-native primitives
The reflex makes sense. PHI lands in your upload queue, compliance is breathing down your neck, and the nearest file-integrity library is one install away. I've been there. Three tabs open, comparing SDKs, before I stopped and asked the real question: what do I actually need?
Pending todos as a first-class dashboard surface
Velocity looks great until you realize your agent dashboard is a highlights reel. Invocations up, tokens flowing, latency down. Everything trending right. You feel like you know what's happening, until something slips through and you realize you didn't.
A reversible installer for your CLI config
Every CLI installer I've ever run leaves a question hanging: what exactly did it touch, and can I get back? I've been burned enough times (clobbered configs, mystery overwrites, a setup that "worked" until the moment I tried to undo it) that reversibility stopped being a nice-to-have. It became the first constraint I wrote down.
When a Salesforce deploy fails on permissions you already granted
The deploy succeeded. The data transfer failed. The error lied to me.
Scratch-org-first as a deploy discipline
The first time I pushed a half-shaped metadata manifest straight to a shared sandbox, I cost my team an afternoon. The org was dirty from a previous sprint, the error message made no sense, and rolling back took longer than the deploy itself. Expensive. And completely avoidable.
The Most Productive Builders I Know Look Unfocused
The most productive builders I know look unfocused. Their histories read like group projects: a healthcare parser one week, a drift detector the next, a compliance audit after that. Ask them what they do and there's a pause.
Your agents re-decide what they already know
I watched my routing agent send the same task to the same sub-agent for the forty-seventh time. "Summarize this PDF." Same shape, same answer, every time. On attempt forty-eight it stopped, thought hard, burned the tokens, and arrived at the exact route it had already arrived at forty-seven times before.
Your loop detector is measuring the wrong thing
It was 2am and my agent had burned 40k tokens reverting the same file four times. The logs scrolled, new patches, new reasoning, new diffs. It looked busy. It was getting nowhere.
Apache-2.0 is a two-way patent grant, and the second way can bite you
> Disclaimer: I am not a lawyer and this is not legal advice. This is a reading of what the license text plainly says. For any real IP decision, consult a qualified patent attorney.
The 30-second license check I run before every pip install
> Disclaimer: I am not a lawyer and this is not legal advice. This is a reading of what license texts plainly say. For any real IP decision, consult a qualified patent attorney.
Stop writing examples, start stating invariants
Every example test I write is drawn from my own imagination, which is the one place my blind spots are guaranteed not to be.
Test the outage where everything fails at once
I was proud of my fallback logic, and that pride is what nearly shipped the bug.
The race your single-threaded test will never find
The first time I counted, the number was wrong, and the wrongness is the whole story.
Your happy-path test never met a real user
When I write a test, I type something polite. A task that says summarize this document. Clean, short, exactly the kind of input I had in mind when I wrote the code, which is the problem. The distribution of real user input is not the distribution living in my head.
Mocks let your integration test pass for the wrong reason
My integration test passed run after run before I caught it lying.
Dispatch ・ ESSAY
Your Apex class has a sharing posture. You just haven't declared it.
I was reviewing a service class in a mature org. Clean code, well-tested, passing all the gates. Then someone asked: "Is this running with or without sharing?"
READ
Dispatch ・ ESSAY
Killing Secrets in Packaged Apps
There is a specific feeling when a security review comes back with "hardcoded credentials" in the findings. Not embarrassment exactly. The slow realization that you already knew, somewhere, that the way you wired that callout was always going to end here. Temporary became permanent. And now it is a blocker.
READ
Dispatch ・ ESSAY
A converged router is a strong opinion about a world that moved
My router spent a month learning which model to trust. Then one of them got silently updated, its accuracy fell off a cliff, and it kept sending work to the dead arm because three weeks ago that was the right call.
READ
Dispatch ・ ESSAY
A conception-evidence matrix for solo inventors
Most solo inventors misunderstand first-to-file the same way: they think the clock starts when they had the idea. It doesn't. Under the AIA, the clock that matters is when you file.
READ
Dispatch ・ ESSAY
Healthcare file-upload integrity with platform-native primitives
The reflex makes sense. PHI lands in your upload queue, compliance is breathing down your neck, and the nearest file-integrity library is one install away. I've been there. Three tabs open, comparing SDKs, before I stopped and asked the real question: what do I actually need?
READ
Dispatch ・ ESSAY
Pending todos as a first-class dashboard surface
Velocity looks great until you realize your agent dashboard is a highlights reel. Invocations up, tokens flowing, latency down. Everything trending right. You feel like you know what's happening, until something slips through and you realize you didn't.
READ
Dispatch ・ ESSAY
A reversible installer for your CLI config
Every CLI installer I've ever run leaves a question hanging: what exactly did it touch, and can I get back? I've been burned enough times (clobbered configs, mystery overwrites, a setup that "worked" until the moment I tried to undo it) that reversibility stopped being a nice-to-have. It became the first constraint I wrote down.
READ
Dispatch ・ ESSAY
When a Salesforce deploy fails on permissions you already granted
The deploy succeeded. The data transfer failed. The error lied to me.
READ
Dispatch ・ ESSAY
Scratch-org-first as a deploy discipline
The first time I pushed a half-shaped metadata manifest straight to a shared sandbox, I cost my team an afternoon. The org was dirty from a previous sprint, the error message made no sense, and rolling back took longer than the deploy itself. Expensive. And completely avoidable.
READ
Dispatch ・ DISPATCH
The Most Productive Builders I Know Look Unfocused
The most productive builders I know look unfocused. Their histories read like group projects: a healthcare parser one week, a drift detector the next, a compliance audit after that. Ask them what they do and there's a pause.
READ
Dispatch ・ ESSAY
Your agents re-decide what they already know
I watched my routing agent send the same task to the same sub-agent for the forty-seventh time. "Summarize this PDF." Same shape, same answer, every time. On attempt forty-eight it stopped, thought hard, burned the tokens, and arrived at the exact route it had already arrived at forty-seven times before.
READ
Dispatch ・ ESSAY
Your loop detector is measuring the wrong thing
It was 2am and my agent had burned 40k tokens reverting the same file four times. The logs scrolled, new patches, new reasoning, new diffs. It looked busy. It was getting nowhere.
READ
Dispatch ・ PRINCIPLE
Apache-2.0 is a two-way patent grant, and the second way can bite you
> Disclaimer: I am not a lawyer and this is not legal advice. This is a reading of what the license text plainly says. For any real IP decision, consult a qualified patent attorney.
READ
Dispatch ・ PRINCIPLE
The 30-second license check I run before every pip install
> Disclaimer: I am not a lawyer and this is not legal advice. This is a reading of what license texts plainly say. For any real IP decision, consult a qualified patent attorney.
READ
Dispatch ・ ESSAY
Stop writing examples, start stating invariants
Every example test I write is drawn from my own imagination, which is the one place my blind spots are guaranteed not to be.
READ
Dispatch ・ ESSAY
Test the outage where everything fails at once
I was proud of my fallback logic, and that pride is what nearly shipped the bug.
READ
Dispatch ・ ESSAY
The race your single-threaded test will never find
The first time I counted, the number was wrong, and the wrongness is the whole story.
READ
Dispatch ・ ESSAY
Your happy-path test never met a real user
When I write a test, I type something polite. A task that says summarize this document. Clean, short, exactly the kind of input I had in mind when I wrote the code, which is the problem. The distribution of real user input is not the distribution living in my head.
READ
Dispatch ・ ESSAY
Mocks let your integration test pass for the wrong reason
My integration test passed run after run before I caught it lying.
READ
