Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cheatsheets and revising the R reference card #22

Open
brownag opened this issue Jan 20, 2021 · 1 comment
Open

Cheatsheets and revising the R reference card #22

brownag opened this issue Jan 20, 2021 · 1 comment

Comments

@brownag
Copy link
Member

brownag commented Jan 20, 2021

I think we should focus some efforts towards updating the "reference card" from 2016, and taking its contents and putting into an even more compact format

@smroecker @jskovlin @dylanbeaudette @hammerly @phytoclast @skyew

http://ncss-tech.github.io/stats_for_soil_survey/reference_card/reference_card.html

It is a great idea -- and has well-written content -- but it is not a "card."

The traditional "cheatsheet" concept is something I have wanted to emulate for aqp and soilDB. But I have not done that. And that is not an issue for this stats class repository. We barely scratch the surface of either of those packages in the class, so I almost would be tentative to throw the cheatsheet at a brand new R user -- given the current variety in both packages. I had wanted to make something before SSSA, but I didnt ever get around to it. Partially because of this [perceived] problem.

Here are some examples: https://github.com/rstudio/cheatsheets

I think we could make a cheatsheet that is specific to the stats classes (one each for parts 1 and 2) -- and targeting an actual single-page, nice looking, compact format

@brownag
Copy link
Member Author

brownag commented Jan 20, 2021

Another fun exercise might be to have all the instructors and mentors go through alist of cheatsheets such as:

https://rstudio.com/wp-content/uploads/2019/01/Cheatsheets_2019.pdf

And pick out a top 3 or 5 that reflect things we use, or things we think people should know. We could then tabulate the results -- could be a fun stats exercise, but also just an interesting way to crowdsource some ideas on different packages and things that different folks like to use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant