CONTENT EXPERTISE · THE ANTI-SLOP STANDARD

I know content. It never ships as slop.

The problem was never too few AI tools — it was that nobody had connected them into one pipeline that produces work worth publishing, instead of slop. Before I engineered content, I made it by hand for years: neuroscience videos, courses, essays. That taste is the part automation can't fake, and it's what I build into every system I ship.

+
25

CLOUDFLARE WORKERS
IN PRODUCTION

+
11

LIVE PRODUCTS USING
AUTOMATIONS I BUILT

244

NODES IN MY LARGEST
n8n PRODUCTION WORKFLOW

60

HOURS SAVED MONTHLY
BY A TYPICAL BUILD

THE METHOD

Understand → Encode → Gate → Tune.

01

Understand

Learn the domain, the audience, and what “good” looks like here — before a single word is generated.

02

Encode

Turn that judgment into the system: prompts, guardrails, source hierarchies, and structure the model has to follow.

03

Gate

Nothing publishes unvetted — fact-checks, quality gates, and a human veto where it earns its place.

04

Tune

Watch what ships, measure what lands, and tighten the system so it compounds instead of drifting.

NON-NEGOTIABLES

Three things I won't trade away.

Taste

Knowing the difference between publishable and passable. It doesn't come from a model — it comes from years of making the work by hand.

Standards

Cited sources, real structure, no hallucinated stats. If it wouldn't survive an editor, it doesn't ship.

Performance

Content that earns attention and gets cited — not volume for a dashboard.