Another IndieWeb Peeve

I have a few guides/tutorials saved in my drafts. Most of them start with a tangentially related preamble about this subject. I thought it'd be smart to just trim the fat; cut straight to the point for those posts, and share the preamble here separately for those who really care.

I've seen a lot of experienced webmasters complain about how newer webmasters shouldn't do [insert thing here], but they don't explain why said thing is bad, or don't say what you should be doing instead. This isn't exclusive to the indieweb community by any means, but it's still something that I see a lot.

Telling your kid to stop eating so much candy is not the same as telling them to eat their vegetables. If you tell your kid to stop eating candy, they might just start eating chips instead. Some people require clearer instructions. I think that older and more experienced webdevs should set an example for those who are younger or less experienced.

If you want someone to start doing something, show them how to do it. If someone doesn't understand why, then explain it to them. Don't assume that just because something is "common sense" to you, that means everyone else does/should know it. Will this work with everyone? No, but that doesn't mean that it won't help anybody. It's at least more helpful than whining about "poser webcore kids coming from TikTok/Twitter" or whatever the fuck.

As a sidenote, I'm sorry how ranty/opinionated my posts have been as of late. I guess a part of me feels like this is a safe place to vent, since I'm basically forced to suppress any negative emotions/opinions I have when I'm offline. I'm not really sure what my "audience" (if they even exist) expects of me, but I can't imagine reading my frustrated ramblings is all that fun. I promise I'll try to get some more positive/constructive stuff out soon!