TA comments

[ChadFibke]

The Reflection

• Thanks for sharing your workflow! Another way to get help is to go to the lower right panal in r studio > click the help tab, and type in the command you want help with.

The README

Creativity & Effort

The good :thumbsup:

• You explored many markdown syntax options to introduce yourself (went above and beyond), and it makes the readme nice to look at!

Needs work :thumbsdown:

• NA

Ease of access

The good :thumbsup:

• Easy for me to navigate from canvas to your github!

• It was good that you linked to the updated files :smile:. It really helped with navigation.

Needs work :thumbsdown:

• You can easily remove the extra files right from your r.proj interactivly. Open the project that is connected to git (that you previously clonned) > go to the lower right pannel in rstudio > click the files tab > check the files you want to remove > click the delete tab. This will register the deletion (will show a red square) which you will see in the top right git tab.Then Pull > stage/check > commit meassage and commit > push.

The Rmd/md

Coding style/strategy

The good :thumbsup:

• Utilized markdown in a consistant, helpful way (headers!)

• Some inline comments, and interpreting the results helped with the flow.

• Code looks great! Each line of code has its own function, and piping like this helps with readability for others!

• Explored the data!

Needs work :thumbsdown:

• There is excessive output that is not needed. An easy work around would be:

levels(as.factor(iris$Species))

• Add a name to each code chunk. This will help with the organization. To check what I mean, go to your hw01-JasmineLib/STAT545_Gapminder_Updated_files/figure-markdown_github/ folder and see all the unnamed chunks.This indexing/naming will help diagnose errors when knitting a file, and help with overall navigation.

Overall

• Great work!

[JasmineLib]

Hi Chad,

Thank you so much for the helpful comments. I'll be sure to add names to the code chunks for hw02.

Jasmine