Closed ghost closed 5 years ago
Topic | Excellent | Satisfactory | Needs Work |
---|---|---|---|
Coding style | x | ||
Coding strategy | x | ||
Presentation | x | ||
Achievement, creativity | x | ||
Ease of access | x |
Great use of markdown, and organization of your page! Whenever you have issues and need clarification, feel free to contact the TAs too! :)
Topic | Excellent | Satisfactory | Needs Work |
---|---|---|---|
Coding style | X | ||
Coding strategy | X | ||
Presentation | X | ||
Achievement, creativity | X | ||
Ease of access | X |
Remarks: Good use of markdown elements Good and detailed sections. Don't use branches as stated in class. Use gitignore files when possible to avoid committing useless files such as .ds_store
Topic | Excellent | Satisfactory | Needs Work |
---|---|---|---|
Coding style | X | ||
Coding strategy | X | ||
Presentation | X | ||
Achievement, creativity | X | ||
Ease of access | X |
Remarks:
While working on homework 1, I had trouble making lists, ensuring that my assignment looked the same in GitHub as it did on RStudio, and incorporating an image. I mainly guessed and checked my work using the preview tool on RStudio, but I needed more help incorporating the image, so I visited Dr. Soltoff during his office hours. He helped me add an image to my GitHub repository and helped fix the headers (I hadn't added a space after ##). He also explained that due to a different software, sometimes files in RStudio look different than on GitHub.