A Craftsman looks at continuous integration

What this post added

This post argues that daily builds are insufficient for true Continuous Integration and advocates for more frequent, ideally per-check-in, builds. It stresses the importance of running all unit and acceptance tests automatically with every build and highlights the need to immediately address build failures rather than ignoring them. The post emphasizes short feedback loops and the responsibility of craftsmen to use CI tools to their fullest extent for creating the best software.