18 Matching Annotations
  1. Sep 2022
    1. There has been much discussion about “atomic notes”, which represents the key ideas from a person’s research on some topic or source (sources one and two). These are not the kind of thing I am interested in creating/collecting, or at least not what I have been doing. A far more typical thing for me is something I did at work today. I was trying to figure out how to convert the output of a program into another format. I did some searching, installed a tool, found a script, played with the script in the tool, figured out how to use it, then wrote down a summary of my steps and added links to what I found in my search. Since I am not doing research for a book or for writing academic papers, the idea of an atomic note does not fit into my information world. However, capturing the steps of a discovery or how I worked out a problem. is very real and concrete to me. I used to know a fellow engineer who wrote “technical notes” to capture work he was doing (like a journal entry). Maybe that is how I should consider this type of knowledge creation. 

      Andy Sylvester says his engineering type of notes don't fit with the concept of atomic note. A 'how to solve x' type of note would fit my working def of 'atomic' as being a self-contained whole, focused on a single thing (here how to solve x). If the summary can be its title I'd say it's pretty atomic. Interestingly in [[Technik des wissenschaflichen Arbeitens by Johannes Erich Heyde]] 1970, Heyde on p18 explicitly mentions ZK being useful for engineers, not just to process new scientific insights from e.g. articles, but to index specific experiences, experiments and results. And on p19 suggests using 1 ZK system for all of your material of various types. Luhmann's might have been geared to writing articles, but it can be something else. Solving problems is also output. I have these types of notes in my 'ZK' if not in the conceptual section of it.

      Vgl [[Ambachtelijke engineering 20190715143342]] artisanal engineering, Lovelock Novacene 2019, plays a role here too. Keeping a know-how notes collection in an environment where also your intuition can play a creative role is useful. I've done this for coding things, as I saw experienced coders do it, just as Andy describes, and it helped me create most of my personal IndieWeb scripts, because they were integrated in the rest of my stuff about my work and notions. Vgl [[Vastklik notes als ratchet zonder terugval 20220302102702]]

  2. May 2022
  3. May 2021
  4. Apr 2021
  5. Mar 2021
  6. Feb 2021
    1. that's a point, but I would say the opposite, when entering credit card data I would rathre prefer to be entirely in the Verified By Visa (Paypal) webpage (with the url easily visible in the address bar) rather that entring my credit card data in an iframe of someone's website.
  7. Jan 2021
  8. Nov 2020
  9. Sep 2020
    1. Svelte will not offer a generic way to support style customizing via contextual class overrides (as we'd do it in plain HTML). Instead we'll invent something new that is entirely different. If a child component is provided and does not anticipate some contextual usage scenario (style wise) you'd need to copy it or hack around that via :global hacks.
  10. Jul 2020
    1. "that text has been removed from the official version on the Apache site." This itself is also not good. If you post "official" records but then quietly edit them over time, I have no choice but to assume bad faith in all the records I'm shown by you. Why should I believe anything Apache board members claim was "minuted" but which in fact it turns out they might have just edited into their records days, weeks or years later? One of the things I particularly watch for in modern news media (where no physical artefact captures whatever "mistakes" are published as once happened with newspapers) is whether when they inevitably correct a mistake they _acknowledge_ that or they instead just silently change things.
  11. May 2020
  12. Mar 2020