Code linters should check code style, not code correctness. I don't remember a single instance of a lint rule for correctness that accurately detected an issue, but I have seen countless instances of a linter recommendation introducing a bug or otherwise creating friction.
-
-
Trust the programmers heuristic over the linter’s heuristic until we can lint code correctness- then trust the linter.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I'm curious about your opinion on the current research applying Deep Learning to Source Code Do you think in the future linters and other developer tooling will be empowered by ML? Disclaimer: I definitely believe so, that's why I left
@google and joined@sourcedtech +#MLonCode -
Do you train adversarial networks to compare code structures?

- Show replies
New conversation -
-
-
Now think of using ML there instead, not to rely only on hard rules, not based on single deterministic examples, and able to match the given codebase style. Particularly when you think of style beyond tabs x spaces and more like idiomatic ways to write code in a given language.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.