Make every talk a blog (and vice-versa)
- Tips and tricks for R & Gitlab (CODEOWNER), resolve stuff from R, clone all repos with the API, specific pkgs, etc.
- An #RStats Valentines Day (Cute ways to tell someone you fancy them via R - messages on pkg load, change prompt, R profile/env)
- Scraping the three peaks
- Converting R to JSON and API posting
- Analysis of my experience with twitter hate bubbles
- Scraping Welsh twitter
- Analysing parkrun data
- 🌩️{levelup} Using {yaml} & {rmarkdown} for CPD reporting
- 🌩️ Visualising my work day with clockify, {dplyr}, {ggplot2}
- Bilingual {shiny} / dashboards (too much like Appsilon {shiny.i18n}?
- The little RMarkdown doc that grew and grew and grew
- Validating data (comparison of packages)
- Pretty tables with {GT}
- Visualising TB story
- [ ]
- "I wonder how many characters I can fit into this title bo..." Shiny QA
- Using {bookdown} for client communication Clarity over Availability. Why are we always on? Choose auto-reporting and planned meetings over slack channels
- OWN your code Why/Why/How of CODEOWNERS -> Who's been committing in my repo?
- 🌩️ Google docs for formative assessment (with {googledrive} and {rmarkdown}
- Reproducible research
- 🌩️ GitLab quick actions
- Seperating play and production -> sandboxing
- 🌩️ How not to organise a meetup
- You don't need shiny to sparkle - an overview of interactivity in R
- JR blog on Refactoring Russian Doll Code
- Using Git in your organisation - what to think about?
- Maintainance Look after your biking/paddling kit -> look after your programming kit
- Is it significant?
- How risky are my hobbies? Fell running / cycling / kayaking? Mountain rescue stats
- Knitting and maths
- Identity Crisis - data scientist vs statistician
- Share your data story
- Valentines Day Maths
- Futurama group theory workshop