| Job | Prof of Stats and DS at Cal Poly |
| Pronouns | she/her |
| Location | San Luis Obispo, CA |
| Favorite R Package | stringr |
Python Data Science at posit::conf(2023). We are excited about all our Python workshops are posit::conf this year.
posit::conf(2023) is our conference for all things open source data science. Join us in Chicago Sept 17-20. With two days of workshops, and two days of talks and community. Learn more at pos.it/conf.
See below!
I legitimately sincerely tried to narrow down my schedule I swear. It is not possible everything is too awesome.
Current mood: Shiny apps in Quarto
It is soooo much easier to write and design and debug chunks and text in app.qmd compared to the big nested functions in app.R
As usual, wishing I tried this sooner. 😂
Materials and info for all talks from our #jsm2023 session yesterday, "Teaching (with) Quarto" 👇
https://mine-cetinkaya-rundel.github.io/teach-with-quarto/
Shoutout to @minecr for putting together a great session (and website!), and to @quarto_pub for basically being the answer to all my #rstats and #python prayers!
Last night's drink definitely prepared me well for my #jsm2023 talk on @quarto_pub !!!
Thanks to all who cane, we had a fun crowd and some excellent questions! #rstats crew knows how to show up!
🏴☠️💙
Does anyone in my #rstats and #python crew have good advice for a Colab -> Quarto render workflow?
Context: we'd like our students to work in Colab, but turn in a final Quarto-rendered file.
The workflow of "download ipynb -> run quarto render" feels like bad reproducibility. As students tweak the notebook for render, this will leave the Colab copy un-updated.
Ideas?
Posit
Julia Silge