Holyā¦ Justā¦ Wow. Lol
I had ignored this thread when it began, but for some reason tonight I decided to read it. All of it. Canāt decide if I regret that or not, butā¦ Lol
I agree that the documentation needs help. I donāt say that because it frustrates me (though at times, it has), but rather I say that because the frustration of others is evident in their posts and language. Most frustrating is that apparently the devs did not have the same CS professor that I did (not surprising since Iām pretty sure they are in a different country). On day 1 of CS121 she said āwhen you write your documentation, pretend you are explaining to your grandmother how to use your softwareā. Even though Iām not a full-time developer by trade, for the handful of things I have written, and for the internal technical documentation I author, that sentiment has always stuck with me.
Someone mentioned videos - I already took up that mantle. There are lots and lots of āentertainmentā YouTube channels about smart home stuff, or channels about ālook at this neat thing I made my house do, hereās a 20,000 foot view of how I did it (and then never actually showing the code or the automation or the config)ā, so I started my own channel. I have over 50 technical videos published, and I show all the code and explain everything as best as I can. If someone is looking for how to do something, give it a look. Itās clearly not ALL there, but thereās a good amount, and I add to it regularly. I do also take requests, so thereās that.
With regards to the āregularsā giving up on helping the noobs, I find the problem to be the same in nearly every case, regardless the topic.
The āold guardā gives answers. The new hotshots that think they know better and like to have the loudest voice in the room chime in, loudly, oft with inferior (or flat out incorrect) information. The old guard gets tired of trying to not only educate the new users, but also tires of having to ādefendā themselves from the never ending barrage of nonsense from the mouthy ones, so they just give up and stop participating. This is not only a great loss to whatever community it happens to, but it also ensures that future generations of participants will be much worse off than their predecessors since now they are only able to gather their information from the lesser-knowledgeable (but louder) cohort. The cycle repeats, and you end up with idiocracy being a documentary.
Overall, this has been a very interesting read. The thought that keep reverberating in my head as I read a lot of this is that there was a post some time ago around new users and struggles and barriers to larger market acceptance/penetration, and I remarked about how the documentation and support structure wasnāt what the āaverage Joeā would require, and I recall being poo-pooād, with the sentiment basically boiling down to something akin to āthis is a project by nerds, for nerdsā. I think. That was many moons (and many whiskeys) ago.