2 ms·
Every day, every month, every year we prioritize code contributions and eschew the non-code work that goes towards supporting code, we’re driving away people wh
by uiri 10y ago
Every day, every month, every year we prioritize code contributions and eschew the non-code work that goes towards supporting code, we’re driving away people who believe in open source, who could be contributing.
The claim that documentation and testing are eschewed is patently false. Every software professional is well aware of their importance and when there is a related deficiency in one of their projects. Documenters, code reviewers, testers, and security folk need to know the codebase as well as anyone in order to properly document/test/review/pentest the code. While it is nice that artists, managers, organizers, and fundraisers want to get involved, they are not always relevant to smaller open source projects (which tends to be most of them).
I don't mean to minimize the experiences of the author, but perhaps she would do better to perform a security audit of her favourite project than to write a blog post about how she feels marginalized (not that the two are mutually exclusive, of course).
- nebabyte 10y agoIt sounds just as likely that you're in a bubble where it sounds like a "patently false" notion - It varies heavily by project, and as you check out smaller (and not necessarily niche, unfortunately!) teams' projects, it becomes increasingly likely that the ad-hoc'ing/prototyping patterns - that can indeed eschew 'details' such as testing/docs/maintainability in favor of 'shipping and adding features' - exist (and can even flourish, depending on the dev). While fortunately as these projects grow the 'rest' of a process model is introduced by others in the community, it's certainly lacking enough to the degree that calling it 'patently false' would be at all accurate.