2 ms·
I have a background in research and academia. > They will want to work with tools like Matlab or Python, when we typically work with languages like Rust. I do
by mattpallissard 4y ago
I have a background in research and academia.
> They will want to work with tools like Matlab or Python, when we typically work with languages like Rust.
I don't see them problem with this. Research is done, paper is published, engineers take the paper and implement. Standard operating procedure.
I will also note that there are A LOT of academics interested in compute that would love to work in languages that are more strongly typed than python. That said, they'd probably still mock things statistical things in python or R 'cause libraries.
> They also don't seem to have a big sense of the urgency needed at my small company.
If you can tie the work to prestige you can change that. For example, if there is a timeline for a paper to be published. I've seen a lot of research set to a cadence successfully. At times it felt like a product launch, 11th hour shenanigans included.
- tkiolp4 4y ago> Research is done, paper is published, engineers take the paper and implement. Standard operating procedure. Sounds awful (from a developer perspective). If engineers are not getting involved until research is done and paper is published, you run the risk of writing a useless paper (useless from the perspective of the engineers who have to implement it; obviously, from the perspective of the researchers, it’s not useless at all, as in they got to publish yet another paper).