The question on this page doesn't actually have anything to do with the content of the page. Also, is putting datasets in Git really something that we want to be recommending?
ex3
Maybe put the repo in a directory named "repos" or "repositories". Beginners might be wondering what the significance of the "repl" directory is.
Maybe say: "What is the message on the chronologically first entry in the log (which is displayed last)"
I had an error message submitting on this one: ``` Something went wrong. If the problem persists, please report an issue ``` When I restarted the session, it went back to the very beginning of the terminal, no to the `git log` part that I would expect it to.
When I exit the course and then opt to continue where I left off, the shell session similarly starts at the beginning.
Also, the output of `git log` goes to `more` or `less` or some other pager on the screen of my MacBook Air, many beginners wont know to scroll down (and I didn't think to either).
Actually, I can't get this one to submit at all, even after multiple tries.
ex5
None of the answers, including the correct one, are recognized as correct.
ex6
My terminal crapped out by itself after a few minutes on this page.
You should probably mention in this one that each changed file has that @@ line, followed by the additions and removals for that file. For a beginner, its very confusing what all the symbols mean, and the @@ directly pertains to the comprehension question.
No answers are recognized as correct.
ex7
I see that you explain the diff more here, but it still feels like I should have known this before the last question.
Which argument comes first - the hash or the filename?
No answers recognized as correct.
The incorrect submission hint talks about `git show ed0ec0`. I think this is the wrong hint.
ex8
Maybe link to the absolute path lesson from your shell course here?
No answers recognized as correct.
ex9
No answers recognized as correct.
ex10
Change wording of first sentence to: `git show` only shows the changes made since the previous commit.
"previous-but-two" is phrasing that I'm unfamiliar with, and probably others as well. Change to: "…between its current state and its state two commits previously". Or something like that.
No answers recognized as correct.
Higher level, pedagogical thoughts
Many of these commands in the first lesson don't play a huge role in an average data scientist's workflow. They aren't necessarily key to understanding the underlying concepts (arguably), and they are very dry and verbose, especially before beginners really understand how and why they would be looking at these particular details. Do you see value in starting from a more practical, workflow driven place?
I though I'd split up my feedback into lessons for easier digestibility.
ex2
ex3
ex5
ex6
ex7
ex8
ex9
ex10
Higher level, pedagogical thoughts
Many of these commands in the first lesson don't play a huge role in an average data scientist's workflow. They aren't necessarily key to understanding the underlying concepts (arguably), and they are very dry and verbose, especially before beginners really understand how and why they would be looking at these particular details. Do you see value in starting from a more practical, workflow driven place?