Series
Reading paths
Ordered, multi-part arcs. Standalone posts live on the home page.
Building a coding agent
- An agent loop is a while loop with good manners draft
- Your app calls a model in more places than you think draft
- Your LLM provider is state, not architecture
- Subscription OAuth is the hard half of multi-provider auth draft
- The model never reads your handler
- Most approval prompts should never render
- The whole permission model is one folder draft
- Error messages are prompt engineering now draft
- Your agent is a protocol, not an app draft
Effect in practice
- Where exceptions are allowed to exist
- Make the compiler tell your ids apart: a guide to branded types
- The model will find the fourth shape: property-based testing with fast-check
Effect, from zero
- Effect from zero: the beginner's guide I wanted
- Effect, in full: services, layers, errors, and the concurrency toolkit
- AI applications are Effect-shaped
How an agent remembers
- The transcript is the memory draft
- The context window is a resource you engineer, not a buffer you fill draft
- Sub-agent transcripts are capital, not exhaust
- Zero-config storage: Postgres is an option, not a prerequisite draft
Observing an agent
- Observability is built in; where it goes is a layer draft
- Name spans for humans, query them by attribute draft
- Your eval has no database; the trace is the dataset draft