Skip to content

#engineering-practice

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

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

Hiring engineers when everyone has an agent

Our take-home test stopped working in the autumn. Every submission was clean, tested and about the same as the others, because every candidate had used the same tools and the test was measuring the tools. We rebuilt the process around what still tells candidates apart, what they do with an agent's output. This is the loop, the exercise and what it found.

hiringengineering-practiceai-agents+1 more
10 min read13 min listen

How we review pull requests that an agent wrote

By spring an agent was opening more than half of the pull requests on our main service. Our review process was built for people who understood their own diff, and it broke in specific ways. 'Read more carefully' didn't fix it. Changing what a PR has to contain before a person looks at it did.

code-reviewai-agentsengineering-practice+1 more
9 min read11 min listen