I think there's an important distinction between presenting an opinion or experience and presenting a fact. I don't think there's anything wrong with someone writing a post about their experiences with language X or why they think framework Y is rubbish. But if the post is about how to correctly configure authentication in framework Y or how to query a database with language X then there's a huge amount more scope for spreading misinformation and the author needs to take responsibility for ensuring the facts presented are correct.
Totally make sense... I have seen and struggling to get developers start writing about their problem/offer solution because of fear that they might be wrong. I encourage them to not be afraid, there will always be an opportunity to correct a mistake if you share it and someone point it out :)
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 think there's an important distinction between presenting an opinion or experience and presenting a fact. I don't think there's anything wrong with someone writing a post about their experiences with language X or why they think framework Y is rubbish. But if the post is about how to correctly configure authentication in framework Y or how to query a database with language X then there's a huge amount more scope for spreading misinformation and the author needs to take responsibility for ensuring the facts presented are correct.
Totally make sense... I have seen and struggling to get developers start writing about their problem/offer solution because of fear that they might be wrong. I encourage them to not be afraid, there will always be an opportunity to correct a mistake if you share it and someone point it out :)