I see your point, however I don't think the advice is necessarily bad. For example, I put the world's easiest stuff on my todo list first -- something like "start the dev server" or "fix that typo". It's so easy that I can convince myself to do it, yet it gets me into "work mode".
Well, that's the trick. (Serial procrastinator here. Hello!) You can't think of a large project as a large project. Otherwise you'll never get it done. It's impossible by definition, because a larger project is a composite of a number of smaller tasks. So sometimes you end up having to trick yourself with "fix a typo" or "change this class name" or w/e. It has to be small and stupid enough that the activation cost is as low as possible.
Easier said than done, of course. Did I mention I'm procrastinating?
Of of the things I "trick" myself with is "you don't have to start working on it now, just look at the task list and split a couple of them into smaller sub tasks".
If I'm in a mood for putting things off, this provides an "excuse" that at the same time eventually results in a list that's fine-grained enough to convince myself to "just knock off a couple". Once I've then started, it's a lot easier. Sometimes it can lead to ludicrously detailed lists...
In particular for large projects it works very. I decide to work on it for only 15 minutes, doing something simple like making a folder with a text document with a list of things that needs to be done for the project. After that I take a decent break feeling good about myself before I start with the next 15 minutes.
