I absolutely felt the same, but basically made myself take a look at the go[1] issue tracker[2], before just committing to working on a bug. Once I got one fixe

I absolutely felt the same, but basically made myself take a look at the go[1] issue tracker[2], before just committing to working on a bug. Once I got one fixed, it was an amazing feeling - I can contribute to this project that is run by people from goddamn bell labs, legends in the industry[3], etc. - though my contribution may be small, I was able to fix something. Getting past that first hurdle was just amazing Theeeeeeen I tried a more serious bug[4] - the only high-priority one in the whole tracker which hadn't been solved for over a year (yeah. Maybe a bit over-ambitious). After hours of learning C and the codebase (my day job is as a financial CRUD C#-er) I was able to find a way to fix it :-) It has genuinely been a voyage into the unknown and taken quite some effort + despite feeling utterly not up to the task, but being able to contribute even minor changes to a project you believe in is just the most amazing thing, really. So I am with @briancurtin on this one - just push yourself to try it, it's genuinely worth it. Knowing you contributed something to a project you care about is just damn awesome. Seriously :) [1]:http://golang.org http://golang.org [2]:http://code.google.com/p/go/issues/list http://code.google.com/p/go/issues/list [3]:http://en.wikipedia.org/wiki/Rob_Pike http://en.wikipedia.org/wiki/Rob_Pike [4]:http://code.google.com/p/go/issues/detail?id=667 http://code.google.com/p/go/issues/detail?id=667