The Slack notification that would have posted 200 times on day one
How I learned that notification products have two failure modes: the day-one flood and the ongoing noise. A ConnectWise-to-Slack bridge built around both.
Read →BLOG · PAGE 6
Page 6
The cert that expired at midnight and nobody knew until 9 AM
A production TLS cert expired while everyone was asleep. Nine hours of quiet downtime before the on-call engineer caught it. This is why I built CertWatch.
Read →The AWS bill that tripled (and how I didn't notice for six days)
How an EC2 instance I forgot to terminate ran for six days before I noticed — and the tool I built to make sure it doesn't happen again.
Read →The AI chief of staff is a job title waiting to be invented
Founders pay $8k/month for a human EA who does scheduling and email triage. The same workflow runs on $25 of Claude API calls. Here's what's missing.
Read →The agent wrote the course
I used an overnight autonomous agent to build a course about building overnight autonomous agents. The irony is useful.
Read →The fallback that wasn't
A one-line bug in the apply pipeline: Firebase was labeled the primary source for HN listings, raw_context was the fallback. When primary returned empty, fallback never fired.
Read →A live dashboard for an overnight coding agent
Autonomous agents are finally good enough to run unattended. The missing piece isn't capability — it's seeing what they're doing. Here's a ~120-line dashboard that streams an agent's progress and texts me only when it matters.
Read →The other half of noise: digest mode for notification products
Quiet bootstrap fixes the day-one flood. Digest mode fixes the *ongoing* flood. A notification product has two failure modes; both have to be paid attention to, or the product feels broken.
Read →The missing converter: how a single missing file blocked six nights of output
An overnight pipeline drafted a blog post six nights in a row and shipped zero of them. The blocker was two files that didn't exist on the host.
Read →Quiet bootstrap: the day-one experience of a notification product
A notification product whose first tick is loud doesn't get a second tick. Build the silent-snapshot path before you build the alerting path.
Read →Whitelist beats blacklist when the input variety is unbounded
A title filter that keeps falling behind doesn't need more reject tokens. It needs to flip into a whitelist.
Read →When the URL outlives the job
Why fetching JD bodies at ingest beats lazy-fetching at apply time, learned 242 dead URLs at a time.
Read →How to keep an LLM from sounding like an LLM (on a CV)
Specific bans beat vague style guidance. Prompt rules from the EverCV renderer.
Read →The smoke test caught a real prod bug on the first run
I wrote a post-deploy smoke test for my SaaS the way you're supposed to: small, focused, fail-the-deploy-if-the-URL-doesn't-serve-what-you-just-uploaded. Then I ran it against production. The test failed. The bug had been live for four days.
Read →