|
|
|
|
|
by sarusso
1571 days ago
|
|
I think we are just talking about two different things, and that you have in mind "coders" and "developers", not software engineers or data scientists. But the OP was talking about the latter, not the first, where I can to some extent agree with you. I saw it many times: javascript kids or self-taught backend Python "engineers" falling extremely short when it came to scalability, algorithmic complexity, or just abstracting concepts. Similarly, I saw several self-claimed "data scientists" not even knowing what a non gaussian error distribution means. Not knowing this stuff jeopardise your work and the projects you are working in. Then, if you are telling me that your interview process should spot these shortcomings at the same level a university degree can, then to me this sounds a bit unrealistic. However, if you need someone that can write code to pass the unit-tests that some one else wrote without taking any architectural decision, than OK I can agree with you, but it does not sound much of an appealing career path IMO. |
|