> There is debate about how the therapy works and whether it is more effective than other established treatments.[3][9] The eye movements have been criticized as having no scientific basis.[10] The founder promoted the therapy for the treatment of PTSD, and proponents employed untestable hypotheses to explain negative results in controlled studies.[11] EMDR has been characterized as a pseudoscientific purple hat therapy (i.e., only as effective as its underlying therapeutic methods without any contribution from its distinctive add-ons).[12]
I always assumed EMDR's effectiveness had nothing to do with eye movements.
After 20 years of hoping for a Bell Labs to magically show up again, I now work to emulate this culture but with a focus on energy systems that has the same characteristics as combustion engines but with 10x power/energy-density (and zero emissions).
If this resonates with anyone here, feel free to reach out.
mydata <- read.csv('mydata.csv')
mydata['score'] <- mytransform(mydata['score'])
This can be simplified with your proposed operator: mydata['score'] <|> mytransform()
An upgrade in elegance, i like it. But in R, a language which is commonly used switching between scripts and the REPL, with an IDE which by default captures your workspace so all your variables etc are restored the next time you resume the session, in this environment i feel like variables should be used as constants as much as possible. Mutating a variable (as in my example) creates room for confusion: Does mydata contain the raw csv data or the transformed data? Did i already evaluate this line in the REPL or did i not? What happens if i evaluate this line twice? Many people i know tend to "jump around" in their scripts, not following the written order of operations. This creates potentially irreproducible environments.
My proposed solution is treating all variables (or at least as many as possible) like constants: mydata <- read.csv('mydata.csv')
mydata_transformed <- transform(mydata)
Now i always know what a variable contains because each variable contains exactly the same value, independent of when i evaluate.But nevertheless; i kinda went on a tangent here and strictly speaking, the problem i describe only arises from careless user behavior (which is quite prevalent in statistics though). Aside from this kind of behavior, i think this operator is an elegant idea!