Reputation
3,152
Top tag
Next privilege 5,000 Rep.
Approve tag wiki edits
Badges
11 27
Newest
 Nice Answer
Impact
~304k people reached

Feb
13
comment How should I manage a team with different skill levels?
+1 for "Be the model." That's been the biggest benefit I've seen in code reviews: learning from other people's slickness. That, and catching the occasional defect.
Feb
13
comment How should I manage a team with different skill levels?
@P.Brian.Mackey: There was no specification of free tools in the question. If the code isn't testable, get them off the team. Try to show them how to write testable code, and if they don't make any improvement, get them off the team.
Feb
13
comment How should I manage a team with different skill levels?
@Jeff O: Then get them off the team.
Feb
13
answered How should I manage a team with different skill levels?
Feb
13
answered Teaching programming to a non-CS graduate
Feb
13
comment How do you avoid being a “blowhard”?
Actually, it's a corollary of one of the Franklin-Covey effective habits: "Seek first to understand, then be understood."
Feb
10
awarded  Editor
Feb
10
comment What is the difference between these senior software engineer titles?
I always wanted to sing "For he's a jolly good Fellow" whenever one of them was around... :-D
Feb
10
revised What is the difference between these senior software engineer titles?
Get second dot list right!
Feb
10
answered What is the difference between these senior software engineer titles?
Oct
23
awarded  Teacher
Sep
19
awarded  Autobiographer
Sep
19
awarded  Supporter