6 ms·
This is the most depended upon node module on npm, this is not some beginner engineer - I think this belongs here.
by abritishguy 12y ago
This is the most depended upon node module on npm, this is not some beginner engineer - I think this belongs here.
- hawkice 12y agoIf the purpose is to alert people to perhaps subtle bugs in their code, then clearly it's relevant to the engineers here. But if your point is that we should publicly highlight mistakes (or things we don't like) in packages because we expect people to do better... then I guess I should step out of this conversation. I don't want to talk highschool about someone building cool things.
- deleted 12y ago[deleted]
- akerl_ 12y agoThe connection between a project's developers and its community is noteworthy and worth discussing. As a developer, how you treat your user base is relevant, and has a real impact on the value of the thing you have produced. We have successful projects whose leaders vary wildly in style, from Linus's approach to kernel development to projects that delegate final code control to community contributors. Talking about the human elements that factor in to technology has merit; talking about the best ways to handle a project's community has merit. It's not "talk[ing] highschool".
- rubiquity 12y agoWe could also submit a link to your issue on GitHub with the title "Engineer Mindlessly Updates Dependencies and Deploys Without Testing, Shocked to Learn Application Doesn't work."
- abritishguy 12y agoI started a new repo and wanted to know why several of the dependencies were not working, only way to fix it was to manually change the underscore version number in these dependencies - obviously you wouldn't just push an update to production without testing it.
- grayclhn 12y agoI think you'd find that it falls off the front page pretty quickly.