+1 for code reviews. Plus technical brown bag sessions once a week or fortnight
On Tue, Feb 9, 2016 at 2:09 PM, Stephen Price <step...@lythixdesigns.com> wrote: > I highly recommend doing code reviews. Not only does it improve the > quality of your code base, but its a two way learning avenue. The person > reviewing the author’s code gets to understand what the code is doing. The > Author thinks through their own reasoning while trying to accurately > explain what the code does to the reviewer. Bugs can be found by both > parties and its just brilliant. Doesn’t happen enough, in my experience. > > > > Print the code out on paper, go into a quiet room with GREEN pens. > Psychological effect of RED pens makes you feel like you are being marked > wrong in school. This is important that any feedback is expressed as a > contribution, with a view to improve the quality of the code, not make > someone wrong or invalid. > > > > Your other suggestions are good, but I think there is magic to be found in > code reviews. Take turns, mix it around to make sure everyone has a go in > both roles, and don’t always pair up with the same person. > > > > Good luck! > > > > Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for > Windows 10 > > > > *From: *Dave Walker <rangitat...@gmail.com> > *Sent: *Tuesday, 9 February 2016 10:00 AM > *To: *ozDotNet <ozdotnet@ozdotnet.com> > *Subject: *[OT] Internal Developer Training > > > Hi all, > > I've recently taken over a new team which has a wide variety of technical > skill from complete beginner to senior developer. Talking to the team I've > found that especially their C# skillsets are limited and can be greatly > improved. So far we've organised for everyone to have a pluralsight account > and encouragement is given to spend work time watching videos however it > feels a little bit disconnected. I'd really like to have a more formal > ongoing set of training but as it stands I have no experience implementing > this. > > There is limited budget so can't just send everyone off on a training > course and not really looking for an overnight fix but more of a program > that improves different skills over time to a certain level. > > My thoughts for now were to mix between: > * Book club - everyone reads a chapter of 'Clean code' and we gather > weekly to discuss it > * Pluralsight club - same but with a pluralsight video > * One on one peer programming where the more senior members help the less > experienced > * Demo sessions/lectures by more experienced developers from outside the > team > > Has anyone else ever tried to take on something like this? If so how did > you go about it and what advice can you give about this? > > Cheers, > Dave >
