Stop stopping at good stopping points

I loved this post about the wisdom of stopping work when you’re NOT at a “good stopping point.”

If you stop when something is broken but close to being fixed, it’ll be easy to get started again the next day. The post calls it an “on-ramp to flow.”

Unless the task is done, leaving the system / code too clean makes it hard to know what to work on next. While it’s really tempting to try to stick the landing on an internal milestone, it can often be more productive on net to stop just short of a neat milestone as an onramp to your next coding session.

Source

Good stopping points are bad, and bad stopping points are good.