I think conducting any kind of test during an interview is a waste of time.
I think conducting any kind of test during an interview is a waste of time. If someone comes in with a resume that clearly demonstrates years of relevant experience, a Github account with examples of things they've worked on, and if they can talk intelligently about the problems I'm trying to solve, that's all I really need to know about their skills. I couldn't care less how someone thinks. What I want to know is do they have experience writing code and more importantly, are they the sort of person I would enjoy working with. Both of these questions can be answered in more effective ways than a test or whiteboard question.
Posted by innocentoldguy on May 5, 2015, 7:28 AM
Tags
Related issues
- That isn't really relevant for the tool starting the container.
- Why is there no link to the source?
- Something I wonder about in this domain is if this is the fault of the language.
- Namespace pollution is an annoying problem in Rust.
- Currently, no language ports of Timefold Solver are planned.
- I agree with you, almost all .NET code I write is within the .NET framework, yet when I look at C# repos, it's disheartening to see so ma...
Raise real-world problems, find people facing the same issue, and discuss solutions.6,500 issues0 comments
hackernews (Software)
That isn't really relevant for the tool starting the container.
Why is there no link to the source?
Something I wonder about in this domain is if this is the fault of the language.
Namespace pollution is an annoying problem in Rust.
Currently, no language ports of Timefold Solver are planned.
I agree with you, almost all .NET code I write is within the .NET framework, yet when I look at C# repos, it's disheartening to see so ma...
Why is there no simple workaround for this?
I have been using https://github.com/jacktasia/dumb-jump to quickly jump to definitions.
I think conducting any kind of test during an interview is a waste of time.
I think conducting any kind of test during an interview is a waste of time. If someone comes in with a resume that clearly demonstrates years of relevant experience, a Github account with examples of things they've worked on, and if they can talk intelligently about the problems I'm trying to solve, that's all I really need to know about their skills. I couldn't care less how someone thinks. What I want to know is do they have experience writing code and more importantly, are they the sort of person I would enjoy working with. Both of these questions can be answered in more effective ways than a test or whiteboard question.
Comments (0)
No comments yet. Start the discussion.