My journey as open source contributor #1
In the current world it is very hard to stand out of the crowd. When we apply to the job many times we do not get response, one primary reason could be the recruiter do not feel the candidate is capable enough/suitable. I was struggling from few months how I can step up my game by acquiring new skills and become more capable, so I did some courses on Coursera, Edx, Udemy and other learning platforms, and to my surprise I was shortlisted for interview based on my recently did courses. But during the interview when recruiter realised I have not worked on any practical problems and have just done the basic course and tutorials he turned off, and as expected I did not got selected.
I faced this problem, how can I cherish the fruits of the new learning I do apart from my regular job. Because you are doing it in the dark, no one knew about it, and also you do not have practical experience so that you can showcase your skills and recruiter will believe it. Following the mantra “whenever you face any problem, ask for help” I talked with the friends and come to the solution that I should work on open source project. It has many benefits, first thing whatever contribution you make, your get credit, but the most important benefit I think is the smart people you acquainted with. They are the people who have already travelled that path, they are the people like whom you want to become. I feel, the successful career is you should be identified due to your work and capability and not because of your position within the organisation.
So I have decided to become a open source contributor. This is my first day. I am novice in programming and I am from non CS background. In this journey I felt that I should document my journey, so that I can read it later, and look how I was at that time.
These posts are not for giving knowledge to others but this is my notebook to document my journey. The files on personal laptop or in hard copy I may loose in unforeseen event but the cloud hopefully will remain till I get old.
Done with the creating profile on Github, done with the installing github desktop on the laptop.
Very funny event happened, I forked one package to my github account and just to play with github, I modified readme file and created pull request. I thought the change will get added to the forked directory only. After sometime I felt may be I have made the mistake, it may go to the original package, so I called my little experienced friend about it he said he works on branches and after testing they merge the changes and he was not sure what will happen, he said he will check and hanged the phone. And to my nightmare I got the mail from prime developer, asking what are you trying to do? it was a mixed feeling for me, fear for making a mistake and getting scolded by developer and happiness for getting chance to talk to one of the best developer of that package who do not interact personally and only talks on forum for answering the tough technical questions. I told him sorry, I was playing with it, blah blah… to my surprise he was kind, and said you can play in PRs by selecting your own branches of your forked directory. Now I have to decipher what he meant by that. But it was great experience.
Currently I am facing one problem, when I look at the package that I have forked, its huge, I am not getting hint where to start to understand the package. Its basic structure, its logical tree, all the branches and all. Its a pure python package. I have to figure it and make a note of it here.