Are you more interested in posting things you are currently learning? Or do you want to show of your solution for a specific problem and see what other ppl think about it?
Lately I've been doing more of showing my solution but I love writing as I learn as well (I did that with my GraphQL article a while back and I loved it), but I sometimes feel anxious doing that or I don't want to add clutter amongst the already good resources on the topic, so I sometimes write on my wiki instead. As an example my own personal reference and "gotchas" for Go syntax, I did not feel it was worth an article because there's already A LOT of content covering its syntax.
I have a habit of not wanting to write an article on a topic if I already found good resources covering it, so a lot of the articles I write are "guides I wish I had", for topics I searched for quite a bit and could not find good resources on.
That is a really good tip! Thanks for your advice :)
I really think the same way as You... As long as there are enough posts out there I don't have to be the 100th one posting it. If there is no proper solution which i can find easily it's worth a try :)
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.