Blog
- What one person actually built
- Turning a customer's API spec into a published docs site
- Automating multichannel marketing
- Surgical fixes in agentic pipelines
- A long job and a hot reload
- The contract an agentic job runs on
- Why I switched from a polylingual stack
- From rules to reasoning
- A team of agents in visible panes
- Context as files
- Assume the model call fails
- Files are how it perceives
- The expensive way to call the same model
- The unit that hides the tokens
- The hotfix lane: skip the process, not the safety
- A website chat you can trust to answer
- A CRM activity log written for an LLM to read
- The accept button collects training data
- Email without campaigns or segments
- What a page needs and how it looks are separate stages
- Every route configures itself
- The Swiss Cheese Model
- My errors come with fixes attached
- Access to one app
- Where deleted things go
- A single prompt cannot build a website
- Plop in a key
- One invite, sent to seated
- One domain, connected
- Three test suites that never overlap
- War Story: Failing Test Suites
- One page, two visits
- Where one permission lives
- Name it right the first time
- The localization I skipped
- One push, start to finish
- GCP vs Azure, from someone who shipped both
- Permissions, borrowed from Amazon and Google
- One event for slow and expensive
- One request, start to finish
- No test, no endpoint
- Where the code comes from
- We rolled our own Next
- Forms that cannot drift
- One block model, two surfaces
- The builder came first
- Postgres after six years of Firebase
- Analytics feeds the AI
- The stack came before the product
- The Business Case for Giant Context