Merlin’s weekly podcast with Dan Benjamin. We talk about creativity, independence, and making things you love.
@If Context
GOD | Feb 19 2006
One of the problems I have is coordinating a particular action in one place so that I can complete it in another. For instance, grabbing a book from the office that is ready to be returned to the library as I go out to get coffee on the other side of campus. Another similar example is that I meant to give something to a friend of mine, have had it in my pocket for several days now, but forgot to give it to him when I saw him today -- even though we spent a few hours together, eating and talking. I thought about tackling this with dated tasks, which would certainly help in the situation with my friend, but it wouldn't help in the first example. So I think I'm going to try using @If contexts. An example would be, @If - Going past library, then grab book to take back. Or, @If - You see Mark, give him that thing. Thoughts? 18 Comments
POSTED IN:
 I guess what I'm saying...Submitted by TedPavlic on February 23, 2006 - 8:42pm.
I guess what I'm saying is that that's how @Agenda (and really all the @Contexts) are supposed to be used. Don't think of it as "scheduling a task," because you're not adding a task to the schedule. You're just listing something that you need to do sometime in the future. Keep your @Library list near you and when you happen by the library you can read it off. Putting something on @Library and then immediately heading to the library defeats some of the purpose of the system. At that point, it sounds like the @Library is just an extra step -- you were going there anyway. However, if you keep @Library in your back pocket and just happen to pull it out (a) when you're at the library and then you have an effortless way of getting things done. So maybe the real trick is learning to use your @contexts just like you use your @If? » POSTED IN:
|
|
| EXPLORE 43Folders | THE GOOD STUFF |
