Making Changes feedback

[justmytwospence]

• ex1
• ex2
• ex3
• ex4
• ex5
• ex6
• ex7
• ex8
• ex9
• ex10
• ex11
• misc

ex1

• Correct answer not recognized.

ex2

• Second task doesn't complete when I type git status.

ex3

• A mnemonic for the -r flag would be helpful.
• Can't get the second task to complete with git diff -r HEAD data/northern.csv | cat

ex4

• Second task doesn't complete.
• Do we want to talk about what a commit should be (atomic, thematically related)? A misunderstanding of Git practices is one of the biggest problems DS have with version control in my experience, preventing them from getting the most out of it.

ex5

• I get the exercise completed message as soon as I type the command - there's no time for me to actually write a message!
• Do we want to give a sentence or two about styling your commit messages?

ex6

• None of the tasks are completing.
• I mentioned this in my feedback for the last lesson, but do we want to be encouraging data scientists to put their data in version control? This is generally regarded as a bad habit where I come from.

ex7

• Same old problem with the tasks.

ex8

• This exercise touches on the "what a commit should be" question I posed above.

ex9

• First task completes, second doesn't

ex10

• Maybe you could link here to a part of shell course that deals with the -- shell idiom.

ex11

• The note about Git being large and irregular is discouraging to a beginner, I think. As you point out in the sentence, its not actually irregular in full context.

misc

• I think an overview of the working files, staging area, committed files, etc. is useful before digging into each of them. Having the big picture is important before zooming in on the smaller components. Maybe a diagram?

• Even if you'd rather not restructure things into an overview -> specifics format, is it possible to get pictures into the lessons to help illustrate things?

[gvwilson]

Closed after 451cb4c and reorg, with one issue pushed sideways to #17.