Sorry, but there is no good defense against multiple contexts. As has been stated elsewhere, there is no reason why GTD couldn't use multiple contexts, it's just not feasible with a paper or simple list-based solution. With advanced tools, though, advanced usages are available.
Perfect example: I have calls to make. Some are work-related, some are non-work related. The idea of a context as a working state should be flexible enough to support the idea of "I'm in the mood to focus on work tasks" and "I'm in the mood to make some calls". Both are very specific states of mind and both have overlapping tasks. If I'm in the mood to work, I can blow through a bunch of work tasks, including invoicing, calls, etc. If I'm just in the mood to make calls, I can blow through a call to the florist, a call about an overdue work invoice, and a call to pay a bill all in one blast. Those are two different contexts that could include the same tasks.
Do _not_ say "have you read GTD". I have several times and am extremely familiar with it both in principle and in practice. Right now, OF interferes with supporting natural GTD contexts and switching between them quickly because it forces you to go through all kinds of kludges and hacks just to be able to support the very simple example described above. Calling about an overdue invoice is both a phone call and work related, and both of those are separate work states, either of which could allow me to knock that task out if it showed up correctly in the list.
This is the single biggest reason I have moved to Things. The second OF supports multiple contexts, I would be glad to come back. Right now, not having it is a severe limitation whose workarounds needlessly add noise to task management in OF.
Perfect example: I have calls to make. Some are work-related, some are non-work related. The idea of a context as a working state should be flexible enough to support the idea of "I'm in the mood to focus on work tasks" and "I'm in the mood to make some calls". Both are very specific states of mind and both have overlapping tasks. If I'm in the mood to work, I can blow through a bunch of work tasks, including invoicing, calls, etc. If I'm just in the mood to make calls, I can blow through a call to the florist, a call about an overdue work invoice, and a call to pay a bill all in one blast. Those are two different contexts that could include the same tasks.
Do _not_ say "have you read GTD". I have several times and am extremely familiar with it both in principle and in practice. Right now, OF interferes with supporting natural GTD contexts and switching between them quickly because it forces you to go through all kinds of kludges and hacks just to be able to support the very simple example described above. Calling about an overdue invoice is both a phone call and work related, and both of those are separate work states, either of which could allow me to knock that task out if it showed up correctly in the list.
This is the single biggest reason I have moved to Things. The second OF supports multiple contexts, I would be glad to come back. Right now, not having it is a severe limitation whose workarounds needlessly add noise to task management in OF.