From 80dc3f1dd0636af1e9dda430176b0735a407b31c Mon Sep 17 00:00:00 2001 From: Craig Maloney Date: Mon, 28 May 2018 09:29:11 -0400 Subject: [PATCH] Checkpoint --- Makefile | 2 +- chapter02.md | 3 +++ metadata.xml | 2 +- 3 files changed, 5 insertions(+), 2 deletions(-) diff --git a/Makefile b/Makefile index c52e5a2..39a0dec 100644 --- a/Makefile +++ b/Makefile @@ -5,7 +5,7 @@ METADATA = metadata.xml CHAPTERS = intro.md chapter01.md chapter02.md chapter03.md chapter04.md chapter05.md chapter06.md epilogue.md appendixa.md TOC = --toc --toc-depth=2 COVER_IMAGE = images/cover.jpg -LATEX_CLASS = report +LATEX_CLASS = book all: book 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. diff --git a/metadata.xml b/metadata.xml index 0efac3b..fe471d6 100644 --- a/metadata.xml +++ b/metadata.xml @@ -1,2 +1,2 @@ -Copyright 2018, Craig Maloney and released under a CC-BY-SA International 4.0 License +Copyright 2018, Craig Maloney. Released under a CC-BY-SA International 4.0 License en-US -- 2.31.1