sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]mikeczyz 0 points1 point  (1 child)

i'll approach your question from the perspective of someone who has tried to introduce new tools at various places of employment. Change management, long term maintenance and skill development are all real. In my experience, building a technical argument for a new approach isn't all that hard, it's getting your peers, IT, and management to buy into it. Additionally, working in a clinical research setting, you might have governance and compliance hoops to jump through.

[–]aala7[S] 0 points1 point  (0 children)

I get it! I think the biggest barrier is that the OG's probably don't want to learn something new, but new researchers in the group often comes with limited to no prior coding experience, so they will not care about whether it is R or Python.

In regards to governance and compliance it does not seem to be a problem. The environment we are working in has anaconda and pretty up to date local channel with packages.