Lint used to be for making code readable and consistent. Now it's an enforceable contract between you and your coding agent, and that makes it more important, not less.

2 points•willio58•10 days ago•4 comments•

4 comments

cscmsg10 days ago
A lint rule is only enforceable if the agent can't edit the rule. Prompt files are guidance because the model can ignore them. A config file is just another file in the repo and an agent can find ways to bypass that. I've seen my agent code around it or quietly loosen the config instead of fixing the code.

My solution was putting the hook and lint configuration where the agent can't write to it. That was more effort to set up, but it seems to work.

willio5810 days ago
Great consideration to make, those rule sets should absolutely require at least a confirmation from a human to change.
prologic10 days ago
Because consistency is still considered a quality rubric ?
willio5810 days ago
Absolutely, I could touch on that in the article more.

Read the full thread on Hacker News →

Related stories