Sub-contexts for @work?
Most of my GTD lists hum right along, but one area where I could use the most improvement is @work. I'm trying to come up with a good solution for subdividing this list. It gets a little longer than I would like, which makes me reluctant to add items to it.
I am a web developer. I work in a cube about 10 feet from all of my colleagues and 20 feet from my manager. My phone rings about twice a month, and one of those is a wrong number. Virtually everything I do is on the computer, or if it's a face-to-face thing, my team members are readily accessible to me. Agendas and contexts don't help very much here.
I've thought about breaking the @work list up by applications that I use regularly, but this would honestly be more trouble that it's worth. Firing up my development software or remoting in to a server takes 30 seconds at most, which is minimal compared to the effort required to switch gears and tackle a task on another project that uses the same program. I never make phone calls. I've had an @email list in the past, but I spend so much time in email that it's more effective to use @Action/@Waiting For folders in Outlook.
Which leaves me with a longish @work list. Lately I've found myself going through this list and picking out a few items that I hope to do today. It's not a daily to-do list--more of a light prioritization.
Any suggestions for an elegant method to break this list up?