From 4247ac4d791d0b0ad88712866ef24a4d743fff55 Mon Sep 17 00:00:00 2001 From: jaketothepast Date: Tue, 26 Dec 2017 16:32:49 -0500 Subject: [PATCH] Formatting issues --- content/post/managing-a-team.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/post/managing-a-team.md b/content/post/managing-a-team.md index a5e80c5..78adb22 100644 --- a/content/post/managing-a-team.md +++ b/content/post/managing-a-team.md @@ -56,7 +56,7 @@ share some anecdotes, and lessons I learned from being a manager for 3 months. ## Lessons learned -1. Prevent knowledge "Silos." +### Prevent knowledge "Silos." We had a member of our group, who I shall call Kevin. Kevin was a genius student when it came to computer science theory. However, Kevin was very very quiet. He would sit during our meetings @@ -72,7 +72,7 @@ junior programmer's coding skills. I was very happy at the end of the year to se programmer asking Kevin for reviews of his code versus asking Kevin to fix it, and Kevin would provide thoughtful, constructive feedback to the junior. -2. Intrinsic motivation is very powerful +### Intrinsic motivation is very powerful The junior members of my team often got very discouraged when they could not tackle hard problems. It would take one of them days to do something that Kevin could do in an hour, so keeping them @@ -88,7 +88,7 @@ and would hit deadlines more consistently and often early. He cited in his final leadership that feeling supported and valuable made him want to do more with the project, more than tangible rewards that were given to him. -3. Provide a visualization of work being completed. +### Provide a visualization of work being completed. What was very important to me as a hybrid manager-developer, and to the people on my team, was progress. It was important for my teammates to be able to see that we were actually getting work