Checkpoint

diff --git a/Makefile b/Makefile
index c52e5a265c879d5874865e8373d3670f897af599..39a0dec1ac8e1243eaf2411d0fa56d2818accb29 100644 (file)
--- 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 05bca2794f4c2c25c26545a8ee6c8206cb969b69..6f35730dc273a7dff49fbe5f4fca2afb3b3fb28d 100644 (file)
--- 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 0efac3b673d92c3d31ac80caf0d44a4d944d69fc..fe471d6b80b6f5dae1e59a63051dc37c5fdf82f2 100644 (file)
--- a/metadata.xml
+++ b/metadata.xml
@@ -1,2 +1,2 @@
-<dc:rights>Copyright 2018, Craig Maloney and released under a CC-BY-SA International 4.0 License</dc:rights>
+<dc:rights>Copyright 2018, Craig Maloney. Released under a CC-BY-SA International 4.0 License</dc:rights>
 <dc:language>en-US</dc:language>