I have wrestled with the exact same question, and I've come to some revelations:
I don't know if the topic is actually well explained if I don't understand it. I can't be sure I understand it until I write it out. So I have to write a post about the topic to know whether it is well explained.
Each post reflects the background and assumptions of its author. Many times they assume knowledge I do not have, where I can write a new post to fill in.
Good knowledge is not necessarily widespread. If I find a piece of knowledge useful, I want to promote it, and one more post means a bit more chance that someone stumbles upon it. Link back to the original to help with search engine optimization too.
Combining the above two points, the design space for dev is HUGE, and there is still a large gap of intermediate knowledge applied to use cases, between introductory material and advanced design patterns. Well explained doesn't mean well understood. I need examples and I don't find them, so I have to write them.
Looking forward to your posts!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I have wrestled with the exact same question, and I've come to some revelations:
Looking forward to your posts!