4 ms·
I've seen both in bioinformatics, because the field is so wide now. 1) Bioinformatics as tool-building, algorithm-dev: you're right, you don't need to know muc
by a_bonobo 4y ago
I've seen both in bioinformatics, because the field is so wide now.
1) Bioinformatics as tool-building, algorithm-dev: you're right, you don't need to know much biology there if the problem is defined well.
2) Bioinformatics as a tool to answer biological questions: here I've seen ML-background people really struggle, either developing stuff that's not useful or reinventing-the-wheel-but-now-it's-deep-learning. I've seen ML people present their fancy plant disease image detector which turned out to be pretty good at spotting 'yellow' - very good at training accuracy and benchmarks, does not add anything to what people in the field are doing.
- qumpis 4y agoIn regards to 2), it sounds a bit directionless to be proposing stuff people don't need? Isn't that more of a problem of selecting relevant problems to solve, and getting supervision on your ideas?
- a_bonobo 4y agoYeah that's the problem! The ML people and the biology or agriculture people don't talk, they're not in the same building. A biologist might see the ML-person's work only after it's published.