3 ms·
People are too quick to dismiss other's work when they don't know how hard it is or have done anything significant in the same field. Once dismissed, it becomes
by thrwaway69 7y ago
People are too quick to dismiss other's work when they don't know how hard it is or have done anything significant in the same field. Once dismissed, it becomes
a matter of what they feel about it at face value.
To everyone, it seems programmers write 500 words SEO spam posts so not worth much or hard. They can program the same if they wanted to.
(Note - SEO spam posts here refers to subjecive low quality code, duplicate of existing solutions or very similar to what you can do by combining two existing tools.)
Perception or feelings like above are quick to convey so they get conveyed.
Spitting out code is not the hard part of open source imo. It's dedication, commitment, building a community and sustaining feedback. If I am writing software to solve trivial problem, then it wouldn't take me much time but if I am writing software to solve trivial problems for others, It would take me tremendous time to write insignificant piece of code because it needs to be documented, accessible, thoughtful, clean, hosted, testable, branded (naming is one of the hard problems, after all.) and pass through many such criteria.
It doesn't need to but most people who love open source feel this way about their projects.
It's hidden. It's not visible to someone who just created an issue. Somehow we live in meritocratic ideals but forget that meritocratic solution on their own don't get much attention. Without a good readme, a lot of people simply ignore the project. We are actively optmized to go through ton of information that it de-empathizes us to human touch or mistakes. It's quick to notice a typo and make an insignificant comment about it because you can't focus on everything. Anything unexpected is a distraction and we get easily distracted, thus sometime vent on meaningless things.