From 219291a03214c7dbdfeb06939bd6e875b52b5dc1 Mon Sep 17 00:00:00 2001 From: Craig Maloney Date: Sat, 2 Jun 2018 08:00:19 -0400 Subject: [PATCH] Fleshing out more of Chapter 02 --- chapter02.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/chapter02.md b/chapter02.md index 6f35730..1e9ded9 100644 --- a/chapter02.md +++ b/chapter02.md @@ -22,4 +22,4 @@ There's nothing wrong with reading a post-mortem about a project - we can learn ## Ranking programmers -There are many metrics for which folks rank various programmers. You've likely seen these metrics manifest themselves in competition sites, commits to projects, productivity, turn-around of code, and good ol' gut feelings. +There are many metrics for which folks rank various programmers. You've likely seen these metrics manifest themselves in competition sites, commits to projects, productivity, turn-around of code, and good ol' gut feelings. We do it to ourselves and others. We compare our work against our peers and folks that we admire. But that can lead us to make comparisons that aren't objective or based on all of the data. I can compare myself against folks who do low-level programming and find that I don't measure up in that realm; never mind that I haven't done a whole lot of low-level programming. Or I can compare myself against folks who were mentored by programmers whose names are legendary in the field. Unfortunately I will likely find gaps between my knowledge and their knowledge. Comparisons like this tend to be unhelpful and lead us into punishing ourselves for not being the other person. We look at our projects and our history and find that we're not the other person, nor could we ever be the other person. -- 2.31.1