[tcoff91]

This is why you need to be generating more linter rules instead of just having things be in markdown files.

I had never written an eslint rule until i started having agents pump them out for me and now I've encoded a bunch of important rules as lint rules that will fail CI if violated.

[deadbabe]

Who lints the linters

[jckahn]

Linter linters, obviously

[tcoff91]

It's linters all the way down

[hansmayer]

A linter won't prevent your idiot LLM from going bonkers and suddenly switching to GQL instead of REST just for that one endpoint, because it confabulated something or putting your stripe secret into your react frontend - all cases of slop I've seen happen.

[tcoff91]

That's why we still do code review. The linter rules is just about lowering the amount of mistakes you have to catch at code review time.

[hansmayer]

> The linter rules is just about lowering the amount of mistakes you have to catch at code review time.

Aren't they, in the modern context, mostly used for code formatting and such? I don't recall anyone using them today for "catching errors". Unless you count code formatting style violations as 'errors'.

[tcoff91]

Maybe in whatever language ecosystem you are in, but in the javsacript world most projects have tons of eslint rules that are specifically designed to stop bugs.

Like for instance there are tons of eslint rules to make sure you aren't breaking the rules of react, like having missing dependencies in a useEffect dependencies array, or calling a react hook conditionally.