Ryan Zidago's Blog

I realised this week that documentation next to the code can explain more than what a module or function does.

Code-review agents should provide evidence for actionable findings whenever possible.

Problem I ran into a problem at work that I suspect will become increasingly common as products allow end users to write and save their own prompts.

In AI coding agents need software engineering guardrails, I made the case for why deterministic guardrails matter.

A test should explain itself.

Introduction In the previous article, I argued that deterministic guardrails are a better place for repeatable engineering policies than an AI agent's context window.

Problem LLMs cannot reliably remember every rule in your codebase: your coding style guide how to write a database query returning multiple records in a deterministic order add type specs to functions soft deleting a record instead of hard deleting it etc…

TL;DR Copying deps and _build is the obvious first optimization.

A customer wanted a visual dashboard builder (where you click buttons and create your own dashboard).

AI agents are becoming part of the development workflow, and they're only as good as the feedback your codebase gives them.