A fixed wheel counts as a brake, though I've only seen the law in relation to bicycles which require 2 working brakes not sure how this applied to unicycles.
The increasing prevalence of non-standard evaluation in R packages was one of the major reasons I switched from R to python for my work. The amount of ceremony and constant API changes just to have something as an argument in a function drove me mad.
If you've ever had to deal with the UK police as a victim of a crime, you'll quickly find out they're pretty useless at obtaining CCTV footage. I was asked to get it myself, to which the business who owned the CCTV told me they would only hand it to the police, so nothing happened.
Yep, at one point in my life I was consistently cycling for 30 hours a week and eating enough became a chore. So it's definitely possible, but it requires enough exercise that's essentially a full time job.
The choice of groovy was unfortunate, but yet it still seems more popular than snakemake which I can only attribute to the nf-core set of curated workflows.
I have a dislike of nextflow because it submits 10s of thousands of separate jobs to our HPC scheduler which causes a number of issues, though they've now added support for array jobs which should hopefully solve that.
My biggest issue with R package management is version pinning. If I specify an older version of a package, R will fetch the latest versions of all its dependencies, regardless if they're compatible or not, which leads to manually chasing down and re-installing specific versions of dependencies and sub-dependencies one-by-one.
Microsoft's CRAN time machine helped solved this, but I think they've recently shut it down and I don't really trust Posit to not have a version behind a paywall.
They can invite whoever they want, but I think they will struggle to attract talent unless they actually start making some changes to make it a more attractive option rather than just assuming elsewhere is going to get worse.
I did a post-doc in France after my PhD in the UK. It was possibly worthwhile just for the experience, but the actual funding and research environment is not one I would recommend to my colleagues.
A 63 watt average must have been taking into account all the time you weren't pedalling, that's extremely low - you would struggle to ride into a slight breeze.
We tried plumber at work and ran into enough issues (memory leaks, difficulty wrangling JSON in R, poor performance) that I don't think I could recommend it.
Happens with R as well where everything gets dumped into a global namespace. It's a huge mess.
If you're lucky all functions will have a common prefix str_* or fct_*. If you're unlucky then you have to figure out which package has clobbered a standard library function, or the exact ordering of your package import statements you need for your code to run.