Hacker News Reader

With IntelliJ, spellchecker + linter + static analysis + duplicate code detection + etc = basic quality as opt out feature

VS Code and other setups make those opt in.

Meaning, when you see a bunch of typos and really poorly written code you know it is from one of the DIY setup people.

So then you have to move all those checks to the next stages like SCM hooks and CI.

View on HN

The flip side of this, the only times I've run into projects without external build tools, protective githooks or even .editorconfig, it was set up by an JetBrains family dev using the IDE as part of the build process.

Having to start a heavy, proprietary IDE to build code and other assets is a royal pain in the hole.

Exactly. And since you can't force people to setup IDE properly, automatically enforce them with CI.

Reply on news.ycombinator.com