4 ms·
Learning git, refactoring, testing, CI, ect. is going to be way too many "credits" spent on that. It's important, but certainly not what they should be spend th
by hvidgaard 6y ago
Learning git, refactoring, testing, CI, ect. is going to be way too many "credits" spent on that. It's important, but certainly not what they should be spend their time on if they could avoid it.
The universities ought to have a CI system in place with guidelines, and preferably staff that can help with it. Ideally there should be some collaboration between the SE students and researchers worth credits for the CS students.
- GauntletWizard 6y agoEvery bit of Git, Testing, CI, etc - These are experimental skill. They directly translate into good experiment design. They help you figure out where you went wrong, what you assumptions were, and condense them down into a precise, succinct and yet fully-formed thesis.
- hvidgaard 6y agoIt's a mindset, and absolutely not necessary for researchers. If they do not learn that as a part of their PhD, they're not going to learn that with programming.
- l0b0 6y agoI would love to see this sort of thing facilitated. Get someone on board who is familiar with something like GitLab CI/CD and at least a couple popular languages, and let them set up and maintain template repos with all the good stuff: in-repo configuration (not snowflake CI systems like Jenkins), tests, idiomatic project structure, commit hooks for linting/formatting, simple Markdown documentation, maybe even some popular IDE configuration. Anyone used to learning by example will just need to know about the readme to get a head start.