> 2) The blog being in a public Git repository is nice for transparency. The expectation that all your code is on a public repository (I blame GitHub for this)

> 2) The blog being in a public Git repository is nice for transparency. The expectation that all your code is on a public repository (I blame GitHub for this) is one of the most horrifying developments in software engineering.