I used a lot of these ideas in the 90-minute version of this workshop I taught in October 2016, and was happy to have a few more minutes to discuss in the full-day version in September 2017.
One of the concerns shared by a couple of the RSEs at the September 2017 workshop is strategies for dealing with inherited legacy codebases. It's one thing to launch a brand new project with these newfound best practices, or to gently improve a young and nascent project. But legacy projects with nontrivial amounts of code are a different beast. This is something we may want to think discussing more explicitly in this module (and maybe others).
I used a lot of these ideas in the 90-minute version of this workshop I taught in October 2016, and was happy to have a few more minutes to discuss in the full-day version in September 2017.
One of the concerns shared by a couple of the RSEs at the September 2017 workshop is strategies for dealing with inherited legacy codebases. It's one thing to launch a brand new project with these newfound best practices, or to gently improve a young and nascent project. But legacy projects with nontrivial amounts of code are a different beast. This is something we may want to think discussing more explicitly in this module (and maybe others).