Xiangyu Tao HW 1

[xt5]

The experience of setting up softwares in the first lab actually prepared me for this homework. I first forked the repo from uc-csff to my GitHub and then opened R studio to create a new project through version control. I cloned the HW1 from my git repo and opened the readme.md.

I read the guide from GitHub for writing Markdown documents and practiced using R Markdown while editing my biography. I committed several times to see what it look like in GitHub. After finished my homework, I saved and committed all the changes in R studio, pushed the commit to Github, and opened a pull request. That's where I am right now.

The only challenge I faced in this HW was that I couldn't embed a photo of myself since the URL for most of my photos didn't match the requirement, that is, I couldn't find a link looks like "xxxxxxx.jpg". (I don't know how to precisely describe the difference between different URL, and I hope I will be able to do that after taking this class.) Anyway, I googled "how to get a link with jpeg format" and successfully solve the problem.

I feel very excited and encouraged that I could finish this homework independently, even though I knew that HW 1 had nothing to do with R and must be the easiest HW in this quarter. I won't drop the class! I'm gonna finish the rest!

[pohyuquan]

Evaluation HW-01 for Xiangyu Tao

Topic	Excellent	Satisfactory	Needs Work
Coding style	✓
Coding strategy	✓
Presentation	✓
Achievement, creativity		✓
Ease of access	✓

Remarks:

Xiangyu definitely showed that she could successfully fork and clone a repository from GitHub, make local changes to the documents and commit her changes before pushing it to GitHub.

Syntax used in the Markdown document demonstrates understanding and conceptualization of the syntax required to create a presentable layout.

One thing that she could have done differently was that she could have previewed her html on RStudio without needing to commit and push every time she wanted to view her changes. While 4/5 of the objectives for the markdown document were demonstrated, perhaps she could also have attempted to include the last objective (link).

With regards to the image, good attempt at embedding it into the markdown document by looking up google. I believe that is the way you get images embedded (upload the picture into a online platform to get a url to embed).

Other than that, really excellent attempt for the first assignment.

[MichelleWang32]

Evaluation of HW01:

Coding Style: N/A (no coding) / + Coding Strategy: N/A (no coding) / + Presentation: Excellent + (Clear and comprehensive) Achievement, Creativity: Excellent + Ease of Access: Excellent +

Reviews: Good job! This assignment is clear and concise, and it demonstrates that she knows how to apply markdown elements (bold, italics, picture, hyperlinks, lists, and headers) in this assignment. She also saves, commits and pushes to the Github constantly as she fixes her biography, which is a good strategy as someone who just got to know R and Git. Nice work overall and look forward to your future works!

[jmausolf]

Evaluation HW-01 for Xiangyu Tao

Topic	Excellent	Satisfactory	Needs Work
Coding style	x
Coding strategy	x
Presentation: graphs
Presentation: tables
Achievement, creativity	x
Ease of access	x

Remarks:

• For the header of the assignment, you probably could have removed the "hw01" header and subsequent lines with the assignment details. If you would like to include these, they could probably go in your pull request title/notes.
• Nice attempt of adding a .gitignore. There is actually a default one for R files that you can get when creating a new repo. You tried to ignore the .Rproj, but committed it anyway. Two things:

1. Commit the .gitignore before other commits
2. Pay attention to the backslash: .Rproj.user vs.

   .Rproj.user/

3. If you are using bash, you can run the command git status to check what files you have added before committing them. This is best practice, especially at first.

Full R .gitignore file

# History files
.Rhistory
.Rapp.history

# Session Data files
.RData

# Example code in package build process
*-Ex.R

# Output files from R CMD build
/*.tar.gz

# Output files from R CMD check
/*.Rcheck/

# RStudio files
.Rproj.user/

# produced vignettes
vignettes/*.html
vignettes/*.pdf

# OAuth2 token, see https://github.com/hadley/httr/releases/tag/v0.3
.httr-oauth

# knitr and R markdown default cache directories
/*_cache/
/cache/

# Temporary files created by R markdown
*.utf8.md
*.knit.md

• Otherwise, you effectively used four of the five style elements, italics, headers, list, and photo. Good job.
• Great use of git. Proved you can do the workflow.