I'm sure many here have seen this situation before:
I've ordered a new phone and its in the mail. I found a few cool pieces of software I want on the phone after it is all set up so I have a pending action "download app X". Its not actionable until after I get the phone (which is currently a waiting for item and a "set up phone" project). The "set up phone" project folder has a bit more info in it which is all reference material.
I don't want to store the "download app X" action in the project reference because it will not get looked at until I review the entire file. Currently I'm stuffing the action in my waiting for.
I have a pattern for this kind of thing: "when event E happens, do action A". I'm looking for a more elegant way to store and track them.
What are your thoughts about these actions? They cannot be acted on until something else happens but they are small, concrete things that really don't belong in a big project reference file. I usually want to act on them right away, too.
I've ordered a new phone and its in the mail. I found a few cool pieces of software I want on the phone after it is all set up so I have a pending action "download app X". Its not actionable until after I get the phone (which is currently a waiting for item and a "set up phone" project). The "set up phone" project folder has a bit more info in it which is all reference material.
I don't want to store the "download app X" action in the project reference because it will not get looked at until I review the entire file. Currently I'm stuffing the action in my waiting for.
I have a pattern for this kind of thing: "when event E happens, do action A". I'm looking for a more elegant way to store and track them.
What are your thoughts about these actions? They cannot be acted on until something else happens but they are small, concrete things that really don't belong in a big project reference file. I usually want to act on them right away, too.