Two Contexts

The problem starts with capture. Since the objective of capture is keeping your head clear, the process results in my inbox containing two types of tasks—those I will do, and those I might do. - DaFacto

Great concept.

In my situation I've got a lot of location-aware tasks that can only be completed at a certain store or off-site location. This means I've got to implement a list of context per location so I can easily shift to the tasks at hand for the location I'm currently working.

But aside from these locations, my contexts are all over the place. So maybe implementing a simplified approach for all tasks that are not related to those specific locations could be a great approach.

Something to think about.


In case you’re wondering what I’m talking about, look at this shit. A network process using 100% of the CPU, WiFi disconnecting at random times, and names, names (1), names (2), names (4). All caused by a crappy piece software called discoveryd. -Craig Hockenberry

I manage a network of around 600 Macs on a daily a basis. Yes. DiscoveryD is a clusterfuck. And no. Rebooting an entire enterprise network is impossible.