Ain’t got no time to work for free. - The codebase is huge, I don’t understand a shit - I can’t do build on Windows? No thanks. - I need to install linux, learn git, X language, Y framework, a long way to go… - How do I build this thing? The builds fail :( - IRC is boring. Why are people too busy to respond? - Do I really need to do all this? Why can’t things be simple?
1 + - I did terribly last time. I had to do something. - I didn’t wanted to work for a health insurance company. - Competitive programming is not my cup of tea. - Zomato hires GSoCers. = I got a New Year resolution.
Project 2: Didn’t actually had any project to build and work. Project 3: Built, but poor code. So I rejected. Project 4: Google rejected it. Project 5: Was accepted for first time. Also, felt cool. Project 6: Had the most active community.
softwares that thousands of people use. - Writing code matters, but being able to read and review other people’s code matters even more. - Made me regular with writing and maintaining my blog. - That things may seem daunting and huge first, but if you try to stick with it, they become much easier. - Proper design and tests are there for a very good reason. - GSoC a full time thing. Think thrice, before doing it with an internship.
experience of contributing to Open Source projects that helped me a lot. - Writing efficient code - Community - People smart than me to work with - Pushing me for things that I wouldn’t have learned otherwise. - Internships, freelancing, conferences, etc
ask to select. People will often help only when you actually need help. The more you help others, the more you’ll be helped. Having a quality proposal is way more important than number of commits or Lines of Code merged.