16 Matching Annotations
  1. Oct 2023
    1. You don’t connect notes as the pinnacle achievement in dealing with knowledge (or at least should not, because it is an insult to your potential). You should go way deeper. To make sure that you go as deep as you can, you should try to actually create something. Create (knowledge) tools you want to use. If you process a book, an article or whatever, ask yourself what tools you (or perhaps your clients) need. Then you marry the two concepts, Depth of Processing and Value Creation, properly. The depth is the necessary condition to create something valuable. You notice if you hit the threshold of proper depth of processing when you have created something of value.

      List/explore this in [[Maak machientjes in je PKM 20230304092406]]

  2. Jan 2023
    1. You’re not going to have a clear picture at the start. So start with a fuzzy one

      This sounds like what I call soft-focusing. Some years ago I let go of being strict with myself, and stopped having defined goals in favor of course/directions and a vaguer sense of the destination. I also started soft-focusing my inputs (if there's a connection to my running list of interests connected to my sense of direction it qualifies), and am now trying to soft-focus my outputs. Not blogpost / project A or deliverable B as I would earlier, but more emergent. Then when I have task / creative thing to do, I use it to formulate questions to my notes and see what comes up. This evolved from doing the same in conversations with clients and colleagues where the value of that and resulting associations was clearly visible.

  3. Apr 2022
  4. Jan 2022
  5. May 2021
  6. Mar 2021
    1. When nesting an activity with multiple outcomes, you can wire each terminus to a different route.
    2. For example, an output using Track(:create) will snap to the next possible task that is “magnetic to” :create. That’s how tracks or paths are created.
    3. Semantics are mostly relevant for nesting
    4. Remember, in a railway activity each task has two standard outputs with the “semantics” success and failure.
    5. By using Output(:semantic), you can select an existing output of the task and rewire it.
    6. Why don’t we put the “create user” task onto the failure track, and in case of successfully persisting the new user, we deviate back to the happy path?
    7. To implement such an activity, we only need to rewire the second step’s failure output to a new terminus.
    8. Since you can reference outputs by their semantic, you as a modeller only connect conceptual termini to ongoing connections!
    9. it’s a bit as if the following wiring is applied to every task added via #step
  7. Apr 2019