Menu

1 / 3

8 Type Checkers and Linters Fast Enough to Run After Every Coding-Agent Turn

DEV Community: productivity·Gabriel Anhaia·10 days ago
#GZDUSbB5
#devtoproductivity#devto#dev#args#turn
Reading 0:00
15s threshold

Book: Decoupled PHP — Clean and Hexagonal Architecture for Applications That Outlive the Framework

Also by me: Thinking in Go (2-book series) — Complete Guide to Go Programming + Hexagonal Architecture in Go

My project: Hermes IDE | GitHub — an IDE for developers who ship with Claude Code and other AI coding tools

Me: xgabriel.com | GitHub

Twelve turns in, the agent reports success. You run the type checker and the terminal fills with errors, and now you are reading one diff that twelve turns wrote, trying to work out which of them broke the build.

Nobody runs the full CI after every turn. It's too slow, so the usual habit is to run nothing until the end. There is a middle ground: checkers that only redo the work a small change requires, because they cache what they already checked.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.