5 ms·
> Please, to save your own time and energy (if not the time and energy of other people) search for a solution before you build one. Only if you have found the t
by Myrmornis 11y ago
> Please, to save your own time and energy (if not the time and energy of other people) search for a solution before you build one. Only if you have found the two or three solutions that the community likes most and you are still unsatisfied, only then start coding.
I hope no-one reading this thread gets the impression that most open-source software engineers would agree with this. That's one of the beauties of the ecosystem -- everyone can code and publish what they damn well want.
> I really want to support open source efforts. But I really can't if there's a project developed without any googling before the first line of code.
How is your "support" of open source software negatively impacted by this, as you perceive it, malpractice? It makes choice of OSS solutions harder for you?
- erikb 11y agoYes, most agree with this. Before there was google it was called RTFM. And of course everybody can do what they want. There won't be an exam tomorrow of how many people have read my comment and got to the conclusion that yes, to provide value to the community it's a smart thing to find out what the community has produced first, and distinguish your addition. Could you say the author didn't care about what he adds to the community? Sure you could. But then one had to wonder why he added his project to HN or wrote a Readme in the first place.
- Myrmornis 11y agoThere are several things you are not getting. One of them is the totally unnecessary barrier to entry that your attitude would create. This is a community that is attempting to make itself more approachable and enterable, not less. There's nothing wrong with reinventing the wheel in your own time, especially if you learn from the experience.