> Spam from junior devs who started a blog so to build a name for themselves.
I often find this is the most useful category out of the 5 you listed. Junior devs writing something like "How to setup webpack" often explain things in plain words and just spell out how to get the thing working. There's humility to the post like "I don't know what all these options do, but this is what worked for me".
I find that a lot more honest/useful than say category 5 there where I have no idea if what they're talking about will actually work for me or how much effort it's going to take to integrate because the assumption there is you have big teams who can spend all their time maintaining these tools.
I am completely baffled by this comment. You're saying the _juniors_ are creating overly complicated modern frameworks, or are the ones pushing it?? It's clearly the opposite in my opinion. Big companies/teams are releasing tools that may work well for their scale but are overkill for most, and they're championing them as good solutions for everybody, and juniors are the force working in the opposite direction (trying to simplify/untangle all this complexity, they don't have the experience to recognize if it's overkill. They also want to get hired at all the companies that use these tools so they have to learn it).
While I do think that most of the useful pages either come from juniors or from someone promoting their own product, I think there are a ton of bad pages from juniors that have outright incorrect or dangerous information, too. So it can be hard to tell what advice to use and what not to if you're at a level that you're asking the question in the first place.
I often find this is the most useful category out of the 5 you listed. Junior devs writing something like "How to setup webpack" often explain things in plain words and just spell out how to get the thing working. There's humility to the post like "I don't know what all these options do, but this is what worked for me".
I find that a lot more honest/useful than say category 5 there where I have no idea if what they're talking about will actually work for me or how much effort it's going to take to integrate because the assumption there is you have big teams who can spend all their time maintaining these tools.