luke.arundel@taso.org.uk.
LA - if you would rather this isn't your personal email, we could direct to the research@ inbox. Let's discuss
8 Matching Annotations
- Feb 2024
-
lukearundeltaso.quarto.pub lukearundeltaso.quarto.pub
-
-
lukearundeltaso.quarto.pub lukearundeltaso.quarto.pub
-
Coding practices
What do you think about adding a tip here to explicitly specify dependencies? Something like - explicitly specify dependencies in your code using a description file (for packages) or a readme file (for scripts). This helps users understand what packages are required and aids reproducibility.
-
4:
Footnotes come after punctuation - please amend
-
improve readability
This should read 'improve the readability . . .'
-
-
lukearundeltaso.quarto.pub lukearundeltaso.quarto.pub
-
butitsuremakesthingseasiertoread.”
Haha, nice quote
-
-
lukearundeltaso.quarto.pub lukearundeltaso.quarto.pub
-
s3.
Footnotes after punctuation - please amend
-
-
lukearundeltaso.quarto.pub lukearundeltaso.quarto.pub
-
choice.
Luke, what do you think about adding an e.g., to show the options and accessibility and encourage adoptions. E.g., RStudio or Excel
-
TASO Technical Hub
Double check with comms, are we happy with this name for the resource? 'Hub' fits with the idea that we have multiple hubs - the SMH hub, for example. An alternative option is to call it 'TASO Technical Guide'
-