this post was submitted on 26 Jun 2023
45 points (88.1% liked)
Experienced Devs
3981 readers
1 users here now
A community for discussion amongst professional software developers.
Posts should be relevant to those well into their careers.
For those looking to break into the industry, are hustling for their first job, or have just started their career and are looking for advice, check out:
- Logo base by Delapouite under CC BY 3.0 with modifications to add a gradient
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Recognizing class/functions/basic functions is not a criterion for a good engineer, it's a criterion for any developer. Not saying it's bad to check that... In fact yes, quiet a bit bad. Nowadays there is google to help you understand how to use find; you don't need to know by heart how it works, and maybe you are a good engineer that can find how to use that with
man
or internet in a short time.Ask him also a relatively hard problem (easy to understand though). Not something to code particularly, but a problem to see how he process it, how he's thinking about it, what will he look for in the project, what questions will he ask you about the problem.
It will not take more than 10-15minutes, and you can easily pick who will be able to Engineer a solution (=> think about it, how it works, how it interacts) from people that can output code that works but need someone else to give them detailed instructions to be able to work.
This is exactly what I am saying, you don't need a 30+h coding challenge. Good questions to understand theoretical understanding, style, practical experience, software design, and few quick technical assessment tests to confirm they didn't lie, over few key basic tasks, those that one should know without googling, and that can show coding style and quality.
I believe 30+h of unpaid work are unfair just to prove me something I can understand with less effort on their side