If you find an answer on Stack Overflow, it's ripe to be re-described in the form of a simple blog post.
Dunno, to me that always felt like a form of plagiarism, at least unless there's a lot of added information. It's one thing to find a SO answer, spend an hour or two researching why it works, then writing on those findings. But simply re-phrasing it, adding nothing new, and writing an article on it is really just selling someone else's effort as your own.
EDIT: There's also the obvious option of linking to the original answer, copying the relevant code, and just pointing out what makes it interesting and ask for a discussion.
It is very helpful to write simple explanations of concepts — just in case someone comes along needing what you're describing.
This doesn't exactly describe what I'm talking about, but it's related:
If you find an answer on Stack Overflow, it's ripe to be re-described in the form of a simple blog post.
Here is an example:
How to sort an array in JavaScript
This is how you sort an array in JS.
Happy coding!
I challenge anyone stopping by to read this to create a simple post like this. You will help someone out there in the future, I guarantee it.
Dunno, to me that always felt like a form of plagiarism, at least unless there's a lot of added information. It's one thing to find a SO answer, spend an hour or two researching why it works, then writing on those findings. But simply re-phrasing it, adding nothing new, and writing an article on it is really just selling someone else's effort as your own.
EDIT: There's also the obvious option of linking to the original answer, copying the relevant code, and just pointing out what makes it interesting and ask for a discussion.
Hehe, luv the "Sunshine" quote :D
One of my favourite movies ever, if for no other reasons than that single sentence ... ^_^
("Kaneda, what do you see?")