A friend is getting a degree in a field similar to biology. She and everyone else in her program have been processing their data (for at least the past 5 years) with a script written by the person in the department who is most competent with the programming tools at their disposal.
Last week, sanity-checking its output, she discovered a bug in the script that meant that every dataset processed by this program had been deeply flawed.
That means dozens, maybe hundreds of studies published based on meaningless data.
It might be worthwhile to also introduce a cautionary tale or two and encourage your students to take followup courses that go deeper into programming; learn automated testing; etc, so that they can be confident in the future that the output of their studies is correct.
Even worse, I heard a very similar story in a science talk only last week. I wonder how many more of these bugs there are out there?
Big labs with large funding where funding sources allow hiring non-research full-time support staff as software engineers, places like the Broad, tend to have slightly better practices. But if you're using a package written by a graduate student.... his job is not to make yours easier. And since he's paid less than the guy who manages your local sandwich shop, maybe it's understandable.
There's a problem in science where we don't value scientists. Telling them "the world values software engineering" and turning them into software engineers is only going to make them go into industry faster.
I agree that we shouldn't ask them to be professional software developers, but then we need to provide them with access to professional developers if we want there to be such a thing as science that uses data and computing.
It's ridiculous to ask untrained people to write data processing scripts if you want to be able to rely on the output.
And then people wonder why we have a reproducibility crisis.
For the actual data science, as opposed to writing new software packages, it would be reasonable for students to maintain lab notebooks (except for computer experiments not wet lab ones), with exact versions of everything, exact steps, name, size and checksum of every dataset, and so on. I think things are definitely moving in that direction but this is a skill that is not beaten as much into grad students as recording wet lab work is. But in time it will be.
Though, my experience in wet labs is, both quality of the lab notebooks and quality of the labeling of the stuff in the fridge definitely varies.
As for students in biology I will always go tools-first, at least for the first course (which is ~30 hours here). Then for further courses I would go fundamentals.
A lot of students of biology (unfortunately) don't really care about programming, and may consider it as some kind of black magic. Taking them quickly to do things that "works" is essential to break the ice. And this is just what I think the first course is for: to give them the intuition of what programming is.
Then, for a biologist to take a second course of programming (this is not mandatory here) means he/she really wants to learn something, so we can raise up the bar and go fundamentals.
Hope this helps.