That's an excellent list. The health and commute parts I can definitely agree with, the rest I may have just gotten lucky with in general. One additional tric

That's an excellent list. The health and commute parts I can definitely agree with, the rest I may have just gotten lucky with in general. One additional trick I like to use: when the work itself is getting repetitive and boring (similar requirements, etc), vary the way you do it, or parts of it. This can be anything from experimenting with the way you do your estimates, planning and bookkeeping, changing up the tooling (try a different source control tool, code analysis, whatever). Try different frameworks or languages (although preferably only for non-essential projects, in case it goes badly). Read up in-depth about exception handling policies and frameworks, and make use of one in your next project (if you don't already). And so on, the list is nearly endless. By varying these topics gently (preferably one at a time), you can keep risk to your clients at a minimum, while keeping things interesting for yourself, and broadening your skill set. This might seem obvious, but I see far too many people lose skills and motivation because they're stuck doing the same boring thing for years.