Hacker News new | past | comments | ask | show | jobs | submit login

What's your alternative plan for when a dependency is discovered to be broken?

I've done Josh's plan a bunch of times. It's why I prefer my dependencies to be open source. Everything is broken, but if it's open source, it's easy to fix it when it's noticed, push to production to fix it for my users, and send a PR to fix it for the world (eventually, if they take my patch; not everyone does, but I've had many accepted)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: