🚀 Feature: Blog post on shared linter configs

### Feature Request Checklist - [x] I have [searched for related issues](https://github.com/JoshuaKGoldberg/dot-com/issues?q=is%3Aissue) and found none that matched my issue. ### Overview I started writing this sub-section in #420 but took it out because it doesn't really serve a strong need in that post: ```md #### Downplaying Shared Configs Speaking of `eslint-config-airbnb`: I don't consider shared _configs_ to be as important a part of a linter's ecosystem as in the past. Shared _plugins_ are of course perpetually essential for providing new rules, language support, and so on. I think shared configs like [`eslint-config-airbnb`](https://www.npmjs.com/package/eslint-config-airbnb), [`xo`](https://github.com/xojs/xo), and [`eslint-config-standard`](https://github.com/standard/eslint-config-standard) were mostly popular early on because: - They provided many off-by-default _formatting_ rules that were not yet available in Prettier - They additionally provided many rules that weren't yet in the recommended configs in ESLint and later typescript-eslint - They could wholly manage the ESLint configuration for most projects, since ESLint's ecosystem wasn't so mature that most frameworks had dedicated plugins yet These days, I think those benefits are significantly lessened: - Formatters like Prettier are now the de facto standard for _formatting_ rules - ESLint and typescript-eslint have put a lot of work into making their preset configs comprehensive and useful - ESLint's plugin ecosystem is so rich that most projects would benefit from customizing their configs There is still some use in shared _configs_ for grouping collections of useful rules. I think companies in particular benefit from providing pre-made _"this helps us"_ configs for their projects. But for any arbitrary new project, I don't think they're as useful as they used to be. They obfuscate how the linter actually works and add a layer of tooling you have to learn on top of the linter. If I wrote a linter, I would document recommendations of when to use preset configs. The documentation would suggest using them if you have an organizational link to the creator, such as being in the same company. It would recommend against using them if you're just getting started linting. ``` ### Additional Info More nuance needed. Also more research too. This type of opinion is one that would get a lot of backlash from folks who work on those things (e.g. neostandard). 💖