71 Matching Annotations
  1. Last 7 days
    1. Open a new tab in your Chrome browser and type chrome://flags in the search field

      Access beta or secret features of Chrome browser family i.e. inc Brave

  2. Jan 2024
    1. Our flow is: The reporter reports an issue, and we developers create sub tasks upon that issue... in Redmine, we also had a percentage graph that would reach 100% when all sub-tasks were completed, was a great way about checking 1 item without the need to drill down all subtasks.
    1. The comparison to MRs is a good one, because MRs have a distinct workflow and JTBD. As such, they are their own object record. I'm not sure whether a decision to move them to work items has been made, but I can see a case for and against.
    1. https://web.archive.org/web/20240106094118/https://actions.work/actions-for-obsidian

      An app with a range of acions for Obsidian. See the list of actions, that are likely easily to create in AppleScript or Alfred, for those that are useful to me.

  3. Dec 2023
  4. Oct 2023
  5. Jul 2023
    1. 流程中的节点往后传递参数非常简单,只需往控制台输出即可。但须注意,多个控制台输出会合并到一起,因此除了往后传递参数外,其他情况下都不要往控制台打印文本。通常控制台输出会包含换行符,为避免换行符带来干扰,推荐使用 echo -n(bash) 或 sys.stdout.write(python);直接执行 js 时,方法内部的return 即往后传递参数,此时 console.log 输出到控制台并不合法。

      Alfred workflow 脚本传递参数

  6. Jun 2023
    1. 日常生活中,在微信订阅号列表,或者是好友的群聊中看到不错的文章,直接转发给 Wechat 2 Reader,将文章收藏到 Readwise Reader。

      inbox

  7. Mar 2023
    1. Perhaps tools like ChatGPT signal the start of a revise revolution in OER creation, where the role of an OER creator starts not with creating content but with creating the correct prompts to generate a first draft of content, then spends the bulk of their time revising and validating the content.
  8. Feb 2023
  9. Nov 2022
    1. So these are our two goals with organize. A, that the information is organized well. What you want to have happen here is that you can very quickly get the gestalt of what’s on your plate, what’s due, what’s not, who you’re waiting to hear back from. The information is put aside in such a way that it’s not just a list with a hundred things. And two, all the relevant information is there. I’m not scrambling around to figure out what I need to know to do this thing. All the information is there.

      Configure: Make sure all relevant information is available Make sure that information is structured for easy access.

  10. Sep 2022
    1. Now, not every programmer prefers that kind of development. Some programmers prefer to think of development as a process of designing, planning, making blueprints, and assembling parts on a workbench. There’s nothing wrong with that. Indeed, a multibillion-dollar international industry has been built upon it.

      I still think they should worry about it. Production systems need to evolve and contain data; reasoning about the systems completely statically from the source code with no regard to the existing data is a lot more complicated than it needs to be.

    2. In fact, there’s a style of programming, well known in Lisp and Smalltalk circles, in which you define a toplevel function with calls to other functions that don’t yet exist, and then define those functions as you go in the resulting breakloops. It’s a fast way to implement a procedure when you already know how it should work.
  11. Jul 2022
    1. These notes have no value except as stepping stones for turning literature notes into permanent notes. You discard the fleeting notes once you transformed them into permanent notes (more on that in level 3).

      I would love to know more about what this actually looks like...how does one use their fleeting notes to turn Literature Notes into Permanent Notes?

      For example, in Roam, does one have linked references for fleeting notes open in the sidebar and then filtered linked references for literature notes in the main window? And then you are looking for a connection or spark between a fleeting note and a literature note on one of the topics you are looking at?

  12. bafybeibbaxootewsjtggkv7vpuu5yluatzsk6l7x5yzmko6rivxzh6qna4.ipfs.dweb.link bafybeibbaxootewsjtggkv7vpuu5yluatzsk6l7x5yzmko6rivxzh6qna4.ipfs.dweb.link
    1. coordination can be defined as the arrangement of actions across people,places and times so as maximize synergy and minimize friction. In earlier work (Heylighen, 2012b),we have analyzed coordination into four components: alignment, division of labor, workflow andaggregation.

      Definition: Coordination is the arrangement of actions across people, places and times so as maximize synergy and minimize friction. It can be analyzed into four components: 1. Alignment 2. Division of Labor 3. Workflow 4. Aggregation

  13. Jun 2022
  14. Mar 2022
    1. process

      Workflow: a photo, a memory, a bit of each— into reworked words, seldom profound, but always a release.

  15. Feb 2022
  16. Nov 2021
    1. A good workflow can easily turn into a virtuous circle, where the positiveexperience motivates us to take on the next task with ease, which helps us toget better at what we are doing, which in return makes it more likely for us toenjoy the work, and so on. But if we feel constantly stuck in our work, wewill become demotivated and much more likely to procrastinate, leaving uswith fewer positive or even bad experiences like missed deadlines. We mightend up in a vicious circle of failure (cf. Fishbach, Eyal and Finkelstein,2010)

      =! workflow is Virtuous circle or vicious circle ?

  17. Aug 2021
    1. My process for collecting and synthesizing information used to be exactly that: make highlights, sync them to Roam, tag the articles’ pages, and the respective blocks/highlights. And when it was time to write I would think of applicable tags for drafting the outline of an article, open their linked references in the sidebar, drag relevant ones into the outline, and draft the manuscript.

      work flow of roambrain/Maarten van Doornm page, example of catch knowledge

  18. Jun 2021
  19. Mar 2021
    1. Whenever I get a new cookbook, I go through it and bookmark recipes that are either worth considering, or that go on a list to definitely try. Usually the maybes outnumber the definites. In this case, I've bookmarked a large number of recipes that I DEFINITELY will make.
    1. Solution The goal should be to use Markdown on git as the source of the documentation by default. This will make version control possible and facilitate collaboration. To achieve this, the first step should be to export all the InDesign files to Markdown, going through HTML. This page explains how to export InDesign to HTML Once the HTML files have been generated, converting them to markdown requires Pandoc. Help the client install Pandoc following this guide There is also a web version of Pandoc Some markdown editors like Atom export HTML into markdown Assuming the HTML file that needs to be converted is named file.html and the Markdown file the client needs to generate should be called file.md, the command to convert HTML to markdown is this: pandoc -o file.md file.html Once all the HTML files have been converted to markdown, the client can start updating their files directly in the git repository. Markdown files can then be imported into InDesign going through HTML whenever the client feels they can consolidate one version into a PDF or print. To export Markdown into HTML Pandoc can be used again, but also editors like Atom or ReText export markdown into HTML. This time the command in pandoc will be: pandoc -o file.html file.md ( assuming the Markdown file that needs to be converted is named file.md and the HTML file the client needs to generate should be called file.html). A howto for importing HTML to InDesign Instead of the Python script included in this article to delete new lines in the HTML file (which doesn’t seem to work), we can send the client this script in bash. The script can be launched on a Linux machine (it should also work in a Mac terminal). Instructions for the client: Download the attached file to the folder where you have saved your HTML files. You can open the file with a text editor to check that all is ok. You can also find the script here: https://github.com/AccessNow/helpline_documentation_resources/blob/master/scripts/sed-clean-HTML.sh allow the script to be executed, by running this command: chmod 777 sed-clean-HTML.sh run this command on all your files: ./sed-clean-HTML.sh filename.html
    1. Marked has a basic AppleScript dictionary, and allows you to get the document filename from multiple windows, as well as open files from scripts. This allows some workflow integration if you know a little bit of AppleScript. You can have any application which can trigger an AppleScript open a document in Marked, or have it retrieve a document from Marked for editing or other actions.
  20. 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

  21. Jan 2021
  22. Dec 2020
    1. Better community building: At the moment, MDN content edits are published instantly, and then reverted if they are not suitable. This is really bad for community relations. With a PR model, we can review edits and provide feedback, actually having conversations with contributors, building relationships with them, and helping them learn.
    2. Better contribution workflow: We will be using GitHub’s contribution tools and features, essentially moving MDN from a Wiki model to a pull request (PR) model. This is so much better for contribution, allowing for intelligent linting, mass edits, and inclusion of MDN docs in whatever workflows you want to add it to (you can edit MDN source files directly in your favorite code editor).
  23. Nov 2020
    1. I'd like to go with an RFC-based governance model (similar to Rust, Ember or Swift) that looks something like this: new features go through a public RFC that describes the motivation for the change, a detailed implementation description, a description on how to document or teach the change (for kpm, that would roughly be focused around how it affected the usual workflows), any drawbacks or alternatives, and any open questions that should be addressed before merging. the change is discussed until all of the relevant arguments have been debated and the arguments are starting to become repetitive (they "reach a steady state") the RFC goes into "final comment period", allowing people who weren't paying close attention to every proposal to have a chance to weigh in with new arguments. assuming no new arguments are presented, the RFC is merged by consensus of the core team and the feature is implemented. All changes, regardless of their source, go through this process, giving active community members who aren't on the core team an opportunity to participate directly in the future direction of the project. (both because of proposals they submit and ones from the core team that they contribute to)
  24. Sep 2020
    1. separate the workflow description from its execution.

      Separating a workflow description from its execution is an important aspect of reproducibility.

    1. And because it's real CSS, rather than some camelCased quotes-everywhere impostor, we can take advantage of the 'tweak in devtools, paste back into our source code' workflow, which I personally couldn't live without.
    1. Many changes, including bug fixes and documentation improvements can be implemented and reviewed via the normal GitHub pull request workflow. Some changes though are "substantial", and we ask that these be put through a bit of a design process and produce a consensus among the Yarn core team. The "RFC" (request for comments) process is intended to provide a consistent and controlled path for new features to enter the project.
  25. Jul 2020
  26. Jun 2020
  27. May 2020
  28. Dec 2019
    1. Archiving and downloading annotations Annotation viewing and export, from Hypothesis Labs Link: https://jonudell.info/h/facet Screencast: https://jonudell.net/h/facet.mp4 Description:  View annotations by user, group, URL, or tag. Export results to HTML, CSV, text, or Markdown.

      Did anyone tried to use this to feed mind/concept-mapping tools like Tinderbox or Cmap?

    1. Is there any way to use this to catch hypothesis annotations into a mind/concept map app? Like Tinderbox or cmaptools?

    1. However, it did require us to think differently about the creation, maintenance, and sustainment of our components moving forward — an integrative process we call "storybook-driven development."
  29. Nov 2019
  30. Jan 2019
    1. These protocols, formal structures, plans, procedures, and schemes can be con-ceived of asmechanismsin the sense that they (1) are objectified in some way(explicitly stated, represented in material form), and (2) are deterministic or at leastgive reasonably predictable results if applied properly. And they aremechanisms ofinteractionin the sense that they reduce the complexity of articulating cooperativework.

      People apply "mechanisms of interaction" to reduce the complexity of the articulation work.

      Schmidt and Bannon use these examples:

      • Formal and informal organizational structures • Planning and scheduling • Standard operating procedures (see Suchman's work on situated action) • Indexes and classifications for organizational and retrieval (see Bowker and Star on boundary objects/infrastructures)

    2. Therefore, instead of pursuing the elusive aim of devising organizational modelsthat are not limited abstractions and thus in principle brittle when confronted withthe inexhaustible multiplicity of reality, organizational models in CSCW applica-tions should be conceived of asresourcesfor competent and responsible workers.

      Schmidt and Bannon posit that organizational models in CSCW should be flexible enough to support new interpretations/evaluations of the model (contingent on circumstances), as well as capture decisions to "adapt, circumvent, execute, modify, etc. the underlying model".

  31. Dec 2018
    1. Exceptions are normal in work processes.

      More specific reference to workflow as a prime CSCW concern. Exceptions, edge cases, and fluid roles need to be accommodated by technology.

  32. Nov 2018
    1. Re-open libraries for exploration I use in-ns to jump into library namespaces and re-define their vars. I insert bits of println statements to help understand how data flows through a library. These monkey-patches only exist in the running REPL. I usually put them inside a comment form. On a REPL restart, the library is back at its pristine state. In this example below, I re-open clj-http.headers to add tracing before the header transformation logic: [source] ;; set us up for re-opening libraries (require 'clj-http.headers) (in-ns 'clj-http.headers) (defn- header-map-request [req] (let [req-headers (:headers req)] (if req-headers (do (println "HEADERS: " req-headers) ;; <-- this is my added print (-> req (assoc :headers (into (header-map) req-headers) :use-header-maps-in-response? true))) req))) ;; Go back to to the user namespace to test the change (in-ns 'user) (require '[clj-http.client :as http]) (http/get "http://www.example.com") ;; This is printed in the REPL: ;; HEADERS: {accept-encoding gzip, deflate} An astute observer will notice this workflow is no different from the regular clojure workflow. Clojure gets out of your way and allows you to shape & experiment in the code in the REPL. You can use this technique to explore clojure.core too!

      explore library code in the repl in-ns and the redefinition

  33. Sep 2018
    1. We'll first look at modelling the problem space - what is common to, and what differs between, thedifferent product variants. Then we'll consider one possible approach for realising product variants in the solutionspace using C++ as an example. Finally we'll look at how Application Engineering is performed by using theproblem and solution space models to create a product variant.
    2. In reality, this linear flow is rarely found in practice.Product Lines usually evolve continuously, even after the first product variants have been defined and deliveredto customers.
  34. Jul 2018
    1. Data becomes dark because no one is paying attention. There is little professional reward structure for scientists to preserve and disseminate raw data. Scientists are rewarded for creating high-density versions of their data in statistics, tables, and graphs in scholarly journals and at conferences. These publications in some ways are the sole end product of scientific inquiry. These products, while valuable, may not be as useful as some authors hope.

      Reward system in place is not rewarding the preservation of dark data.

  35. Jun 2018
    1. Traders continue to monitor their open positions and look for any more opportunities.
    2. If everything is working properly, traders start scanning the markets for potential trading opportunities.
    3. After reading about events and making note of what the analysts are saying, traders head to their workstations, turn on their computers and monitors and open up their analysis and trading platforms.
    4. Traders will also review economic calendars to find out which market-moving financial reports – such as the weekly petroleum status report – are due that day.
    5. This involves reading stories from various newspapers and financial websites, as well as listening to updates from financial news networks, such as CNBC and Bloomberg.
  36. May 2018
  37. Oct 2017
  38. Sep 2017
  39. Feb 2017
  40. Feb 2016
    1. Hi! I'm interested in translate the handbook into spanish, but I have a couple of questions: 1) Is someone already doing this? and 2) is there any methodology or guidelines of the flow of information among translators?