On Tue, 19 Jul 2016 08:16:05 PDT Matt Aimonetti <mattaimone...@gmail.com> wrote: > > I just wanted to point out a post I published today talking about the fact > that we are often leaving new / less experienced Go developers high and dry: > https://medium.com/@mattetti/go-is-for-everyone-b4f84be04c43 > > I'd love to see what you all in mind to help new or junior developers. > Maybe share some of the pain points you've experienced or seen (for > instance setting up the Go path, finding resources to get started etc...) > I'm thinking about a bunch of very short posts on basic topics and maybe a > real beginner tour of Go. We are going to do a beginner night next month at > our LA/Santa Monica Go meetup and hopefully better understand what the > current pain points/blockers are. > > What do you think?
What worked for us: @ Work review of code written by anyone in my team *had* to have my ok before it could be committed. Initially people *hated* it and it added a lot of work for me. But this allowed me to provide specific help on every little or big thing they ran into. In addition to detailed comments explaining why something needed to be done differently, I pointed them to pertinent online documents/tutorials/talks etc. And I added make targets for go vet, fmt, race, test, coverage etc. that they had to run before submitting a code review. In addition we had a local "developer's guide" with links to various things that they started with. I think what helped the most: a) they *had* to actually do the work I suggested or argue why their way was better or discuss design issues in some depth. b) they could reread review comments & dialog. Basically all the good intentions are not enough if you don't actually do the work and I needed to give them an incentive to do so! Pretty soon the person who hated it the most learned the quickest way to get through his reviews + his reviews of other people's code were as tough as mine so now he and I share the code review load. We will add more people once they reach the level I want. Anotther thing I learned is that people use a looming deadline as an excuse to slack off and once the code is committed, their enthusiasm for fixing things goes way down. So I have to stop being the nice guy on reviews! As it happened, nobody other than me knew Go when we started out and we had a number of junior programmers but by now I think we do a decent enough job. [BTW, we *are* looking for seasoned Go programmers! email me if interested] Not suggesting this is what others should do; just stating my experience. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
