Skip to content

#architecture

4 posts on this topic, newest first. all tags →

TypeSafe's Jev in production: thresholds and two bugs

Jev is a decision model: it picks, rates and judges, and writes nothing. I wired it into ten places on this site and measured what it cost. The model was the easy part. The hard part was choosing a threshold for each decision, giving moderation a token budget nothing else can spend, and finding out the counter meant to cap the whole thing had never counted anything. These are the eleven thresholds, the two bugs, and the rule I kept.

llmai-agentsarchitecture+2 more
19 min read24 min listen

Just use Postgres, until it actually hurts

The queue, the cache, the search index, the vector store, the job scheduler and the analytics table for a product with 40,000 daily users all live in one Postgres 18 instance, and that was the plan from the start. Here's what each piece looks like, what it costs, and the three specific signals that would make me move one of them out.

postgresqlarchitecturedatabase+1 more
8 min read10 min listen

The code nobody read

A client asked me to take over a product two people and an agent had built in four months. It worked. It was sixty thousand lines, no human had read most of them, and the first bug took a week to find because there was nobody to ask. This is what inheriting vibe coded software is like, and what I'd have done differently in those four months.

ai-agentsengineering-practicemaintenance+1 more
9 min read12 min listen

Context engineering is cache management

A million token context window didn't make the long-running agent problem go away, it just moved it. The model still forgets what you told it an hour ago, only now it forgets after paying for it forty times. The techniques that work, compaction, retrieval, memory files, are the same ones we use to manage a cache.

llmai-agentsarchitecture+1 more
8 min read10 min listen