4 ms·
>It's crazy to me that researchers prefer to be published over having world renowned software to their name. You could figure out the fanciest database research
by coldtea 5y ago
>It's crazy to me that researchers prefer to be published over having world renowned software to their name. You could figure out the fanciest database research, but there was a period where every fancy new NoSQL database was based on BerkeleyDB despite all that, bolstering the reputation of the University of Berkeley.
Unless the BerkeleyDB was written based on novel research, it didn't move the state of the art forward, it was just a good, used, embeded database.
In which case, your statement can be rewritten as:
"It's crazy to me that researchers prefer to be known for their research over being known as developers of popular programs".
Doing research is the reason they went to an academic career, if they wanted to be developers, they'd just have gone and be developers.
So, why not strike two birds with one stone, and make high quality widely used software that's ALSO state of the art research based?
Well, because creating "high quality widely used software" is a different process, and needs different resources, dedication, and even skills, than doing research.
To showcase some novel research in practice is much much faster, easier, and cheaper to create "half finished demonstration software", that to create a mature, final, implementation that people can use.
So, either they slow their research considerably, and spent most of the time doing software development work - which besides slowing down the pace of research will also count against them in their academic field, they opt to focus on research and just do simple implementation that are not production ready and aren't meant to be.
Seen in this light, it's not a "crazy" choice, it's an essential tradeoff.
- adminprof 5y agoIt seems like it's just that the goals are different. Computer science researchers could also make the opposite case, "The underwhelming impact of software development on producing state-of-the-art computer science discoveries."
- eslaught 5y agoThere are some points in the middle, but it's rare. I work on one of these [1]. We've been building the system for over ten years, and are starting to see some truly killer apps being built on top of it [2, 3]. While it has some great benefits once you arrive, the upfront costs are enormous. You need to find a funding source (or sources) that will pay for this product while you're building it. Also, in order for the research payoff to be worth it, you need both the product itself, and subsequent innovations it enables, to be research-worthy. Not all areas of research can support this. On top of it all, even when you do this, you'll still spend years of effort in activities that are essentially not research. You're basically responsible for all of your own customer support, sales, marketing, etc.---like a startup, but without the financial upside if you succeed. Yes there is recognition and so on, but the payoffs aren't as dramatic. Most people aren't ready to commit to this path. Keep in mind that you can't build this in 5 years either. So a single generation of PhD students can't get it done. The only reason we were successful is because the key staff on the project stuck around for 5+ years after our PhDs because we all believed in doing the work. Given all that, I don't hold it against people at all who just want to build prototypes and then move on to the next thing. It's way less risky and higher reward relative to the costs. [1]: https://legion.stanford.edu/ https://legion.stanford.edu/ [2]: https://flexflow.ai/ https://flexflow.ai/ [3]: https://developer.nvidia.com/cunumeric https://developer.nvidia.com/cunumeric