Anybody who wants to do this has to be willing to step off the gravy train. That sounds snarky, but it just reflects the Hard Problem of a skill that's of value in two sectors with vastly different economics.
There are people who have stepped off the gravy train because they don't like it, or they don't fit into the enterprise workplace for whatever reason. I might be one of those people. I work in industry, but in an early-stage R&D team.
Maybe the status quo is a reasonable solution: Find grad students who are willing to do the work in return for a chance to sharpen their programming skills. This process could be improved by providing scientists with training on how to write better code. The result will be a certain amount of attrition of scientists into software development jobs, but we have to get used to the idea that attrition into a more employable field is actually a good thing, and there will be plenty of scientists.
>I've personally done this by finding normal work that is part time, so I can round it out doing work for scientists
That's what I did for the first 10 years after graduating from university. Eventually I transitioned to a full time 'normal' job but that made me unhappy.
There are people who have stepped off the gravy train because they don't like it, or they don't fit into the enterprise workplace for whatever reason. I might be one of those people. I work in industry, but in an early-stage R&D team.
Maybe the status quo is a reasonable solution: Find grad students who are willing to do the work in return for a chance to sharpen their programming skills. This process could be improved by providing scientists with training on how to write better code. The result will be a certain amount of attrition of scientists into software development jobs, but we have to get used to the idea that attrition into a more employable field is actually a good thing, and there will be plenty of scientists.