Maintaining the house the tidyverse built
summary
Code maintenance frames tidyverse work with a clear lifecycle and concrete promises: experimental, deprecated, stable, superseded guides when APIs may change and when they stay compatible. Deprecated functions warn (example: data_frame deprecated in tibble 1.1 with advice to use tibble and a lifecycle::last_warnings() backtrace; warnings throttle every eight hours). New APIs replace old ones (example: pivot_longer()/pivot_wider() supersede gather/spread but old functions remain). Big changes (magrittr pipe rewrite) are tested across CRAN, blogged and rolled out; use renv or CRAN time snapshots to lock versions for production.
AI-written summary · about
chapters (11)
- 0:00Intro
- 1:08Dealing with frustration
- 6:58Tidyverse life cycle
- 8:42Breaking changes
- 10:32Deprecation
- 14:20Sub superseded life cycle
- 16:34Building codes
- 18:48Offlabel usage
- 21:38Avoiding offlabel usage
- 24:17Unforeseen consequences
- 30:01Conclusion
related talks
29mGrammars of Data: lessons from ~20 years of the tidyverse
33mUnderstanding Maintenance as a Turing Way
47mProject Talk: Maintenance Update
01h 17mDevelopment strategies: You've written a library - now what?
03h 40mMaintainers
58mResponsibly Abandoning Open Source Projects
01h 00mMaintaining a Library and a Community
34mStaying Current A Journey in Software Maintenance