search

swcarpentry / managing-research-software-projects

Managing small to medium-sized research software projects.
https://swcarpentry.github.io/managing-research-software-projects/
Other
37 stars 13 forks source link

Cut/merge material on mechanics and robust software #39

Closed gvwilson closed 7 years ago

gvwilson commented 7 years ago

Major feedback from first run is that there's too much on basic tooling and robust software that participants already know, which meant not enough time for project management material that they don't.

  1. Cut 02-rse (or make it a callout and give it one minute in passing): not relevant to the aims of this course.
  2. Merge 08-selfdoc, 09-installable, 10-integratable, and 11-trustworthy into one 10-minute episode.
  3. Didn't have time to cover 13-packaging, 16-ci, or 17-tdd (though CI and TDD were discussed briefly in the overview of agile).
    1. Mention 13-packaging as part of merger of other "robust software" items 08-11 above.
    2. Make sure there's time for pair programming and TDD exercises.
  4. Didn't get to 20-tolerances.
  5. Didn't get to 22-mentor, but feedback suggested this was something people were really looking forward to.
  6. Did cover the A&E and schedule-building stuff from http://v4.software-carpentry.org/softeng/sturdy.html: add this as a module.
  7. Challenges for attendees that came up that the lessons should address:
    1. No time in schedules to learn new technologies, and (probably) no way to get it.
    2. Distributed teams: how to do stand-up meetings, pair programming, etc., when people are scattered across multiple timezones?
    3. Timeslicing: most people are working on several projects, and don't control their own calendars.

Telepresence worked well enough (some audio glitching in the first hour, stable after that), but Etherpad started locking up around 3:00 pm. Time to switch to a Google Doc...?

gvwilson commented 7 years ago

Replaced by #45 #46 #47.