Are you also dreading your slow CI jobs? A build+test cycle of a couple of minutes sounds like a far distant dream. Reality is, after each check-in you can grab a coffee and watch the first half of the Godfather until your test results trickle in from Teamcity or Jenkins.
This is of course a complex topic. While it could easily spiral into an endless stream of discussions, e.g. on “what is a unit/integration/functional test and why are they so slow”, “my build tool sucks and takes ages to compile”, “who needs CI anyway?”, here are four quick and easy steps that will help you alleviate your pain – now: