[jprokay13]

If you haven’t, adding in strict(er) linting rules is an easy win. Enforcing documentation for public methods is a great one imo.

The more you can do to tell the AI what you want via a “code-lint-test” loop, the better the results.

[crgwbr]

Honestly the same is true for human devs. As frustrating as strict linting can be for newer devs, it’s way less frustrating than having all the same issues pointed out in code review. That’s interesting because I’ve been finding that all sorts of stuff that’s good for AI is actually good for humans too, linting, fast easy to run tests, standardized code layouts, etc. Humans just have more ability to adapt to oddities at the moment, which leads to slack.

[jaggederest]

My rule of thumb is that if I get a nit, whitespace, or syntax preferences as a PR comment, that goes into the linter. Especially for systemic issues like e.g. not awaiting functions that return a promise, any kind of alphabetization, import styles, etc.

[jprokay13]

Yeah I find it pretty funny that so much of us (myself included) threw out strict documentation practices because “the code should be self documenting!” Now I want as much of it as I can get.