46 Matching Annotations
  1. Oct 2022
    1. If you're trying out @tana_inc and are not on the slack... why not?? There are so many talented people coming up with awesome workflows

      https://twitter.com/syncretizm/status/1581264527336669184

      So many in the tools for thought space either have shiny object syndrome or are focusing on "workflows". Eventually you have to quit looking at and building workflows to actually get some work done.

  2. Sep 2022
    1. Experiences with workflow systems, systems which automatically route documents and workthrough defined procedures, show that systems without the ability to handle exceptions to theformalized procedure cannot support the large number of cases when exceptional procedures arerequired (Ellis, Gibbs, Rein, 1991).

      Feels like formalizing organic processes will have this outcome. The goal should be to make an actual formal workflow or build tools that enable users rather than trying to mix them.

    1. Google Forms and Sheets allow users toannotate using customizable tools. Google Forms offers a graphicorganizer that can prompt student-determined categorical input andthen feeds the information into a Sheets database. Sheetsdatabases are taggable, shareable, and exportable to other software,such as Overleaf (London, UK) for writing and Python for coding.The result is a flexible, dynamic knowledge base with many learningapplications for individual and group work

      Who is using these forms in practice? I'd love to see some examples.

      This sort of set up could be used with some outlining functionality to streamline the content creation end of common note taking practices.


      Is anyone using a spreadsheet program (Excel, Google Sheets) as the basis for their zettelkasten?

      Link to examples of zettelkasten as database (Webb, Seignobos suggestions)

      syndication link


  3. Aug 2022
    1. And there’s beginning to be more and more of an understanding on the scientific side and more and more interest on the side of people who are interested in developing tools for thought for understanding. How does the workflow of thinking happen when you have these tools that magnify your capabilities? There really hasn’t been a fraction of the amount of research on that as there has been on the development of the tangible tools themselves.

      Bias towards researching tangible things needs time to be overcome, it's also a gear shift to higher level of complexity in viewpoint. Compare to my searches in my fav topics list, where does this apply / potential hardening of focus?

  4. Jun 2022
    1. Remove the commit from step 2. We will merge ignoring the failure. Remove the commit from the other, check it passes with the other commit now on main. Merge the other. We will trigger builds for the main branch of affected repositories to check if everything is in order. Steps 5-8 should happen continuously (e.g. one after another but within a short timespan) so that we don't leave a broken main around. It is important to triage that build process and revert if necessary.

      It is important to not leave a broken main around.

  5. May 2022
    1. The paper describes four ontologies for representing workflows in Research Objects, and includes examples and motivation scenarios.

      The ontologies developed make use of and extend existing well known ontologies, namely the Object Reuse and Exchange (ORE) vocabulary, the Annotation Ontology (AO) and the W3C PROV ontology (PROVO). We illustrate how the ontologies can be utilized using a real-world scenario, in which scientists created a Workflow Research Object for an investigation on the Huntington's disease. We also present the tools we developed for managing Workflow Research Objects.

      A sketch depicting the main steps that the bioinformatician followed for manipulating and analyzing datasets, and the workflows that were used in each step

  6. Apr 2022
    1. Since most of our feeds rely on either machine algorithms or human curation, there is very little control over what we actually want to see.

      While algorithmic feeds and "artificial intelligences" might control large swaths of what we see in our passive acquisition modes, we can and certainly should spend more of our time in active search modes which don't employ these tools or methods.

      How might we better blend our passive and active modes of search and discovery while still having and maintaining the value of serendipity in our workflows?

      Consider the loss of library stacks in our research workflows? We've lost some of the serendipity of seeing the book titles on the shelf that are adjacent to the one we're looking for. What about the books just above and below it? How do we replicate that sort of serendipity into our digital world?

      How do we help prevent the shiny object syndrome? How can stay on task rather than move onto the next pretty thing or topic presented to us by an algorithmic feed so that we can accomplish the task we set out to do? Certainly bookmarking a thing or a topic for later follow up can be useful so we don't go too far afield, but what other methods might we use? How can we optimize our random walks through life and a sea of information to tie disparate parts of everything together? Do we need to only rely on doing it as a broader species? Can smaller subgroups accomplish this if carefully planned or is exploring the problem space only possible at mass scale? And even then we may be under shooting the goal by an order of magnitude (or ten)?

  7. Feb 2022
    1. In hindsight, we know why they failed: The ship owners tried tointegrate the container into their usual way of working withoutchanging the infrastructure and their routines. They tried to benefitfrom the obvious simplicity of loading containers onto ships withoutletting go of what they were used to.

      Ahrens makes a useful analogy: the reason that early attempts at shipping containers failed was because their users tried to fit them into their own way of doing business instead of reorganizing their businesses to accommodate the shipping container. Similarly one needs to consider how one's note taking method fits into their work in a more integrative way. Without properly integrating it into one's workflow seamlessly the system will fail.

    2. And if you stumble upon one idea and think that it might connect toanother idea, what do you do when you employ all these differenttechniques? Go through all your books to find the right underlinedsentence? Reread all your journals and excerpts? And what do youdo then? Write an excerpt about it? Where do you save it and howdoes this help to make new connections? Every little step suddenly

      turns into its own project without bringing the whole much further forward. Adding another promising technique to it, then, would make things only worse.

      Keeping one's notes across multiple modalities, in different locations, different apps is a massive problem portending imminent and assured failure. Regardless of the system employed (paper, digital, app), one of the most important features of any note taking system is having them all centralized in one location.

    3. Writing is not what follows research, learning or studying, it is themedium of all this work. And maybe that is the reason why we rarelythink about this writing, the everyday writing, the note-taking anddraft-making.

      Here in a nutshell is the thrust of the entire book to come!


      Notes allow one to do small pieces of work over time, then by editing one's notes together to weave a story or create a broader thesis, one is primarily ordering and editing their prior work which isn't as difficult as staring at a blank piece of paper and wondering where to begin.

  8. Jan 2022
    1. What does a Functional Design have to offer? https://en.itpedia.nl/2019/01/16/wat-heeft-een-functioneel-ontwerp-te-bieden/ A functional design is a specification of the functions of the software that the end_users have agreed to. Many companies have a software_developer handbook that describes what topics a functional design should cover. This article looks at the steps of functional design in the context of software development.

  9. Nov 2021
    1. https://diggingthedigital.com/abonneren-op-aantekeningen/

      I like the idea here of being able to watch over someone's shoulder quietly to see what they're working on and how they're doing it. There's some interesting anthropology hiding here.

      Have to say I'm a bit flattered that it's me that's being watched...

  10. Jul 2021
    1. Watched up to 2:33:00 https://youtu.be/wB89lJs5A3s?t=9181 with talk about research papers.

      Some interesting tidbits and some workflow tips thus far. Not too jargony, but beginners may need to look at some of his other videos or work to see how to better set up pieces. Definitely very thorough so far.

      He's got roughly the same framing for tags/links that I use, though I don't even get into the status pieces with emoji/tags as much as he does.

      I'm not a fan of some of his reliance on iframes where data can (and will) disappear in the future. For Twitter, he does screencaptures of things which can be annoying and take up a lot of storage. Not sure why he isn't using twitter embed functionality which will do blockquotes of tweets and capture the actual text so that it's searchable.

      Taking a short break from this and coming back to it later.

  11. Jun 2021
  12. Feb 2021
    1. Additional testing of pipeline portability is currently being conducted as a part of the Global Alliance for Genomics and Health (GA4GH) workflow portability challenge

      For more on how this went and an update on where the platform has developed to in Feb 2021 can be viewed in this video from CWLcon2021 https://youtu.be/vV4mmH5eN58

  13. Nov 2020
    1. As it becomes more clear what are specific functional jobs to be done, we see more specialized apps closely aligned with solving for that specific loop. And increasingly collaboration is built in natively to them. In fact, for many reasons collaboration being natively built into them may be one of the main driving forces behind the venture interest and success in these spaces.

      As it becomes more clear what the functional job to be done is, we see more specialized apps aligned with solving that specific loop. Collaboration is increasingly built natively into them.

  14. Jan 2020
  15. Nov 2019
    1. But in general the guideline is: code should be clean, history should be realistic.
    2. many organizations end up with messy workflows, or overly complex ones.
    3. If you push to a public branch you shouldn't rebase it since that makes it hard to follow what you're improving, what the test results were, and it breaks cherrypicking
  16. Feb 2018
  17. Apr 2016