Overview feedback from Rasmus

[rasmusab]

Step 0: Learner Profiles

I'm not sure how to interpret these. Like, how would the fact that "Yngve already knows the material in this course" or that "Catalina will take this course herself if she has time" guide how you design the course?

Step 1: Concept Map

I think this type of concept map is great for the person doing it, if that person understands what it means. Personally I find it difficult to look at this and understand what's going on and how it relates to the course.

Step 2: Summative Assessment

Is this supposed to be a DataCamp exercise? If so, it seems like it includes to many steps for it to be possible to write as one exercise. Is it more like an example of a task that the student should be able to perform after having finished the course?

Step 3: Formative Assessments

All these seems like reasonable tasks.

Step 4: Course Outline

Is the course outline supposed to map to a DataCamp course outline? Is so it seems that there are either to many lessons (usually 4 per chapter) or too few exercises (usually 12-16 per chapter). Also, a DataCamp course is usually limited to 5 chapters.

Thoughts on the content:

• Would feel natural to me that the course starts with checking out a project.
• Something that needs to go somewhere (maybe in the videos) is the general philosophy/theory of version control in general and git specifically. Like, what is the problem with just sending e-mails, why was git created when subversion already existed, why is it called git, etc. Right now the course outline only seem to mention practical exercises.
• Even if we can't use GitHub/gitlab it should be mentioned as the standard way people use git.
• I've rarely used what's mentioned in "4. advanced features", but "6. Collaborating" is neccecary if you want to work with github. Even if we can't work with github in the actual course, there could be a video explaining how all that works.

Step 5: Course Overview

Great course description and learning objectives!