3 ms·
> …better than you think you can build it? If it's open-source, see where you can contribute, for example, documenting the code or adding a feature you think t
by metasean 11y ago
> …better than you think you can build it?
If it's open-source, see where you can contribute, for example, documenting the code or adding a feature you think they're missing.
If it's not open-source, see if they're hiring. In your cover letter mention that you had a similar idea, but it differed in x, y, and z ways, and include the pros and cons of your your different features and implementation methods.
- yeukhon 11y agoGood points, but always depends right? I need this tool and it happens someone has done the dirty work and will take forever for me to DIY (it requires a lot of research and understand how X works). I used the tool, and I found a bug which affected usage, and I fixed it because the tool was opensource. But I always note I don't actually decide what goes into that software. I can argue about why X feature is needed or why Y should be implemented in Z way, but I don't own that repo. Of course this is the beauty of open source just fork it (with the cavaet of watch the license which many probably doesn't care or doesn't have the knowledge to understand what X license mean to a user and to a contributor). But if I were to test my own ability and feel proud "yes I build it from scratch" I will build one from scratch. There is just that one idea that "I wish I was famous and getting tons of likes and respects because I built something that hundreds of developers are benefiting, being original creator vs a contributor.