Essays
Where AI, power and buildings meet.
Polite failures
The dashboard was green. The room wasn’t.
AI agents rarely fail loudly. The expensive failures arrive on time and say everything is fine. Run the audit.
FLEET STATUS · 03:50
4 of 6 healthy · as reported
Check or go
Where should the human actually be?
Ten things an AI assistant might do. Decide which ones need you. Most people put themselves in the loop far too often.
Rename and tidy files in a project folder.
Would you let your AI do this on its own, or make it check with you first?
My rule: Reputation or money: check. Anything that can’t be undone: check. Everything else: go.
Ten decisions. Let’s see where you’d put yourself in the loop.
Power, mapped
The site is chosen by the power plant. The zoning follows the substation.
Taiwan’s north stopped connecting large data centres. Tap a fact to see where it happens.
Schematic, not to scale. Blue lines show supply sent north from central and southern Taiwan. Sources are listed in the essay.
Two power numbers
The application is an option. The connection is the asset.
In Taiwan, data centres have asked for fifteen times more power than is actually switched on. Underwrite the smaller number.
75 data-centre requests to Taipower as of 31 July 2026, against the contracted capacity of the four sites actually receiving power. Source: Taipei Times, 29 Aug 2026.
On the record
Six calls, with due dates.
I’d rather be specific and wrong than vague and safe. Each call says when to check it.
Calls I’m on record with
“On time” means I still hold the view. If I change my mind, the call stays here, marked.
Field manual
Eight rules for working with AI.
What running my own agents taught me, in a form you can use with a single chatbot on Monday.
Spec first.
Tap for whyProblem, constraints, definition of done. A vague request gets a confident, wrong answer.
The builder never grades its own work.
Tap for whyA second model, or a second pass with a different brief, checks the first.
Context is a budget.
Tap for whyAn agent that reads everything understands nothing. Give it what the task needs.
Put the off switch where work leaves.
Tap for whyGuard the point of publishing or paying, not the door the request came in through.
Prune memory on purpose.
Tap for whyWhat an agent remembers forever eventually misleads it.
Every new tool is a maintenance bill.
Tap for whyCount the upkeep before you celebrate the capability.
“Unverified” is a task.
Tap for whyNever let it sit as a status. Someone goes and confirms it.
Enforce rules in code.
Tap for whyA policy the system can ignore will eventually be ignored.
Frameworks I use
Three tools I reach for.
Pre-mortem
Assume the project already failed, then explain why.
Anti-goals
Decide what you refuse to become while you chase what you want.
Capital allocator or technician?
Before you fix it yourself, ask whether a system should fix it instead.