Amazing piece. Should be required reading for all interviewers.
I think it was DHH who wrote that he considers himself to be a "software writer". I.e., it is his job to write his intentions, through code, clearly and unambiguously to be understood by others.
If we're honest with ourselves, unless we're writing seriously low-level code, this is what most of us do. Those who believe otherwise should come off of their high-horses and learn that people and not code is the most important part of their work. Their interviewing approaches should reflect this.
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.
Amazing piece. Should be required reading for all interviewers.
I think it was DHH who wrote that he considers himself to be a "software writer". I.e., it is his job to write his intentions, through code, clearly and unambiguously to be understood by others.
If we're honest with ourselves, unless we're writing seriously low-level code, this is what most of us do. Those who believe otherwise should come off of their high-horses and learn that people and not code is the most important part of their work. Their interviewing approaches should reflect this.