1. 5
  1.  

  2. 3

    I think this is why interoperability is really important. Otherwise we get everyone re-inventing the wheel.

    It’s better to have 10 hero projects that work together and add up to 10x the value, rather than have 10 hero projects that do the same thing in slightly different, incompatible ways!

    It’s definitely true that you can go faster / write fewer bugs with your own code. Kinda unfortunate too but I don’t know a way around it. I think this is especially true in open source where you’re doing it for fun and not being paid.

    1. 2

      My github project is a “hero” project, at least by this author’s definition. I have a preference for the libraries i depend on to be small, clean and easily understood. In practice, that has meant most of my dependencies are also “hero” projects. I like knowing that if I find a bug in a dependency, then I could fix it myself (because it isn’t millions lines of code), and that there is a high probability that the project maintainer will be responsive to bug reports and pull requests.

      Stories with similar links:

      1. Why Software Projects need Heroes (Lessons Learned from 1100+ Projects) via 355E3B 2 years ago | 14 points | 8 comments