If you're going to correct a post someone puts their hardwork in making for others to learn and strengthen their understanding, you might as well correct it respectfully.
If you had perfect knowledge of this topic why didn't you write the post yourself??
Better still you might as well have answered the 20 more questions with no answers.
You don't have to have perfect knowledge to point out glaring mistakes. It's like seeing someone trying to nail something using a shoe instead of a hammer who says only someone who has been a master carpenter for 20 years is allowed to point out that a hammer is a better tool.
Hard work is a relative matter. For example, the fact that Docker uses the host kernel is in the documentation. It's better to provide the questions as-is and let people learn by doing the research (the questions themselves are good) rather than provide wrong/misleading answers.
Seems like you didn't read the part where I said you should correct respectfully
You're contradicting yourself saying "the questions themselves are good" when you literally called them "wrong", "bad interview question", "pointless".
If you feel a post is "wrong", "bad" or "pointless", there's nothing bad, its your view. But you should atleast correct respectfully if you're going to correct.
There's a difference between question and answer. One is pointless and another could be improved by asking it differently. Some of the answers are wrong, which is what I specifically said. The questions are ok as interview questions.
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.
If you're going to correct a post someone puts their hardwork in making for others to learn and strengthen their understanding, you might as well correct it respectfully.
If you had perfect knowledge of this topic why didn't you write the post yourself??
Better still you might as well have answered the 20 more questions with no answers.
You don't have to have perfect knowledge to point out glaring mistakes. It's like seeing someone trying to nail something using a shoe instead of a hammer who says only someone who has been a master carpenter for 20 years is allowed to point out that a hammer is a better tool.
Hard work is a relative matter. For example, the fact that Docker uses the host kernel is in the documentation. It's better to provide the questions as-is and let people learn by doing the research (the questions themselves are good) rather than provide wrong/misleading answers.
Seems like you didn't read the part where I said you should correct respectfully
You're contradicting yourself saying "the questions themselves are good" when you literally called them "wrong", "bad interview question", "pointless".
If you feel a post is "wrong", "bad" or "pointless", there's nothing bad, its your view. But you should atleast correct respectfully if you're going to correct.
There's a difference between question and answer. One is pointless and another could be improved by asking it differently. Some of the answers are wrong, which is what I specifically said. The questions are ok as interview questions.