How to handle one-way sequences?; "do [this] then afterwards [that]"

Comments

2 comments

  • Avatar
    Brian Clements-Tiberio

    When I make a list, the children nodes are dependencies for the parent in my mind. If it truly is an ordered list, then I just know to start from top and go to the bottom, OR, that doesn't really matter and I execute them in whatever order. Then when the children are done, the parent is done. Context is usually how I discern between ordered lists and sets. Maybe a tag on the parent of the list to indicate list vs set?

    I think what you're looking to do is use tags to signify the other characteristics of the particular items. So this would be, perhaps, priorities? Or maybe a marker Kanban style indicating "doing" "next" etc.

    I've been experimenting with how to do dependencies. Sometimes I have complicated projects that actually depend on single tasks deep within another project. That entire project doesn't need completing in order to do the one task, but it can get completed in one project and count for both. For this I use mirrors.

    I like to use tags that make sense on their own, but also work within a natural language description. And I keep the tag usage and color coding constant across every project so that my exploration can work the same on a global level, or individual project level. So I will use "#waiting" to indicate both something that is stopped and "waiting" on a person to get back to me, or some other dependency task. So I will make a child node that says "#waiting on", and the children of that node will be mirrors to the tasks of other projects or tasks that need completing.

    I've also used mirrors to display the same information, but in different contexts. So I'd have a type of index of all the possible nodes, but then start to create mirrors and alternate sorting and organizations in sibling nodes to allow myself to explore that same data in different representations.

    1
    Comment actions Permalink
  • Avatar
    Kristian Voss Bjerre

    Really interesting stuff!

    Some of it i might need to see visually to truly grasp, but meanwhile here is some of my thoughts:
    I also use #waiting with a color, sometimes with children nodes, but I only use it for awaiting other's people/factors. Basically i use it to mark things I don't have to work on, but might have to know, check up on or remind others of in the future.

    I've considered boards, because it fits my internal visual idea, representing progression from left to right, and because it often can't show as much at once (a advantage in this aspect). The drawback is having to fit the board nodes under a often "redundant" parent node.

    I also wonder if tag-quick-search, could be used to quickly organize and reorganize data and tasks, but haven't played around with it enough yet. 

    Very interesting having mirrors of the same list/index ordered differently! I often wish to have "the same node" but in different iterations mirrored different places, for instance: Updates of the same "statement/fact", public vs private choice of words, same concept used in different settings

    1
    Comment actions Permalink

Please sign in to leave a comment.