theburningmonk · December 24, 2015 16:01
diff --git a/abstract.txt b/abstract.txt
 We programmers spend so much of our time coding everyday, and there's a wealth of information about 
 HOW we work hidden in our commit histories.

 In this talk I'll share some of the ideas we experimented with to analyze our commit history in order
 to gain insight into the way we work, and how the quality of our codebase has evolved over time. 
 Along the way, there were some rather interesting findings!

 All the code examples will be in F#, but you can easily apply the same techniques in any other language.
	We programmers spend so much of our time coding everyday, and there's a wealth of information about
	HOW we work hidden in our commit histories.

	In this talk I'll share some of the ideas we experimented with to analyze our commit history in order
	to gain insight into the way we work, and how the quality of our codebase has evolved over time.
	Along the way, there were some rather interesting findings!

	All the code examples will be in F#, but you can easily apply the same techniques in any other language.