r-best-practice
r-best-practice copied to clipboard
Stuff for a possible page 2
- General advice about writing good code - maybe Code Design:
- Write then rewrite
- Clarity first, efficiency/optimisation later
- Clean up dead code!
- Think about API consistency
- {targets}
- More styling guidance, including {lintr} and {styler}
- A dedicated {renv} section
- Git advice...?
- More options for project layout:
- Package-like
- Facilitates use of {testthat}
- Actual package
- {targets}
- Package-like
- Advice about online communities