jacob.windle/blog
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Formatting issues

Browse Source
This commit is contained in:
Jacob Windle 2017-12-26 16:32:49 -05:00
parent df6b6ce95a
commit 4247ac4d79
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
content/post/managing-a-team.md
View File

@ -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