eggst
commented
6 years ago Evaluation
| Topic | Excellent | Satisfactory | Needs Work |
|---|---|---|---|
| Coding style | x | ||
| Coding strategy | x | ||
| Presentation | x | ||
| Achievement, creativity | x | ||
| Ease of access | x |
Remarks:
- I really enjoyed the clear format, and inviting prose. (I've always loved Denver)
- You're interests are really cool and I'm sure there is a lot to discover through them, I would have liked some additional info about your hobbies or likes outside of the classroom too.
- I enjoyed the comment you left because it's informative, concise and offers some positive opinions as well. Really well done.
- One suggestion (not even sure if it works), if you wanted to streamline the process even more, I believe you don't have to stage any files except the README.md when you commit, that way the extraneous ones like the html or gitignore don't end up taking up space between the files you actually need to see.
audreyyxshi
mayank-kgp
After cloning hw01, I created a new project from the git folder and opened README.md using markdown. It actually took me a while to realize that I could type directly into README after playing around with the console. Getting the headers, emphases, lists and hyperlinks to function was quite easy to accomplish thanks to the cheat sheet from Github. I struggled a bit with getting the image to work. As showed in the issue I opened, the location of the image is simply the file name once it is uploaded onto Github. For this assignment, R Markdown was pretty good to use. However, I did have to be really detail-oriented to make everything work. For example, when I was trying to adjust the font size of a list, the bullet points would be in different sizes in the output. It took me about twenty attempts to figure out that I needed to start with the font size function and leave a blank line before the list. Generally, R Markdown has been very user-friendly even though I still haven't worked out how to make my biography double-spaced. I am getting used to the Github workflow (branch, add, commit, push, etc.) after a few days of playing with bash and trying different commands. While it can be very confusing at times (such as the fetch upstream which I don't know how to use), I think it is systematic and good for collaborative projects.