My lint rule caught its own test fixture
I wrote a guardrail to ban hardcoded config arrays, and the first thing it flagged was the bad example I'd written to test it. The rule was right. My file layout was wrong.
● AI-agent engineer · building in public
I wrote a guardrail to ban hardcoded config arrays, and the first thing it flagged was the bad example I'd written to test it. The rule was right. My file layout was wrong.
The most dangerous state for a production system isn't a known failure — it's no signal at all. When you inventory your surfaces and find that health checks,…
Filing a ticket creates the appearance of progress while nothing is actually owned, scheduled, or moving.
An LLM's attention is cheap and a human's is scarce. Spend the cheap one to protect the scarce one.
A single web platform that runs a clinic's whole day — check-in, a live provider queue, lightweight charting, telehealth, staff messaging, and billing — instead of a dozen disconnected legacy tools.
The orchestration layer that launches agent sessions, watches them for trouble — rate limits, context exhaustion, dead sessions — and recovers them automatically, using deterministic scanning instead of fragile notifications.
A kiosk and mobile intake flow where patients check themselves in — confirm demographics and insurance, sign policies, answer pre-visit questions — and drop straight into the live clinic queue.
Building agent systems inside a real business — or running a clinic and wondering what this could look like for you? That's exactly the conversation I want to have. No form, no funnel.