HackerTrans
TopNewTrendsCommentsPastAskShowJobs

REDS1736

no profile record

comments

REDS1736
·11 เดือนที่ผ่านมา·discuss
Sorry for the off-topic question but would you mind to elaborate on why you can't stand ggplot? I personally haven't spent too much time with the r base functions but have come to absolutely adore ggplot for graphing and am thus very interested in learning about potential reasons to use r base plotting functions instead!
REDS1736
·2 ปีที่แล้ว·discuss
Maybe your keyboard was a contributing factor? I had wrist pain typing in vim on a "regular" (Keychron C1) Keyboard. The wrist pain is gone since i use a split keyboard (Ergodox EZ) which allows me to rotate both halves of the keyboard in order to match the "incoming angle" of my forearm which removes the need to constantly bend my wrists outwards.
REDS1736
·2 ปีที่แล้ว·discuss
Wow that looks amazing, thanks for telling me about this!
REDS1736
·2 ปีที่แล้ว·discuss
The hypothesis is that mental rotation as one way to induce high cognitive load hinders my brain from plaguing me with intrusions. As my sibling commenter already stated, this mechanism's evidence level is "unproven hypothesis" but on top of that, the hypothesis does not explicitly assume mental rotation to be the only effective task for this use case because there are a lot of other very brain-consuming tasks.
REDS1736
·2 ปีที่แล้ว·discuss
I support your assumption. The mechanisms of how EDMR affects the PTSD symptoms are still debated, but indeed a quite prevalent opinion (which i also subscribe to) is that EMDR is not at all about the eye movements but about the exposition therapy happening concurrently. Exposition has been robustly proven to be effective at PTDS treatment and as far as i know, there is no rigorous evidence for EMDR having more effect than standalone exposition, highly suggesting that the exposition part is what makes EMDR work.
REDS1736
·2 ปีที่แล้ว·discuss
Why is that? I'm genuinely curious. Also, what languages / environments do you prefer?
REDS1736
·2 ปีที่แล้ว·discuss
Just a heads up; the "About Morten" page of your website is just lorem ipsum
REDS1736
·3 ปีที่แล้ว·discuss
I agree with you proposing this operator to simplify the specific (but not uncommon!) situation you describe. But i don't think, it exposes a problem to be solved but rather an antipattern to be avoided. Consider the following example in which mytransform is some function i want to apply to a part of the dataset:

  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!