Last year, I was trying to teach my 2-year old son to go up the stairs using both feet. He would get his right foot up and push on his right leg with enough strength to lift himself up, but strangely never use his other leg. I remember feeling somewhat frustrated:
OK now the other leg! No, no, not that one! …
I tried a few different things over a period of weeks, but ultimately, it was positive reinforcement that did the trick. After using his right foot on the first step, I cheered him up and complimented him:
Allright, great job buddy, way to go!
He paused for a brief moment as he listened to my cheers and then, out of nowhere, lifted his other leg, and climbed another step! I cheered even louder as he started going back and forth. My son was more driven by positivism than by other means of education.
Applying this concept to software engineering can be very valuable. Code reviews usually solely focus on what needs to change, and it can sometimes feel disheartening when lots of things need changing. Taking the time to highlight the good parts during code review usually yields faster reaction time and quality response. To praise someone’s piece of code shows appreciation for one’s intellect. It increases self-esteem and confidence, it boosts morale and generates a desire to become a better coder.
Byron says (December 23, 2014 at 10:06 pm):
Sean says (December 23, 2014 at 11:29 pm):
Aivar says (December 24, 2014 at 10:01 am):
Kent says (December 24, 2014 at 10:22 am):
Lars Clausen says (December 24, 2014 at 1:35 pm):
Comments are now closed