The cost of maintenance, coupled with a lack of intrinsic motivation to maintain, is why large open source projects tend to become modular as they grow. Composability, counter-intuitively, reduces maintenance costs by allowing replacement or recombination in the face of higher maintenance costs.
Working in Public: The Making and Maintenance of Open Source Software
from Nadia Eghbal đź“•
Filed under:
Same Source
- Bigger projects often use a formal “request for comments” (RFC) pro...
- At minimum, open source projects hosted on GitHub can be broken int...
- Developers don’t contribute to open source for lack of technical ab...
- MAINTAINERS are those who are responsible for the future of a proje...
- This innate duality—software visible as both a fixed point and a li...
- Code is not a product to be bought and sold so much as a living for...
- Paying a maintainer for their attention can also translate into ful...
- View all
Related Notes
- Deep and shallow modules: The best modules are deep: they allow a ...from John Ousterhout
- > Software with fewer concepts composes, scales, and evolves mor...from oilshell
- Part of what makes LoRA so effective is that - like other forms of ...from Dylan Patel
- The `io_uring` interface works through two main data structures: th...from Glauber Costa
- Inventory should be kept at the lowest-value stage possible [[Hig...from Andrew S. Grove
- For large-scale software *systems*, Van Roy believes we need to emb...from Adrian Colyer
- More generally, Van Roy sees a layered language design with four co...from Adrian Colyer
- **Designing for Disassembly** ensures that all elements of a produc...from xxiivv.com