How do I convince my colleagues to use quarto? #7826
Replies: 5 comments 1 reply
-
If your main outputs are Word and PDF documents and that the argument, about which Quarto allows to include computation directly in the rendered document without copying/pasting anything, does not convince, I don't see what could. If your main output is HTML based documents, then a good argument that usually work very well, is interactivity either directly for the computing languages (R/Python) but also via Quarto with Observable. You could look at the recordings of Quarto introduction in R User group and conferences to get idea of highlight points you could use to target specifically your colleagues. |
Beta Was this translation helpful? Give feedback.
-
In my experience |
Beta Was this translation helpful? Give feedback.
-
I think it really depends on where your colleagues are coming from. If they use Jupyter notebooks, you might want to focus on the language agnosticism that Quarto enables, or on We're on the reproducibility concerns that Quarto and Rmarkdown sidestep. If they're already using Rmarkdown, then showing off layout features or OJS might be the go. If they're using Word and Excel, then doing a post-mortem on a graphic that had to be repeatedly built in Excel to accommodate changes in upstream data, or on a report where content was lost between revisions, might help your colleagues appreciate the value (in time and money) of version control and reproducible graphics. Good luck! |
Beta Was this translation helpful? Give feedback.
-
Maybe the best strategy would be to ask a few colleagues directly (selected for their frank but open-minded feedback), why they're not convinced/enthusiastic. It might be something entirely unrelated to Quarto's capabilities – maybe they do find it impressive but to them it looks very complicated (e.g. they're not familiar with plain text editors, or the command line, etc.) Having those discussions might suggest practical steps to get more people excited, such as teaming up on a small project with someone who's not yet a quarto user. |
Beta Was this translation helpful? Give feedback.
-
Thanks all for the responses. A lot of the issues with uptake I believe is the perception that it's difficult. I use the VS Code Quarto extension and mostly had to setup dev-containers for quarto to bundle the dependencies, this makes a fairly easy one stop shop, but even then, repeatability is sacrificed for ease of starting (i.e. a docx) and cut and paste figures. One consistent statement that I hear against using text base solutions is the ability for docx docs to be edited/monitored by multiple engineers concurrently and changes tracked automatically. I've had a cursory look at some live sharing extensions in VS Code, and use version control, but the latency it problematic. Once again, I appreciate the inputs. |
Beta Was this translation helpful? Give feedback.
-
Description
Hi. I've been using some form of reproducible research principles for around 10 years. Started with Sweave, then moved to knitr. With Quarto and being able to seamlessly integrate python and R into live/traceable documents, I feel that Quarto is now a very a viable option within my industry (Maritime Engineering Consultancy) for document generation within projects. I've demonstrated a couple of qmd files in the office, but, I'm not quite getting the reactions or the traction that I expected.
Long story short. How do I go about pitching the benefits of quarto (and reproducible/traceable research) within my industry or outside of academia/statistics?
Beta Was this translation helpful? Give feedback.
All reactions