3 ms·
> and where researchers are expected to write production-quality code. For someone like myself who has no idea what research labs do beyond "build cool stuff"
by MattGaiser 6y ago
> and where researchers are expected to write production-quality code.
For someone like myself who has no idea what research labs do beyond "build cool stuff" why is this a problem?
Is it just outside your core competency? Eliminates a lot of good researchers?
- wongarsu 6y agoAs a rule of thumb I would say that building something "production-quality" takes at least ten times longer than building something I and close collaborators can use. By having researchers build production-quality code the spend a lot more time with software engineering and a lot less time researching. (And of course many great researchers are actually not that great at programming, so you probably lose many of them as well)
- deleted 6y ago[deleted]
- godelski 6y agoBecause the skill sets aren't the same. Research in of itself is a different skill set. Getting a PhD is more about learning how to take abstract and vague ideas and turning them into a reality. Making highly readable, robust, and secure code is a different skill set. Sure, you can have people that do both, but at that point you're often asking a painter to do sculpting. Skills do translate, but not well. They probably won't be interested in it either, so you're not using your workers efficiently either. Give the canvases to the people who love painting and give the marble to those that love sculpting. You'll probably get better art in the end.