As your codebase and development team grow, being able to communicate how and why your code has evolved is crucial to your ability to continue to change it.
Our version control history is a living, ever-changing, searchable record that tells the story of how and why our code is the way it is. The ability to document your code effectively using Git (or any other version control system) is an invaluable skill which allows your team to make informed decisions about future code changes.
This talk will outline some of the key practices which can be adopted to make your version control history tell a valuable story about your codebase, and how you can embed these practices with in your team.
The Lead Developer 2016 - Accepted [Edit]
RubyConf Colombia 2016 - Rejected [Edit]
SwanseaCon 2015 - Rejected [Edit]
Add submission