Well that's because markdown is for documentation, and we all know programmers don't know how to write documentation.

You can be pretty technical/capable and still write that article (especially if you have technical expertise outside programming). I have never felt so seen.

I worked my way up from arduino -> RasPi -> Debian -> Self hosting quite a few things. I'm very much a hobbyist/novice, but I'm used to learning. It is so hard to read some documentation and understand what something even does sometimes. This goes double for incredibly useful tools for monitoring/implementing other tools. Like I swear I read the kubernetes descriptions 30x before I realized what in the hell it actually does, and now I'm probably about to break my entire home network with it because I think it's cool as hell.

Also, to your comment specifically: I can get sensors on PCBs I personally made collecting data, throwing it through my own MQTT broker, hosting a dashboard etc, all at a remote site across state lines. I have no idea wtf markdown is. I use yaml for HA stuff with the ESPs, but I don't know why markdown is a thing and it's not just python.

And I am 1000% sure there is a very good reason for 98% of this. But yes I found this article hilarious. In my personal circle of hell all nouns end in "-ly".

understands how to write footnotes

x

The footnotes link to the list instead of the actual footnotes. I was quite confused.