The Upstream Tax
A competent engineer adopts a long-term perspective on ecosystem maintenance. When patching bugs or extending features in open-source dependencies, avoid maintaining internal, custom forks. Commit to dedicating time during your development cycles to package, document, and submit those modifications back upstream.
Paying this “upstream tax” ensures that the core tools your team relies upon are maintained communally, reducing your internal maintenance overhead and enriching the commons.
Discussion: Private workarounds might seem faster today, but they rot. Pushing improvements back to the main repository saves the wider community from debugging the exact same problems you just solved.
You might ask yourself:
- To what degree do we give back to the projects that make our work possible?
- To what degree do we make upstream contribution part of our normal delivery practice?
Want to assess your full organization? Take the full assessment
Comments