None of us came out of the womb coding great contributions to open source projects.
We coded our own projects, failed, coded another project, failed, coded another project failed⌠found some bug in an open source project, hunted it down, submitted a patch, received feedback, went into deep depression for a few hours, realized they were right, submitted a different version, repeat a few times, develop a thicker skinâŚ
We set out to add some feature, spent hours on it here and there, for weeks, only to have someone faster swoop in with a better version when we were only half way done. Gained further understanding that the code base doesnât care about our feelings, it just wants to be better.
We produced some of our own open source add-ons to something. Sometimes they were accepted. Sometimes they werenât. Sometimes we were humble enough to receive feedback and learned to make it better.
In our professional and open source lives, we slowly learned to break big things into smaller things working towards an end. Surgical strikes that would get us closer to some end goal. Smaller patches that are not only more palatable to a group of gatekeepers but also objectively better over all.
Now, the problem is that folks like that generally have lots of their own itches to scratch⌠and if they donât align with some feature like âdrag and drop codingâ like Unity or âimplement the adapter for the next big 3D file formatâ then nothing gets done on those fronts. However, there is a giant gulf between noob and expert where folks can still contribute⌠by submitting smaller updates, asking for feedback, developing thicker skins, etc⌠That person really just has to care enough and be willing to devote a piece of themselves to the process.
Itâs rare but it happens. Even here. We have quite a few really talented monkeys that help out in lots of ways. (I started to name names but worried Iâd leave someone out by accident.)