71 Matching Annotations
  1. Apr 2024
    1. It is prudent to maturewell before improvements are adopted. Improvements rashlyintroduced may give cause for regret when it is too late to turn back.

      Regular note taking practice will be the best indicator of when potential improvements are worthwhile. Though you may see someone else's advice, workflows, or potential improvements, they may be just as likely not to work for you and your particular needs. Adopting changes without thinking them through or even practicing them for a while are more likely to cause harm, regret, or additional work without any value added to the system.

    2. Summaries*

      examples of specific workflows within Kaiser's card system

  2. Mar 2024
  3. Feb 2024
    1. The increment-after-release model makes sense for branching too. Suppose you have a mainline development branch, and you create maintenance branches for releases. The moment you create your release branch, your development branch is no longer linked to that release's version number. The development branch contains code that is part of the next release, so the version should reflect that.
  4. Nov 2023
    1. Next Step for your Cornell Notes? by Dr Maddy<br /> https://www.youtube.com/watch?v=QZFrR-u9Ovk

      Like that someone in the space is thinking about taking Cornell notes and placing them into the linked note taking framing.

      She doesn't focus enough on the questions or the spaced repetitions pieces within Cornell. How might this be better built into a UI like Protolyst, Obsidian, etc.? Where is this in people's note taking workflows?

  5. Oct 2023
    1. When digitized, each resulting ‘Digital Specimen’ must be persistently and unambiguously identified. Subsequent events or transactions associated with the Digital Specimen, such as annotation and/or modification by a scientist must be recorded, stored and also unambiguously identified.

      Workflows

  6. Sep 2023
    1. (1:20.00-1:40.00) What he describes is the following: Most of his notes originate from the digital using hypothes.is, where he reads material online and can annotate, highlight, and tag to help future him find the material by tag or bulk digital search. He calls his hypothes.is a commonplace book that is somewhat pre-organized.

      Aldrich continues by explaining that in his commonplace hypothes.is his notes are not interlinked in a Luhmannian Zettelkasten sense, but he "sucks the data" right into Obsidian where he plays around with the content and does some of that interlinking and massage it.

      Then, the best of the best material, or that which he is most interested in working with, writing about, etc., converted into a more Luhmannesque type Zettelkasten where it is much more densely interlinked. He emphasizes that his Luhmann zettelkasten is mostly consisting of his own thoughts and is very well-developed, to the point where he can "take a string of 20 cards and ostensibly it's its own essay and then publish it as a blog post or article."

    1. To build HIPAA compliant software, developers need to be aware of and comply with several key requirements outlined in the HIPAA Privacy Rule and Security Rule. These requirements are designed to ensure the confidentiality, integrity, and availability of protected health information (PHI) and to prevent unauthorized access, use, or disclosure of PHI.

      Building software compliant with HIPAA standards necessitates a deep understanding of its Privacy and Security Rules to safeguard protected health information effectively.

    1. There are many reasons why you might want to migrate from one stack to another. Maybe you’re looking for a more robust solution, or perhaps you’re trying to simplify your development process. Whatever the reason, it’s important to know that it is possible to migrate from one stack to another.

      Migration between tech stacks can be driven by various motivations, including the need for enhanced capabilities or a desire for a more streamlined development workflow.

    1. Additionally, they are at the forefront of sharing valid product ideas with their team since they have an expert understanding of coding best practices as well as mobile and web programming services.

      Developers play a pivotal role in product ideation due to their deep knowledge of coding standards and expertise in both mobile and web development.

    1. Time Required to Code: Every project comes with a deadline, and the time set out by your client to get the work done is a crucial part of your decision. If you have a tight deadline, you might be better off with the fastest front-end framework you can find. One that would work well with your team’s capabilities to ensure great results in the shortest time possible.

      The efficiency of a front-end framework can significantly impact project timelines. Choosing a framework that aligns with the project's deadline and the team's proficiency can ensure timely delivery.

  7. Jul 2023
  8. Jun 2023
    1. (1:21:20-1:39:40) Chris Aldrich describes his hypothes.is to Zettelkasten workflow. Prevents Collector's Fallacy, still allows to collect a lot. Open Bucket vs. Closed Bucket. Aldrich mentions he uses a common place book using hypothes.is which is where all his interesting highlights and annotations go to, unfiltered, but adequately tagged. This allows him to easily find his material whenever necessary in the future. These are digital. Then the best of the best material that he's interested in and works with (in a project or writing sense?) will go into his Zettelkasten and become fully fledged. This allows to maintain a high gold to mud (signal to noise) ratio for the Zettelkasten. In addition, Aldrich mentions that his ZK is more of his own thoughts and reflections whilst the commonplace book is more of other people's thoughts.

  9. May 2023
  10. Apr 2023
  11. Mar 2023
  12. Feb 2023
    1. The novel workflows that a technology enables are fundamental to how the technology is used, but these workflows need to be discovered and refined before the underlying technology can be truly useful.

      This is, in part, why the tools for thought space should be looking at intellectual history to see how people have worked in the past.


      Rather than looking at how writers have previously worked and building something specific that supports those methods, they've taken a tool designed for something else and just thrown it into the mix. Perhaps useful creativity stems from it in a new and unique way, but most likely writers are going to continue their old methods.

  13. Jan 2023
    1. https://nataliekraneiss.com/your-academic-reading-list-in-obsidian/

      This is excellent! I was going to spend some time this week to write some custom code with Dataview to do this, but apparently there's a reasonably flexible plugin that will get me 95% of what I'm sure to want without any work!

  14. Dec 2022
  15. 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.

  16. 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


  17. 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?

  18. 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.

  19. 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

  20. 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)?

  21. 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.

  22. 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.

  23. 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...

  24. 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.

  25. Jun 2021
  26. 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

  27. 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.

  28. Jan 2020
  29. 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
  30. Feb 2018
  31. Apr 2016