Programmer
You have to write or contribute to open source Python code for your research. I'm a software developer with lots of experience in automated quality assurance. Together we can ensure that the code is adequately tested, as simple as possible while being correct, and easy to use for people who want to verify the results for themselves.
Faced with such uncertainty, shouldn't we rather hedge our bets and split our support? For example, if project A has cost-effectiveness in the range of 70-80%, and project B has cost-effectiveness in the range 60-90%, wouldn't it be better (overall) to split the support evenly than to only support project A?