Why a need for routine?
As an engineer we take on many tasks. Coding is half of the puzzle, the other half contains problem solving, peer review, discussions and drinking beer.
Imagine each day you get a bag full of unknown items. These items are not grouped in anyway. Item 1 is peer reviewing some code, Item 2 is working on a feature, Item 3 is more peer review, Item 4 is some problem solving and Item 5 is more peer review.
During the day there is a set of pull requests that don't get merged into a branch because it was left for review too late in the day. Had we done this in the morning, the Pull Request can get merged and the rest of the day can be dedicated to the other tasks on hand.
... read the whole story at mellisdesigns.com.