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

How to Ask Questions so they get Answered! Possibly by Yourself! JD Long, Jenny Bryan, Scott Chamberlain; 2017-03-07, 8AM PST #14

Closed
stefaniebutland opened this Issue Jan 24, 2017 · 23 comments

Comments

Projects
None yet
6 participants
@stefaniebutland
Collaborator

stefaniebutland commented Jan 24, 2017

Community Call v13: How to ask questions so they get answered! Possibly by yourself!

Link to meeting: https://bluejeans.com/928914471

Collaborative notes: http://bit.ly/commcallv13

Agenda:

  • Welcome (5 min, Stefanie Butland)
  • guest: James (JD) Long (15 min)
    • James will review the historical challenges of getting R help and give some history about how the [r] tag on Stack Overflow was bootstrapped.
  • guest: Jenny Bryan (20 min)
    • Jenny will talk about the mechanics of making reproducible examples using the reprex package. Just as important, she'll discuss the philosophy i.e. that forcing yourself to make little, rigorous, self-contained examples makes you think more clearly about programming.
  • guest: Scott Chamberlain (10 min)
  • Q & A (10 min, moderated by Scott Chamberlain)

More details, including speaker bios.

Have an idea for a Community Call? Tell us about it

@noamross

This comment has been minimized.

noamross commented Jan 25, 2017

@stefaniebutland stefaniebutland changed the title from Community call v13 - Tuesday, March 6th, 8 am PST to Community call v13 - Tuesday, March 7th, 8 am PST Jan 25, 2017

@stefaniebutland

This comment has been minimized.

Collaborator

stefaniebutland commented Jan 29, 2017

@jennybc @CerebralMastication Hope this info can facilitate your discussion/decision on what to present. Please add 3-4 lines of text suitable for a blog post to explain/advertise what you will present (due Feb 7, 2017).

Community Call v13: How to ask questions so they get answered! Possibly by yourself!

Presentation Content:

Jenny

  • I plan to talk a bit about reprex (mechanics) but also about philosophy i.e. that forcing yourself to make these little rigorous, self-contained examples makes you think more clearly about programming.
  • https://github.com/jennybc/reprex

James

Notes

  • from @noamross: Note the importance of targeting the right forum to ask a question. There are communities of different scales with different rigor around asking questions. Newer users should be aware of this

Resources that may contribute to a blog post, after Community Call

Draft speaker bios:

Jenny Bryan is a member of rOpenSci's Leadership team, title here at RStudio and an Associate Professor (on leave) in the Statistics Department and the Michael Smith Laboratories at the University of British Columbia in Vancouver. She's a biostatistician specialized in genomics and takes a special interest and delight in data analysis and statistical computing.
GitHub, Twitter

James (JD) Long works in reinsurance in New York City. He builds risk models which, according to George Box, are wrong. In spite of this inconvenient truth, James has proved successful at convincing his employer that his models are useful. James writes poorly commented, inefficient code using Python, R, SQL, and expletives.

James grew up in Kentucky and has multiple degrees from the University of Kentucky. After being marooned on the archipelago of Bermuda for four years, James now lives in Jersey City, NJ with his Minecraft addicted 9 year old daughter and his wife, a recovering trial lawyer.
GitHub, Twitter

@jennybc

This comment has been minimized.

Member

jennybc commented Feb 6, 2017

Is this not enough (what I have above)?

I plan to talk a bit about reprex (mechanics) but also about philosophy i.e. that forcing yourself to make these little rigorous, self-contained examples makes you think more clearly about programming.

@CerebralMastication

This comment has been minimized.

CerebralMastication commented Feb 15, 2017

unless Jenny has compelling desire to speak first, I think it makes sense for me to go first with (10-15 minutes):

  • Review of the historical challenges of getting R help.
  • Some history about how the [r] tag on stackoverflow was bootstrapped

Then I'll pass to Jenny for her deep dive into creating reproducible examples.

@jennybc

This comment has been minimized.

Member

jennybc commented Feb 16, 2017

I'm happy to go after @CerebralMastication and will plan my content accordingly, i.e. not re-cover the same ground.

@stefaniebutland

This comment has been minimized.

Collaborator

stefaniebutland commented Feb 16, 2017

blog post announcing this should go up sometime Thursday. Thank you!!

@CerebralMastication

This comment has been minimized.

CerebralMastication commented Feb 16, 2017

when @jennybc is back stateside we'll ensure coordination.

@stefaniebutland

This comment has been minimized.

Collaborator

stefaniebutland commented Mar 6, 2017

@CerebralMastication @jennybc Here is the link to join Tuesday's call: https://bluejeans.com/928914471
@sckott and I will be there ~7:50 AM

We'll do collaborative note-taking during the call here: http://bit.ly/ropensci_commcall13

Let me know if you have any questions.

@jennybc

This comment has been minimized.

Member

jennybc commented Mar 6, 2017

Got it! I guess we're getting up early tomorrow, eh?

@stefaniebutland

This comment has been minimized.

Collaborator

stefaniebutland commented Mar 6, 2017

yep, I reminded Scott to roast coffee beans in advance. Last time he had to do the call without coffee!

@CerebralMastication

This comment has been minimized.

CerebralMastication commented Mar 6, 2017

@jennybc

This comment has been minimized.

Member

jennybc commented Mar 6, 2017

I could also use a reminder on the tech. I haven't been a presenter in a long time.

@stefaniebutland

This comment has been minimized.

Collaborator

stefaniebutland commented Mar 6, 2017

yes @CerebralMastication that's it. Sound supposedly clearest if you use a headset/earbuds, but this is not required. Screensharing etc with the Bluejeans system seems pretty straightforward to me. There will be a "share your screen" button/tab near the bottom of your window.

James and @jennybc best to join by 7:45 or 7:50 AM (Pacific) so we can test that we can hear you and see your screen when you share it.

@CerebralMastication

This comment has been minimized.

CerebralMastication commented Mar 7, 2017

@amitkumarj441

This comment has been minimized.

amitkumarj441 commented Mar 7, 2017

Hey @stefaniebutland,

I'm sorry :( to say that I couldn't able to attend today call because I'm having my semester exam in an hour.

Will I able to access recorded session of today's call?

Cheers,
Amit Kumar Jaiswal

@stefaniebutland

This comment has been minimized.

Collaborator

stefaniebutland commented Mar 7, 2017

Hi @amitkumarj441. The call is Tuesday. Details at the top of this issue.
Hope your exam went well

@jennybc

This comment has been minimized.

Member

jennybc commented Mar 7, 2017

If I should perish during the night or, more likely, I have internet woes, here's a cool reprex that includes a figure and collapsible session info. I'll try to do this live during the call.

## install.packages('ggbeeswarm')
library(ggbeeswarm)
#> Loading required package: ggplot2
ggplot(mpg,aes(class, hwy)) + geom_quasirandom()

Session info
devtools::session_info()
#> Session info -------------------------------------------------------------
#>  setting  value                       
#>  version  R version 3.3.2 (2016-10-31)
#>  system   x86_64, darwin13.4.0        
#>  ui       X11                         
#>  language (EN)                        
#>  collate  en_CA.UTF-8                 
#>  tz       America/Vancouver           
#>  date     2017-03-07
#> Packages -----------------------------------------------------------------
#>  package    * version     date       source                            
#>  assertthat   0.1         2013-12-06 CRAN (R 3.2.0)                    
#>  backports    1.0.5       2017-01-18 cran (@1.0.5)                     
#>  beeswarm     0.2.3       2016-04-25 CRAN (R 3.3.0)                    
#>  bitops       1.0-6       2013-08-17 CRAN (R 3.2.0)                    
#>  colorspace   1.3-2       2016-12-14 CRAN (R 3.3.2)                    
#>  devtools     1.12.0.9000 2017-02-09 Github (hadley/devtools@d8ab190)  
#>  digest       0.6.12      2017-01-27 cran (@0.6.12)                    
#>  evaluate     0.10        2016-10-11 cran (@0.10)                      
#>  ggbeeswarm * 0.5.3       2016-12-01 CRAN (R 3.3.2)                    
#>  ggplot2    * 2.2.1       2016-12-30 CRAN (R 3.3.2)                    
#>  gtable       0.2.0       2016-02-26 CRAN (R 3.3.0)                    
#>  htmltools    0.3.5       2016-03-21 CRAN (R 3.2.4)                    
#>  knitr        1.15.1      2016-11-22 CRAN (R 3.3.2)                    
#>  labeling     0.3         2014-08-23 CRAN (R 3.2.0)                    
#>  lazyeval     0.2.0.9000  2016-10-24 Github (hadley/lazyeval@c155c3d)  
#>  magrittr     1.5         2014-11-22 CRAN (R 3.2.0)                    
#>  memoise      1.0.0.9001  2016-12-18 Github (hadley/memoise@884d565)   
#>  munsell      0.4.3       2016-02-13 CRAN (R 3.3.0)                    
#>  pkgbuild     0.0.0.9000  2016-11-22 Github (r-pkgs/pkgbuild@65eace0)  
#>  pkgload      0.0.0.9000  2016-11-22 Github (r-pkgs/pkgload@def2b10)   
#>  plyr         1.8.4       2016-06-08 CRAN (R 3.3.0)                    
#>  Rcpp         0.12.9.3    2017-02-24 Github (RcppCore/Rcpp@8bf15c0)    
#>  RCurl        1.95-4.8    2016-03-01 CRAN (R 3.3.0)                    
#>  rmarkdown    1.3.9002    2017-02-09 Github (rstudio/rmarkdown@f098542)
#>  rprojroot    1.2         2017-01-16 CRAN (R 3.3.2)                    
#>  scales       0.4.1       2016-11-09 CRAN (R 3.3.2)                    
#>  stringi      1.1.2       2016-10-01 CRAN (R 3.3.0)                    
#>  stringr      1.1.0       2016-08-19 CRAN (R 3.3.0)                    
#>  tibble       1.2-14      2017-01-06 local                             
#>  vipor        0.4.4       2016-10-05 CRAN (R 3.3.0)                    
#>  withr        1.0.2       2016-06-20 cran (@1.0.2)                     
#>  XML          3.98-1.5    2016-11-10 CRAN (R 3.3.2)                    
#>  yaml         2.1.14      2016-11-12 cran (@2.1.14)
@amitkumarj441

This comment has been minimized.

amitkumarj441 commented Mar 7, 2017

Ohh...Thanks a lot 👍 @stefaniebutland for the reminder! It's 09:30 PM in India, I'll be there during call.

@jennybc

This comment has been minimized.

Member

jennybc commented Mar 7, 2017

template <- "${EXCLAMATION} - your reprex is ${adjective}!"
praise::praise(template)
#> [1] "HUZZAH - your reprex is awe-inspiring!"
@jennybc

This comment has been minimized.

Member

jennybc commented Mar 7, 2017

## install.packages('ggbeeswarm')
library(ggbeeswarm)
#> Loading required package: ggplot2
ggplot(mpg,aes(class, hwy)) + geom_quasirandom()

@stefaniebutland

This comment has been minimized.

Collaborator

stefaniebutland commented Mar 16, 2017

@CerebralMastication Do you have a link to your slides that you're willing to have in the blog post about our call? I've got Jenny's and Scott's. Not to worry if it's a no.

Do you prefer to have a quick look at the draft post before it goes live? (Who knows what wisdom you might be inspired to share after the fact.)

@sckott

This comment has been minimized.

Member

sckott commented Mar 16, 2017

@CerebralMastication

This comment has been minimized.

CerebralMastication commented Mar 17, 2017

@stefaniebutland stefaniebutland changed the title from Community call v13 - Tuesday, March 7th, 8 am PST to How to Ask Questions so they get Answered! Possibly by Yourself! JD Long, Jenny Bryan, Scott Chamberlain; 2017-03-07, 8AM PST Dec 18, 2017

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