On the same page, it seems
@kkuja and @bcmyers2112
This means that at least the three of us - and many others, I am sure - interpret David Allen in the "correct" way, i.e. that there are as many Next actions as there really are. If an action is possible to do now, without anything else being necessary to be completed first, then it is a Next action.
I have heard on countless occasions, though, people on various app forums claim that DA really means there can only be one Next action, and they sometimes quote some passage from one of the books which might seem to recommend "do not pick too many", "one is usually just nice" etc. More often than not, though, I believe they just quote other users. There seems to be a fairly solid and common misconception out there. And the existence of strictly sequential projects in some apps (either that, or the parallel shotgun type, but nothing flexible in between) encourages this misinterpretation.
I do not have a computer context, because I usually have a computer or computer-like appliance nearby. It would be handy sometimes, I admit, to have all kinds tags, but I do not have the energy to tag everything with a computer context since that is something I usually have everywhere. I do have location tags like office1, office2 and home, though, and these places all have all the computers and faxes I need. But they may have entirely different sets of other things, e.g. paper based document archives or some very special software that is only available in one of these locations - that's why I tag those that need be done in one particular place.
I also agree and sympathize with your effort to combine several aspects into one single tag, when possible, such as, in your case, home and brainless. Such relationships are very individual, though. Another such combo, that I have heard many find useful, is quick-n-easy, combining low energy and short time.
Defining tags (contexts) is an art in itself, and is intimately related to the quick filtering capabilities available in the app. For example, if you have a NOT (exclude) filter, you can get away with much less tagging and do more precise filtering. You could then have lots of infrequently used tags called "requires special software X" etc, and simply exclude the tasks that require this software whenever you are in the wrong place. If you only have the ubiquitous "pick this only" (AND) filter, then you would have to tag the vast majority of tasks with the "does not require X" to accomplish the same thing - and that's simply too much work.
Last edited by Folke; 09-19-2013 at 05:20 AM.