I learned about that from @carverofchoice, at least the BBCode syntax Discourse uses for it (you can also get to it by selecting Hide Details from the in the composer), but at times I’ve used the HTML syntax for it when the stuff I want to put inside causes rendering errors in the preview. It’s a cool feature.
I hope I’m not usually blathering too much! 
I did too. Actually you beat me to saying it, myself. I honestly considered saying that exact thing in my post as a joke, and then decided not to, and I’m glad I didn’t because it was even funnier coming from you. 
I enjoy a good joke about my loquaciousness. And don’t mind good humored jokes “at my expense” from people who I know are just being playful and generally like me and aren’t being intentionally malicious.
I’m glad someone said it. My first instinct was to reply “I agree” and then I decided I’d just say I’m actually good at it when I WANT TO BE. I just don’t want to be if it’s not for something that will make me money or save me time.
Hence why I’d do it for things I find myself repeating a lot, such as why someone is having connectivity issues vs how to use X feature. 
I can…having to keep doing something yourself because you don’t want to write the documentation for it. Ugh…I didn’t have enough hours in a day to keep doing everything myself especially when my work has more than doubled every year for the last 3 years in a row and there is only so much automating I can do for some of it. I pushed off writing the documentation for so long that I nearly burned myself out. Finally had to just give in and get through the drudgery of writing documentation just so someone could help out with 80% of my work. But yes, only in that case is not writing documentation worse than writing it. 
But sometimes it’s worth the investment.
That’s actually one thing I don’t miss about QA Testing…lots of documentation. I enjoy finding errors and figuring out solutions and workarounds, etc…writing reports and documentation is the boring part. I kind of like doing it for Wyze because I can tell them about issues in the way I want to without having to do it so formally in particular formats, etc.
Yeah, I have started to try to do that more out of courtesy to my TLDR; friends.
Oh the importance of the documentation is 100% critical, no disagreement there. I just don’t want to be the one writing it
I actually make very good, thorough, detailed diagrams for the networks I design/deliver, I have no problem with that (it does get tedious, but still more engaging than typing a bunch of words). That saves me a ton of time and headache in the long run, support teams rarely have to call me since it is laid out clearly for them. Time very well spent.
What really drives me nuts is when you show someone how to do something once, maybe twice, then they ask you again the third time. That’s when I redirect them to the documentation (that someone else wrote).
Only sometimes, just kidding!
I’m glad you didn’t get offended as sometimes I can get a bit insensitive, it’s my cultural background 
I’ve illustrated more than a few user manuals in my four decades as graphic designer and I kind of enjoyed it even though I didn’t specialize in technical illustration. You both are correct though, I wouldn’t want to write one either.
I wish I had that reason. I acquired a sarcasm gene from my parents. That or slight Tourette’s syndrome. 
I also wrote many tech docs. If is fun while working but not for fun without working.
Say something cultural. 
You first
Ô (effete) Ca-na-da
Improved itself to-day! 
(Celebration may be premature. Who knows into what these creatures may transmogrify.)
Meet you at Timmies for a double double
No Tim Horton’s down here.
You weren’t invited 
Thanks a lot. Besides, the drive is too far. 
There are quite a few in New York State 