The insight here should be that none of the above is about studying for whiteboard interviews.
It is all about demonstrating and effectively communicating an understanding of the theoretical and practical aspects of a software engineering problem.
I would recommend never practicing for whiteboard interviews - it is a complete waste of time.
Instead, invest in writing design documents and presenting them for critical review.
Those skills are what the interview is trying to evaluate.
Likewise competitive coding practices poor engineering and should be avoided.
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.
The insight here should be that none of the above is about studying for whiteboard interviews.
It is all about demonstrating and effectively communicating an understanding of the theoretical and practical aspects of a software engineering problem.
I would recommend never practicing for whiteboard interviews - it is a complete waste of time.
Instead, invest in writing design documents and presenting them for critical review.
Those skills are what the interview is trying to evaluate.
Likewise competitive coding practices poor engineering and should be avoided.