Rounding out my three-part ETL series form Airbyte's developer blog
Cross-post from guest post on Airbyte's developer blog
Simple, self-contained, reproducible examples are a common part of good software documentation. However, in the spirit of brevity, these examples often do not demonstrate the most sustainable or flexible workflows for integrating software tools into large projects.
Marketing maintenance work with irrational exuberance
Using controlled dictionaries for low-touch documentation, validation, and usability of tabular data
Don't believe the documentation! Shiny modules aren't just for advanced users; they might just be a great entry point for development
A walkthrough of using the projmgr package for GitHub-based project management via R
A recommended tech stack for implementing RMarkdown Driven Development
An annotated bibliography of advice for getting started with reproducible research
A workflow for refactoring one-time analyses to sustainable data products