The irony indeed. https://scholar.social/@ccamara/113911195363266854
=> More informations about this toot | View the thread
@josh listening to Computer Future, and really enjoying it. First time listening to Velociraptor and you guys do really well!
=> More informations about this toot | View the thread
So maybe the SA government could improve public transport infrastructure so people don’t need as many cars? https://c.im/@ABC/113858917590243796
=> More informations about this toot | View the thread
Well done ABC. https://c.im/@ABC/113801586516165048
=> More informations about this toot | View the thread
So, I’m trying out Apple Music after struggling to find new and interesting music on Spotify (and seeing that they’re going all in on AI content generation) and I have come across more new music in a week than I did in my efforts to search for stuff I’d enjoy. Time to convince the rest of my family that I don’t want to pay for crappify.
=> More informations about this toot | View the thread
@phocks I had an idea about how we might be able to increase the range of vegan products at our supermarkets. We need a bit that searches for vegan products, but does it from a TOR browser to create a range of IPs to look more authentic. A nice little side project 😉
=> More informations about this toot | View the thread
@coolbutuseless any tips on ansi styling data.frames?
=> More informations about this toot | View the thread
[#]rstats I’ve been really loving the {cli} package lately for command line messages like errors and warnings. Anyone got tips on how to incorporate the styling in a custom print.data.frame() function?
=> More informations about this toot | View the thread
We’ve had a few recent cases where for one of our steps we didn’t check the detail of one of those functions which caught us out. (2/4)
=> More informations about this toot | View the thread
So I’ve been thinking about design patterns for targets, and how users can protect themselves from the mistakes we’ve made. For now we’ve come up with the concept of foreground and background information. Things that can change per project should be in the foreground and should be a parameter to the function that creates the target. Things that won’t change can remain in the background and only be adjusted/improved/fixed as you encounter systemic issues with your projects. (3/4)
=> More informations about this toot | View the thread
The other part that supports this, is if you need to customise a function we use an extra_data list object to pass these parameters/objects in as it means you’re not needing to change your function definition every time you need to do a minor customisation for a single project.
Bear in mind that this is probably only helpful if you’re creating targets pipelines that you reuse across numerous (maybe just a few) projects. (4/4)
=> More informations about this toot | View the thread
Time for another {targets} post today. One of the design patterns we’ve used for a long time is to push as much into a function as possible. If it’s a fairly standard step then parameters are limited. There are some steps that we have that we ‘just know’ will need to have the function updated for the project we’re working on so these too have limited parameters. A 🧵#rStats #targets (1/4)
=> More informations about this toot | View the thread
So {targets} is a great package, but sometimes it creates friction when working interactively. So today, I made a little helper function to load a selection of targets. It allows me to bind this to a shortcut key in VSCode that will load all the highlighted targets.
So far, it is going very well for when I am debugging a function and need to load a bunch of targets into memory. #rStats #workflow
=> More informations about this toot | View the thread
I am trying to avoid the following:
myfun <- function(a = VALUE1, b = VALUE2) {
first_package::myfun(a = a, b = b)
}It seems silly to redefine the function when I could maybe somehow pass parameters when I re-export it.
Any guidance is welcome (2/2)
=> More informations about this toot | View the thread
[#]rStats hive mind. I am trying to piggyback off a function that I have in another package, but I need to pass some parameters relavant to the package I am importing to. I would love to know how I might be able to do this, and if I can the masked function messages to stop when I load both packages.
the normal call to my function would be myfun(a = "valuel1”, b = "value2”)
In package b I have variables set as:
VALUE1 <- “my first val”
VALUE2 <- “my second val” (1/2)
=> More informations about this toot | View the thread
[#]RStats @jonocarroll I managed to get a ntfy server running behind my tailnet that I can use your very cool {ntfy} package with. Thanks for your time investment in making this happen. 🎉
=> More informations about this toot | View the thread
Friday feels
=> More informations about this toot | View the thread
[#]rstats did you know there is no need to join bluesky to find #RStats. If you want to move somewhere to find people who use #RStats /#Rlang there is the perfectly good rstats.me server. No starter packs required, find some cool people talking about R. Also, No VC funding to claw back an investment later.
=> More informations about this toot | View the thread
I might have to do a new desk pic today with the monitor that is making its way to me today. @adamhsparks @lwpembleton
=> More informations about this toot | View the thread
I am currently reviewing some code, and am curious how people balance everything becomes a function vs just write code and let it run. I am familiar with the rule of ‘do it 3 times make a function’ but I have also heard the idea of wrap it in a function and give that a meaningful name. I have seen this latter approach taken to extremes on a recent code base which made it harder to navigate. What’s your approach? #RStats
=> More informations about this toot | View the thread
=> This profile with reblog | Go to danwwilson@rstats.me account This content has been proxied by September (3851b).Proxy Information
text/gemini