We can't replace them, but we welcome anyone looking for a friendly, inclusive community to join us at the Data Science Learning Community (@DSLC) https://DSLC.io
I'm once again returning to some #RStats code that I keep having to set aside (and/or I get overwhelmed and choose to set it aside). Today's goal: Find an actual (~smaller than originally planned) stopping point and MERGE THIS ALREADY GAH! It's waaaaay too hard to pick this back up right now.
@Cmastication Dunno if you can see fosstodon's custom emoji over there on mastodon.social, but we have :amiga: and :anAmigaBall: ๐
(reminded me of when we first met at tidyverse dev day at rstudio::conf(2019))
๐It's my birthday!๐
To celebrate, I'm... Working to build a friendly, diverse #DataScience community at https://r4ds.io, just like I do every day! It'd make my day if you supported our efforts at https://r4ds.io/donate !
I love education, and have worked in #EdTech for longer than I've been involved in #DataScience (and long before I heard of #RStats), but I don't have enough experience running workshops. If you're running an online #RStats workshop and could use a TA, I'm available! I read all the things (books/blogs/social media posts/learner questions/github repos/code) so I'm ready to answer questions, but I need more experience with the format!
Please pass this along to your networks!
@kimcressman I had a hedge in that but didn't feel like I need to get into semantics in the initial post. Right now having the experience is really valuable to me, though, so I'm willing to help out for free in situations that make sense. If I find out someone is using my free labor instead of hiring someone they were planning to pay, though, we'll definitely have words. ๐
@jonthegeek good! Just making sure! I've been grateful to people who have insisted I be compensated appropriately now that I'm an independent consultant, and saw an opportunity to do that for you. It's quite a line to walk.
My most useful #RShiny epiphany: modules are a convenient fiction. If you need a way to access a particular input from "inside" a module, there's nothing stopping you from making another module server function just for that. Or you can just NS() to get it, but it's cleaner if you wrap it up, and that generalizes out to more complex sets of functionality related to your module. #RStats
@jonthegeek but the functional confusion also gets me often when writing modules. Without modules itโs easy to connect inputs and outputs as you go. I often find I get the โboundaryโ of my module wrong and immediately want it to connect to other elements or modules in non-local ways. If you think very functionally, you end up changing whatโs passed into the module. But the return anything method I epiphanied into lets you have both a functional wrapper and non-local connections
@grrrck And after this conversation... I've realized the specific use-case I had in mind doesn't need anything extra; I really just need to return a single reactive after setting up observers and whatnot. It's still hard to grok "You can do the observer stuff but then ALSO return a value 'cuz the observers don't need to be 'returned' per se."
I just finished my first read of https://code-review.tidyverse.org/ and I highly recommend reading at least part of it, even if you only plan to open issues in your favorite #RStats packages. It addresses both sides of the PR relationship, as well as how to write good issues (which has inspired me to update our "help us help you" for @R4DSCommunity). It's short enough to get through right away, but long enough to address quite a lot about the process. Strong work, @davis!
I'll lead a new cohort to read https://r4ds.hadley.nz/ (2e) together starting Friday, 2023-10-06, at 13:00 America/Chicago (and then every Friday at that time)! I haven't read 2e cover-to-cover yet, and I know there's a ton of new material!
To participate:
๐ฌ Join our Slack at https://r4ds.io/join
#๏ธโฃ Find the book_club-r4ds channel
๐ Click the Zoom link when it appears there every Friday 10 minutes before the meeting
I wish I could fast-forward my brain from now, when we all love the old #Slack design and hate the new one, to a few years from now, when we will also love the old (currently new) Slack design and hate the new (future) one.
@jonthegeek I need to ask our Slack herder if there is something they did to keep the old interface b/c I've not seen this new interface that's causing folks so much woe.
@hrbrmstr it's rolling out slack by slack. I just got it on @R4DSCommunity last night. It isn't AWFUL, but it's definitely different, and that feels awful for now at least ๐
Soon I'll buy my Super-Fan tickets for #PositConf2024 in Seattle (not available quite yet as far as I can find), but first it's time for one more thread to summarize my threads! Each post in this thread will be flagged with a titled "content warning" to make it easier to find your way back to the top, I hope that works out!
The workshops were a wonderful new experience. I TAed the #TidyModels workshop last year, but I'd never actually participated in a Posit/RStudio workshop. There will only be 1 day of workshops next year, but I definitely recommend finding one to participate in!
@Cmastication is a GREAT speaker. Not that the others weren't also great, but if you can watch 1 keynote, watch this 1. He's both hilarious and insightful.
๐งโ๐ป Biggest value from rise of data science is it's now ok to code outside IT
๐ "Abstractions will leak. Therefore, abstractions must be permeable to allow debugging."
๐ 80-16-4 rule: "No single abstraction is right for everyone." Talk to users!
I don't think I tweeted one of my favorite lines of #PositConf2023, during @hadleywickham 's takeover of @jennybryan' s talk: "ggplot2 is about to turn 18, so it might be time to emancipate it and let it be responsible for its own maintenance." #RStats