X-Git-Url: https://jxself.org/git/?a=blobdiff_plain;f=chapter02.md;h=6f35730dc273a7dff49fbe5f4fca2afb3b3fb28d;hb=80dc3f1dd0636af1e9dda430176b0735a407b31c;hp=05bca2794f4c2c25c26545a8ee6c8206cb969b69;hpb=2e40c4aec57bb13c8cc5d599d3f66dd799f127e4;p=themediocreprogrammer.git

diff --git a/chapter02.md b/chapter02.md
index 05bca27..6f35730 100644
--- a/chapter02.md
+++ b/chapter02.md
@@ -20,3 +20,6 @@ There's also the tendency in post-mortems to have a bit of hindsight about them.
 
 There's nothing wrong with reading a post-mortem about a project - we can learn a great deal about how a project is run (or shouldn't be run) and what pitfalls may befall us if we go down a similar path. But understand that you're reading one account (whether by one person or one team of people). They have the vantage point of someone deep in the conflict. You're looking at their recollections of tactics, not the overall strategy brought them to the place.
 
+## 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.