Notes on building the AI-native web.
Page 6 of 17
AI employees and your busiest week of the year
Peak is the strongest argument for automation and the worst time to deploy it. Both things are true.
Why your AI feature got slower and more expensive after launch
Nothing broke. The context grew, the retries stacked up, and the prompt accumulated instructions nobody removed.
What a useful AIEO report looks like
Not a traffic chart. Four sections that tell whoever reads it whether the work is landing and what to do next.
What QA looks like for an AI feature
You can’t assert an exact output, so the usual test suite doesn’t apply. What replaces it, and what stays the same.
Does above the fold still matter?
People scroll now, so the old rule is dead. What replaced it is stricter, not looser.
Working with a legacy system you can’t replace
Sometimes the old system stays, for reasons that are entirely valid. How to build around it without inheriting all of its constraints.
Shipping safely: flags, staged rollouts and the off switch
The ability to turn something off in ten seconds changes how much risk a release carries. It is cheap to build and rarely built.
Why your case studies don’t convince anyone
They read as advertising because they are structured as advertising. The fix is specificity that would be embarrassing to fake.
Should you block AI crawlers?
Publishers with paid content have a real case. If you are a business trying to be recommended, blocking is aiming at your own foot.
How AIEO and SEO actually differ
They share more than the consultancies selling both would like. The four places they genuinely diverge are the ones worth budgeting for.
AIEO: how to become the answer AI search gives
Search isn’t ten blue links anymore — it’s one synthesized answer. Here’s the playbook for being the brand that answer is built from.
Configuration and secrets, done simply
Most environment-specific outages are a setting, and most credential leaks are a file that should never have been committed. Both are cheap to prevent.