Beekey Cheung is a software engineer with a large amount of enthusiasm for economics and a passion for education. He loves mentoring other programmers and is currently building an application to te...
I agree about the need to test technical and inter-personal skills, which is why I described using an open ended architecture/design problem to do so.
I disagree that a code review is as good. Discussing how code should be structured and the trade offs of various decisions is more representative of technical skill than catching style errors.
I don't agree that code review is simply about catching style errors: that's what linters and tools like Prettier automate for you. Amongst other things code review should definitely be looking at how coding decisions conform to architecture/design goals.
We at least both agree that using real-world scenarios is a better approach than personality tests and abstract code problems :)
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 agree about the need to test technical and inter-personal skills, which is why I described using an open ended architecture/design problem to do so.
I disagree that a code review is as good. Discussing how code should be structured and the trade offs of various decisions is more representative of technical skill than catching style errors.
I don't agree that code review is simply about catching style errors: that's what linters and tools like Prettier automate for you. Amongst other things code review should definitely be looking at how coding decisions conform to architecture/design goals.
We at least both agree that using real-world scenarios is a better approach than personality tests and abstract code problems :)