The resilient R champion
summary
Practical steps to get R adopted: build a proof-of-concept with open‑source R and share tangible results, run a Lunch and Learn and spin up an internal Slack channel to create demand, use RStudio Connect to auto‑email executives and demo reporting, and offer commercial RStudio only when performance/security/support or legal coverage is required. If IT balks, deploy pre-configured VMs on AWS/GCP/Azure, tap a research “mad scientist” team or external partner to install servers, and ask targeted questions to uncover future funding or policy paths.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 2:09Boost R credibility
- 3:34Barriers faced by R champions
- 6:30Paying for R tooling
- 7:55Funding barriers for R
- 10:56IT and policy hurdles
- 13:25Advocating for R
- 14:50Success stories
- 15:18Q&A
related talks
20mR! You Going?!
20mRipples of Change with R- It's more than just coding
44mHow to Teach an Old Firm New Tricks
16mWhat they forgot to teach you about starting a business with R
11mHow the R for Data Science (R4DS) Online Learning Community Made Me a Better Student
05mTen Simple Rules for Teaching an Introduction to R
18mThe 'I' in Team: Peer-to-Peer Best Practices for Growing Data Science Teams
18mBecoming an R Package Author (or How I Got Rich Responding to GitHub Issues)