28 Matching Annotations
  1. Mar 2024
  2. Jan 2024
    1. From an organizational standpoint, the beauty of sermons is that each revolves around a specific theme. Accordingly, King could devote a single folder to each topic. He accumulated 166 folders, each with a title like “Loving your Enemies” (folder 1), “Why the Christian must Oppose Segregation” (folder 87), “Mental Slavery” (folder 113), and “The Misuse of Prayer” (folder 166). These folders contain King’s outlines; source material, like clippings from books; and drafts.

      In addition to his card index, Martin Luther King, Jr. compiled a collection of 166 folders organized around various topics which he used to organize outlines, clippings, pages from books, and other source materials as well as drafts of sermons or speeches on those topics.

      To some extent these folders are just larger format repositories mirroring the topical arrangements of his card index.

  3. Oct 2023
    1. Nein. Ich habe den Zettelkasten aus der simplen Überlegung her-aus angefangen, daß ich ein schlechtes Gedächtnis habe. Zunächsteinmal hatte ich Zettel in Bücher gelegt, auf die ich mir Notizenmachte, auf diese Weise gingen die Einbände der Bücher kaputt.Dann habe ich mir mit Mappen geholfen, als die jedoch dickerwurden, fand ich nichts mehr in ihnen. Ab 1952 oder 1953 begannich dann mit meinem Zettelkasten, weil mir klar wurde, daß ich fürein Leben planen müsse und nicht für ein Buch.

      Machine translation:

      No. I started the Zettelkasten out of the simple thought that I have a bad memory. First of all, I put pieces of paper in books on which I wrote notes, so the covers of the books got ruined. Then I helped myself with folders, but when they got thicker I couldn't find anything in them. In 1952 or 1953, I started my Zettelkasten because I realized that I had to plan for a life and not for a book.

      There's some missing interstitial space here about how precisely he came to it outside of the general motivation for the thing in general.

      52/53 would have been after law school and in his administrative days and before his trip to Harvard in 61.

  4. Mar 2023
  5. Jan 2023
    1. Hi Chris Aldrich, thank you for sharing your great collection of hypothes.is annotations with the world. This is truly a great source of wisdom and insights. I noticed that you use tags quite a lot there. Are you tagging the notes inside your PKM (Obsidian?) as much as in Hypothes.is or are you more restrictive? Do you have any suggestions or further reading advice on the question of tagging? Thanks a lot in advance! Warmly, Jan

      Sorry, I'm only just seeing this now Jan. I tag a lot in Hypothes.is to help make things a bit more searchable/findable in the future. Everything in Hypothes.is gets pulled into my Obsidian vault where it's turned into [[WikiLinks]] rather than tags. (I rarely use tags in Obsidian.) Really I find tagging is better for broad generic labels (perhaps the way many people might use folders) though I tend to tag things as specifically as I can as broad generic tags for things you work with frequently become unusable over time. I recommend trying it out for yourself and seeing what works best for you and the way you think. If you find that tagging doesn't give you anything in return for the work, then don't do it. Everyone can be different in these respects.

  6. Oct 2022
  7. Sep 2022
  8. Jul 2022
    1. Worth taking a look at the various affordances of folders vs. links vs. tags.

      Some of these functionalities may be highly dependent on the particular tool in question and what affordances the tool allows for these ideas.

      Has anyone done this comprehensively across a number of tools other than threads in fora like reddit, zettelkasten.de, etc.?

      https://www.reddit.com/r/ObsidianMD/comments/vofakc/folders_vs_links_vs_tags/

  9. Jun 2022
    1. Sometimes you know a project is coming and can startsaving things to a project folder in advance,

      no mention of the affordances of being able to cross-link things or even transclude them from an original location (which works for one currently) to another useful location.

    2. As powerful as search can be, studies5 have found that in manysituations people strongly prefer to navigate their file systemsmanually, scanning for the information they’re looking for. Manualnavigation gives people control over how they navigate, with foldersand file names providing small contextual clues about where to looknext.6

      The studies quoted here are in the mid 80s and early 90s before the rise of better and easier UI methods or more powerful search. I'd have to call this conclusion into question.

      There's also a big difference in what people know, what people prefer, and what knowledgeable people can do most quickly.

      Cross reference this with Dan Russell's research at Google that indicates that very few people know how to use ctrl-f to find or search for things in documents. - https://hyp.is/7a532uxjEeyYfTOctQHvTw/www.youtube.com/channel/UCh6KFtW4a4Ozr81GI1cxaBQ

      Relate it to the idea of associative (memory) trails (Memex), songlines, and method of loci in remembering where things are -- our brains are designed to navigate using memory

    3. By takingthat small extra step of putting a note into a folder (or tagging it*) fora specific project, such as a psychology paper you’re writing or apresentation you’re preparing, you’ll encounter that idea right at themoment it’s most relevant. Not a moment before, and not a momentafter.

      But what about the unimagined future projects that may be our most important. Zettelkasten methods cover for this better perhaps?

    4. It assumes only that you are currently working on acertain set of projects, and that your information should be organizedto support them.

      This seems practical, but also means that it isn't necessarily re-usable and may not provide as much serendipity for creating new ideas.

      Think about whether or not these are true.

  10. May 2022
    1. For Eco on using something like a ZK, see his short book How to Write an Essay. Basically, he writes about making something that we could say is like a ZK, but one card system for each writing assignment.

      Umberto Eco's book How to Write a Thesis (MIT Press, 2015, #) can broadly be thought of as a zettelkasten system, but it advises a separate system for each project or writing assignment. This is generally good advice, and potentially excellent for students on a one-time basis, but it prevents one from benefitting from the work over multiple projects or even a lifetime.

      In some sense, a more traditional approach, and one seen used in Niklas Luhmann's example is to keep different sections separated by broad topics.

      Niklas Luhmann's zettelkasten #1 had 108 broad topics (along with a bibliography and a subject index), and zettelkasten #2 had 11 broad topics. (Cross reference: https://niklas-luhmann-archiv.de/bestand/zettelkasten/inhaltsuebersicht)

      The zettelkasten structure allowed a familiar "folder" like top level structure, but the bibliographic and subject indices allowed them to interlink ideas from one space to the next for longer term work on multiple projects simultaneously.

  11. Mar 2022
    1. For Aboriginal Australians,its importance is recognised by its position at the centre of thenational Aboriginal flag, developed in 1971 by Luritja artist HaroldThomas.

      The Aboriginal flag was developed in 1971 by Luritja artist Harold Thomas. Centering its importance to Aboriginal Australians, the sun appears in the middle of the flag.


      It's subtle here, as in other instances, but notice that Hamacher gives the citation to the Indigenous artist that developed the flag and simultaneously underlines the source of visual information that is associated with the flag and the sun. It's not just the knowledge of the two things which are associated to each other, but they're also both associated with a person who is that source of knowledge.

      Is this three-way association common in all Indigenous cultures? While names may be tricky for some, the visual image of a particular person's face, body, and presence is usually very memorable and thereby easy to attach to various forms of knowledge.

      Does the person/source of knowledge form or act like an 'oral folder' for Indigenous knowledge?

    1. If you want to organize said migrations in their purpose you'll probably have a folder for the struture ones and another for the data ones.
    2. not as good/useful as some other gem options/approaches, such as the one that adds a data method per migration, or that lets you tag with :post_deploy, etc.

  12. Feb 2022
    1. In fact, my allegiance to Scrivener basically boils down to just three tricks that the software performs, but those tricks are so good that I’m more than willing to put up with all the rest of the tool’s complexity.Those three tricks are:Every Scrivener document is made up of little cards of text — called “scrivenings” in the lingo — that are presented in an outline view on the left hand side of the window. Select a card, and you see the text associated with that card in the main view.If you select more than one card in the outline, the combined text of those cards is presented in a single scrolling view in the main window. You can easily merge a series of cards into one longer card.The cards can be nested; you can create a card called, say, “biographical info”, and then drag six cards that contain quotes about given character’s biography into that card, effectively creating a new folder. That folder can in turn be nested inside another folder, and so on. If you select an entire folder, you see the combined text of all the cards as a single scrolling document.

      Steven Johnson identifies the three features of Scrivener which provide him with the most value.

      Notice the close similarity of these features to those of a traditional zettelkasten: cards of text which can be linked together and rearranged into lines of thought.

      One difference is the focus on the creation of folders which creates definite hierarchies rather than networks of thought.

  13. Oct 2021
    1. File structure
    2. Collapsing directories Say some directories in a project exist for organizational purposes only, and you prefer not to have them as namespaces. For example, the actions subdirectory in the next example is not meant to represent a namespace, it is there only to group all actions related to bookings: booking.rb -> Booking booking/actions/create.rb -> Booking::Create
  14. Jun 2021
    1. We’ve broken our project up into three different types of packages: apps which are preact apps intended to be bundled and deployed somewhere, modules which are plain npm packages for node/browsers and do not bundle their dependencies, and workers which are either Worker or ServiceWorker scripts entirely bundled up with no imports or exports. We don’t have to keep these three types of packages separated, but it helps us navigate around.
  15. Jul 2020
  16. Dec 2019
  17. burnsoftware.wordpress.com burnsoftware.wordpress.com
    1. Files are sorted by moving them all into a folder with today’s date, and you can organize these folders by day, week, or month.