I honestly don’t think that doing these cool things improves your odds of getting hired. Junior Devs don’t really touch these parts of a platform, let alone lead development on them from scratch.
A valuable engineer, to me, is someone who writes clean, maintainable code and follows common patterns. That’s also something which has to be learned by trial and error to actually see the value of.
Sure, look at their personal projects. I’m just saying the maintainability and quality of the code and speed of iteration is more of the point than how impressive the math is behind an ML algorithm. I’ve just seen a lot of ML engineers/data scientists who really suck at writing maintainable code
“Maintainable code and common patterns? But I prefer code-golfing my if-statements into one, long sequence of characters.”
-coworker standing atop the Dunning-Kruger peak
I honestly don’t think that doing these cool things improves your odds of getting hired. Junior Devs don’t really touch these parts of a platform, let alone lead development on them from scratch.
A valuable engineer, to me, is someone who writes clean, maintainable code and follows common patterns. That’s also something which has to be learned by trial and error to actually see the value of.
And how would you demonstrate clean code and check for maintainability or patterns? How can you gauge the value of their trial and error?
Look at their code, look at their work. It is a point of reference for potential and actual scenarios.
This would absolutely increase their odds.
Sure, look at their personal projects. I’m just saying the maintainability and quality of the code and speed of iteration is more of the point than how impressive the math is behind an ML algorithm. I’ve just seen a lot of ML engineers/data scientists who really suck at writing maintainable code
“Maintainable code and common patterns? But I prefer code-golfing my if-statements into one, long sequence of characters.” -coworker standing atop the Dunning-Kruger peak