3 ms·
> making the feature up This is super hard, often someone will write a mindless issue with a feature request without thinking about it profoundly. Than the de
by a1o 3y ago
> making the feature up
This is super hard, often someone will write a mindless issue with a feature request without thinking about it profoundly.
Than the dev has to sift through the text to understand what is the underlying problem the user is facing, if the proposed solution is actually a good solution to that problem (it often isn't), what is a solution considering long term maintenability, if the feature has synergy with future features or if it solves or is close to solve other already existing issue so the solution scope should be adjusted. The design stage is huge and it's hard to do alone and also hard when other contributors only raise edge cases to try to break a proposed design without validating if the problem the developer extracted is adequate. The scoping and design is often very time consuming and hard to get it right. Usually you end up designing to the scope of available time to solve the issue at hand - time being a rainy Sunday afternoon, or around three and half hours.
- bombcar 3y agoWhich is why you can be entirely helpful in an open source project even without knowing how to code. If you can learn the general program, and interface with the users as a liaison between the developers and the bug tracker, it can be quite valuable.
- mortenjorck 3y agoAs a product designer, I naturally agree with this, but... are there any instances of this actually happening? I suppose there's Blender, but it's kind of a special case.
- MichaelZuo 3y agoAlso there's the possibility to help in writing documentation.