https://lacountylibrary.libnet.info/event/9097350

https://www.youtube.com/watch?v=xMF37TXAV5w

Presenter Lawrence Mak broke down types of notes into the following three categories:<br /> - general notes (projects, ideas, journals, recipes, budgeting, homework, etc.)<br /> - lists (groceries, reading, gifts, to dos, assignments) - reminders (birthdays, bills, maintenance, health)

There's an interesting dichotomy which seems to be arising here. It's almost as if he's defining a folgezettel note in opposition to orphaned notes, most often seen in digital settings when importing lots of "stuff" but which Doto indicates can happen in analog systems as well.

Orphaned notes in an analog space, however are still linked by proximity even though they're not as densely linked (even from a mathematical topology perspective.)

"So long as it happens." And here lies the rub: when will you put in the work to make the note useful and actionable? Will it be now or later?

Some notes are certainly more mission critical than others. Some work towards one's life's work while others are tidbits which may be useful at a later time. Distinguishing along this spectrum isn't always easy, particular in build a bottom up view of one's research.

https://www.youtube.com/watch?v=vww7JLcrJl4

8:05 - 16:20 GTD - Capture - Clarify - What is it? - Is it actionable? What is the action? - Is it a project? - Batching - Reflect - Review over lists/calendars daily/weekly - Engage

17:30 They use the phrase "atomic" paper based index cards, so they've been infected by the idea of "atomic notes" from somewhere, though it seems as if he's pitching that he's "invented" his card system as if from scratch.

19:45 He mentions potentially using both sides of the card, against the usual (long term) advice.

20:00 Analogizes his cards as ballerinas which work together, but each have their own personalities and function within the ballet

He's using a leather cover for Moleskine pocket notebook and Manufactum A7 index cards, as well as a box

Sections of his box: - to erase - inbox - next actions - projects (3 categories of projects) - someday - to delegate - tickler (by month and by day; 12 months and 31 days) - blank cards

Mentions erasing cards as he finishes them rather than archiving them.

Inspiration by How to Take Smart Notes by Ahrens

Recommends one item per card to make things easier and more actionable; also improves focus versus having a longer list. (28:00)

Portability

Sustainable (he erases)

High quality textile experience

The ability to shift between associative modes and sequential modes seems to work well with such a system.

They distinguish between atomic notes and "stellar" notes. Stellar being longer lists or more dense notes/outlines/etc.

Project cards<br /> titles and project numbers (for reference) Project numbers in the top right with a P and/or M below it for<br /> - P for paper<br /> - M for email data<br /> - D for digital files which helps him find reference materials

Weekly review with all cards out on the table

Expansion pack includes: - action - calendar - waiting

Search was quick and easy, but had to carry his box back and forth to work.

Stopping doing it because he was losing the history (by erasing it). Moving to notebook and he likes fountain pens. He likes the calendar portion in his notebook.

He tried it out for the sake of experiment.

In the paper world things are more present and "in your face" versus digital formats where things can disappear.

reply to Edmund at https://forum.zettelkasten.de/discussion/comment/18550/#Comment_18550

@Edmund since I don't do such a thing myself, I'm curious what sort of affordance your #type/NoteName tagging provides you with (especially if you're using more than just those two)? Do you use them regularly for search or filtering, and if so for what reason? How does it help?

To me it look likes extra metadata/work, but without a lot of direct long term value in exchange. Does doing this for long periods of time provide you with outsized emergent value of some sort that's not easy to see from the start?

Not only a short description of the broad standard form of cards in Phyllis Diller's gag file, but also an enumeration of some of the non-standard cards, many of which are specified because of the issues which they presented in scanning/digitizing for transcription.

https://www.dtsheffler.com/blog/2014-07-21-two-goals-of-note-taking/ archive version: https://web.archive.org/web/20220528093415/https://www.dtsheffler.com/blog/2014-07-21-two-goals-of-note-taking/

ᔥ[[abramdemski]] in The Zettelkasten Method (accessed:: 2023-08-25 12:00:07)

This is the first time I've seen someone use the phrase "ghost note" to mean a future implied note which could be created by using wiki syntax [[*]] which in some systems like Obsidian or WikiMedia creates a (red) link which one could click on to create that note.

via u/THX-Eleven38 at https://www.reddit.com/r/Zettelkasten/comments/14ox2tw/what_is_the_proper_way_to_create_a_moc_note_from/

forms of rhythmic displacement

Despite being used primarily as a productivity tool the PoIC system also included some features of personal knowledge management with "discovery cards" and "citation cards". Discovery cards were things which contained one's own ideas while the citation cards were the ideas of others and included bibliographic information. Citation cards were tagged on the 5th block as an indicator within the system.

Question: How was the information material managed? Was it separate from the date-based system? On first blush it would appear not, nor was there a subject index which would have made it more difficult for one to find data within the system.

Within the pantheon of types of notes there are: - paraphrasing notes, which one can use to summarize ideas for later recall and review as well as to check one's own knowledge and understanding of what an author has said. - commentary notes, which take the text and create a commentary on them, often as part of having a conversation with the text. These can be seen historically in the Midrashim tradition of commenting on Torah.

[23:12 - 24:47]

separately also: - productivity notes - to do lists, reminders of work to be done, often within or as part of a larger complex project

Notes can be used for different purposes.

• productivity
• Knowledge
  • basic sense-making
  • knowledge construction and dispersion

The broad distinction is between productivity goals and knowledge. (Is there a broad range I'm missing here within the traditions?) You can take notes about projects that need to be taken care of, lists of things to do, reminders of what needs to be done. These all fall within productivity and doing and checking them off a list will help one get to a different place or location and this can be an excellent thing, particularly when the project was consciously decided upon and is a worthy goal.

Notes for knowledge sake can be far more elusive for people. The value here generally comes with far more planning and foresight towards a particular goal. Are you writing a newsletter, article, book, or making a video or performance of some sort (play, movie, music, etc.)? Collecting small pieces of these things on a pathway is then important as you build your ideas and a structure toward some finished product.

Often times, before getting to this construction phase, one needs to take notes to be able to scaffold their understanding of a particular topic. Once basically understood some of these notes may be useless and not need to be reviewed, or if they are reviewed, it is for the purpose of ensconcing ideas into long term memory. Once this is finished, then the notes may be broadly useless. (This is why it's simple to "hide them with one's references/literature notes.) Other notes are more seminal towards scaffolding ideas towards larger projects for summarization and dissemination to other audiences. If you're researching a topic, a fair number of your notes will be used to help you understand the basics while others will help you to compare/contrast and analyze. Notes you make built on these will help you shape new structures and new, original thoughts. (note taking for paradigm shifts). These then can be used (re-used) when you write your article, book, or other creative project.

Raul Pacheco-Vega uses five different types of index cards (notes): - direct quotations - bibliographic references - one idea index card (a major idea or them in one or two sentences) - summaries - combined (or content) index card

Pacheco-Vega defines a "combined" or "content index card" or one might say a content note as a one with "direct quotations, draft notes and ideas, conceptual diagrams, etc. that are associated with" the work in question. These seem similar to Ahrens' fleeting notes, though seem a bit more fleshed out.

.

a subtle catch about Ahrens' terminology

I take it there's different protocols within the http based on content.

https://www.reddit.com/r/Zettelkasten/comments/zl2hwh/is_the_concept_of_personal_knowledge_management/

This essay seems to be more about shiny object syndrome. The writer doesn't seem to realize any problems they've created. Way too much digging into tools and processes. Note the switching and trying out dozens of applications. (Dear god, why??!!) Also looks like a lot of collecting digitally for no clear goal. As a result of this sort of process it appears that many of the usual affordances were completely blocked, unrealized, and thus useless.

No clear goal in mind for anything other than a nebulous being "better".

One goal was to "retain what I read", but nothing was actively used toward this stated goal. Notes can help a little, but one would need mnemonic methods and possibly spaced repetition neither of which was mentioned.

A list of specific building blocks within the methods and expected outcomes would have helped this person (and likely others), but to my knowledge this doesn't exist as a thing yet though bits and pieces are obviously floating around.<br /> TK: building blocks of note taking

Evidence here for what we'll call the "perfect system fallacy", an illness which often goes hand in hand with "shiny object syndrome".

Too many systems bound together will create so much immediate complexity that there isn't any chance for future complexity or emergence as the proximal system is doomed to failure. One should instead strive for immediate and excessive simplicity which might then build with time, use, and practice into something more rich and complex. This idea seems to be either completely missed or lost in the online literature and especially the blogosphere and social media.

people had come up with solutions Sadly, despite thousands of variations on some patterns, people don't seem to be able to settle on either "one solution" or their "own solution" and in trying to do everything all at once they become lost, set adrift, and lose focus on any particular thing they've got as their own goal.

In this particular instance, "retaining what they read" was totally ignored. Worse, they didn't seem to ever review over their notes of what they read.

I was pondering about different note types, fleeting, permanent, different organisational systems, hierarchical, non-hierarchical, you know the deal.

Why worry about all the types of notes?! This is the problem with these multi-various definitions and types. They end up confusing people without giving them clear cut use cases and methods by which to use them. They get lost in definitional overload and aren't connecting the names with actual use cases and affordances.

I often felt lost about what to takes notes on and what not to take notes on.

Why? Most sources seem to have reasonable guidance on this. Make notes on things that interest you, things which surprise you.

They seem to have gotten lost in all the other moving pieces. Perhaps advice on this should come first, again in the middle, and a third time at the end of these processes.

I'm curious how deeply they read sources and which sources they read to come to these conclusions? Did they read a lot of one page blog posts with summarizations or did they read book length works by Ahrens, Forte, Allosso, Scheper, et al? Or did they read all of these and watch lots of crazy videos as well. Doing it "all" will likely lead into the shiny object syndrome as well.

This seems to outline a list of specifically what not to do and how not to approach these systems and "popular" blog posts that are an inch deep and a mile wide rather than some which have more depth.

Worst of all, I spent so much time taking notes and figuring out a personal knowledge management system that I neglected the things I actually wanted to learn about. And even though I kind of always knew this, I kept falling into the same trap.

Definitely a symptom of shiny object syndrome!

Yet another new name for a sub-type of notes, here he uses reformulation notes as a shorthand for the old advice to rewrite ideas you find in your own words. This advice is often suggested to accomplish two things: - avoid plagiarism - restatement of ideas in your own words is related to the Feynman Technique and assists one in learning and ensuring they understand the concepts

There are several unique ways to foster a discussion within a class setting. Some of these include-

• Small Group Discussions - three to eight people
• Think-Pair-Share - individually or in pairs, then share to a large group

• Large Group Discussions- group of students

• Brainstorming - group of students

All of these contribute to ideas being shared and analyzed by the individuals involved. This also helps to build great communication skills as well as team building skills.

https://wordpress.org/plugins/shortnotes/

This fits perfectly with the four main types defined by Insights Discovery and DISC:

• Dopamine-dominant: Yellow
• Testosterone-dominant: Red
• Serotonin-dominant: Blue
• Estrogen-dominant: Green

Dialectical notes are made at the level of syntopical reading and entail creating a conversation not only between the reader and the author, but create a conversation of questions and answers between and among many texts and the reader.

Conceptual notes are made during the analytical reading of a book and "give answers to questions about the truth and significance of the book."

Adler and Van Doren define structural note making as the sorts of questions one might ask at the level of inspectional reading including: - what kind of book is it? - what is it about? - what is the overall structure with respect to the argument the author intends to make?

This article explains the economic market. Creating 528,000 jobs is an outstanding aspect for the American people. But It also needs to explain the bad parts of creating jobs in this situation. Because challenging the rules of economics should not make a better situation, There are also high risks.

This article describes the disadvantages of high-interest rates. Although there are facts and parts that we need to be concerned about, high-interest rates also have advantages. There are more information about advantages about high-interest.

If you give a title to your notes, "claim notes" are simply notes with a verb.<br><br>They invite you to say: "Prove it!"<br><br>- "The positive impact of PKM" (not a claim)<br>- "PKM has a positive impact in improving writer's block" (claim)<br><br>A small change with positive mindset consequences

— Bianca Pereira | PKM Coach and Researcher (@bianca_oli_per) October 6, 2022

Bianca Pereira coins the ideas of "concept notes" versus "claim notes". Claim notes are framings similar to the theorem or claim portion of the mathematical framing of definition/theorem(claim)/proof. This set up provides the driving impetus of most of mathematics. One defines objects about which one then advances claims for which proofs are provided to make them theorems.

Framing one's notes as claims invites one to provide supporting proof for them to determine how strong they may or may not be. Otherwise, ideas may just state concepts which are far less interesting or active. What is one to do with them? They require more active work to advance or improve upon in more passive framings.

link to: - Maggie Delano's reading framing: https://hypothes.is/a/4xBvpE2TEe2ZmWfoCX_HyQ

https://www.loom.com/share/a05f636661cb41628b9cb7061bd749ae

Synopsis: Maggie Delano looks at some of the affordances supplied by Tana (compared to Roam Research) in terms of providing better block-based user interface for note type creation, search, and filtering.

These sorts of tools and programmable note implementations remind me of Beatrice Webb's idea of scientific note taking or using her note cards like a database to sort and search for data to analyze it and create new results and insight.

It would seem that many of these note taking tools like Roam and Tana are using blocks and sub blocks as a means of defining atomic notes or database-like data in a way in which sub-blocks are linked to or "filed underneath" their parent blocks. In reality it would seem that they're still using a broadly defined index card type system as used in the late 1800s/early 1900s to implement a set up that otherwise would be a traditional database in the Microsoft Excel or MySQL sort of fashion, the major difference being that the user interface is cognitively easier to understand for most people.

These allow people to take a form of structured textual notes to which might be attached other smaller data or meta data chunks that can be easily searched, sorted, and filtered to allow for quicker or easier use.

Ostensibly from a mathematical (or set theoretic and even topological) point of view there should be a variety of one-to-one and onto relationships (some might even extend these to "links") between these sorts of notes and database representations such that one should be able to implement their note taking system in Excel or MySQL and do all of these sorts of things.

Cascading Idea Sheets or Cascading Idea Relationships

One might analogize these sorts of note taking interfaces to Cascading Style Sheets (CSS). While there is the perennial question about whether or not CSS is a programming language, if we presume that it is (and it is), then we can apply the same sorts of class, id, and inheritance structures to our notes and their meta data. Thus one could have an incredibly atomic word, phrase, or even number(s) which inherits a set of semantic relationships to those ideas which it sits below. These links and relationships then more clearly define and contextualize them with respect to other similar ideas that may be situated outside of or adjacent to them. Once one has done this then there is a variety of Boolean operations which might be applied to various similar sets and classes of ideas.

If one wanted to go an additional level of abstraction further, then one could apply the ideas of category theory to one's notes to generate new ideas and structures. This may allow using abstractions in one field of academic research to others much further afield.

The user interface then becomes the key differentiator when bringing these ideas to the masses. Developers and designers should be endeavoring to allow the power of complex searches, sorts, and filtering while minimizing the sorts of advanced search queries that an average person would be expected to execute for themselves while also allowing some reasonable flexibility in the sorts of ways that users might (most easily for them) add data and meta data to their ideas.

Jupyter programmable notebooks are of this sort, but do they have the same sort of hierarchical "card" type (or atomic note type) implementation?

For the second time Goutor mentions using different size cards for different note types, but doesn't specifically advise for it or provide a reason. Perhaps his advice for consistency and card size applies only to cards of particular types? (p28)

link to: https://hypothes.is/a/XPphjkNZEe2s3i9VV4qt1g

Incidentally he also specifically mentions 7x9" cards here too. How frequently used were these as a standard?

Jacques Goutor defines content notes as those that "are drawn in one way or another from the actual contents of the sources." He considers them the most important part of note taking as "they will eventually constitute the pieces of the mosaic." (p20)

He further breaks this type down into generally self-explanatory "quote notes" and "summary notes". (p20) He does advise that one writes out careful summaries so that one needn't do additional future work of writing notes on one's own notes. While he doesn't state it directly, the presumption in his presentation is that a well written summary can be directly used in one's future written project.

Compare this type of note to others like evergreen or permanent notes.

Goutor acknowledges that there are a variety of note types, but focuses on bibliographic notes, content notes, and self-help notes as being the most common and most important. (p12)

These first two are broadly self-explanatory, but the third should be intriguing given the other literature in which this type is rarely, if ever, used. We'll see what comes of it...

bibnote is another I've seen

Do we really need another new sets of names?! ;)

One day all of these different types will eventually be canonical...

https://notes.andymatuschak.org/z6f6xgGG4NKjkA5NA1kDd46whJh2Gt5rAmfX

Julius Reizen in reviewing over Umberto Eco's index card system in How to Write a Thesis, defines his own "insurance card" as one which contains "hard-to-classify thoughts, questions, and areas for further inquiry". These he would keep together so that they don't otherwise get lost in the variety of other locations one might keep them

These might be akin to Ahrens' "fleeting notes" but are ones which may not easily or even immediately be converted in to "permanent notes" for one's zettelkasten. However, given their mission critical importance, they may be some of the most important cards in one's repository.

link this to - idea of centralizing one's note taking practice to a single location

Is this idea in Eco's book and Reizen is the one that gives it a name since some of the other categories have names? (examples: bibliographic index cards, reading index cards (aka literature notes), cards for themes, author index cards, quote index cards, idea index cards, connection cards). Were these "officially" named and categorized by Eco?

May be worthwhile to create a grid of these naming systems and uses amongst some of the broader note taking methods. Where are they similar, where do they differ?

Multi-search tools that have full access to multiple trusted data stores (ostensibly personal ones across notebooks, hard drives, social media services, etc.) could potentially solve the problem of needing to remember where you noted something.

Currently, in the social media space especially, this is not a realized service.

I could swear that there's a suggestion in WordPress Trac for creating a custom post type for comments somewhere.

Successful problem solving requires having the ability to adaptively and flexibly focus one's attention with respect to the demands of the work. Having a toolbelt of potential methods and combinatorially working through them can be incredibly helpful and we too often forget to explicitly think about doing or how to do that.

This is particularly important in mathematics where students forget to look over at their toolbox of methods. What are the different means of proof? Some mathematicians will use direct proof during the day and indirect forms of proof at night. Look for examples and counter-examples. Why not look at a problem from disparate areas of mathematical thought? If topology isn't revealing any results, why not look at an algebraic or combinatoric approach?

How can you put a problem into a different context and leverage that to your benefit?

It should be recognized that these basic note types are very different than the digital garden framing of 📤 (seedbox), 🌱 (seedling), 🪴 (sapling), 🌲 (evergreen), etc. which are another measure of the growth and expansion of not just one particular idea but potentially multiple ideas over time. These are a project management sort of tool for focusing on the growth of ideas. Within some tools, one might also use graph views and interconnectedness as means of charting this same sort of growth.

Sönke Ahrens' framing of fleeting note, literature note, and permanent note are a value assignation to the types of each of these notes with respect to generating new ideas and writing.

The writer uses a claim of value, saying school is meant to be a safe place for learning, and implying that when minors or exercising shirtless, school is no long such a place, but rather dangerous and an unfit place for learning.

The speaker of the text is using a claim of value, stating that minors should not be able to exercise or be on school property without a shirt covering specifically bras. The speaker believes age to be a main contributor. The speaker is stating because of age, it is wrong to allow minors to exercise on school property. This is the speakers point of view.

Tests are a good thing, but not all devs are even aware of the loss of safety net and so there's no guarantee that using a dynamic language results in more tests.

Using tests and static-types together would mean that there's whole categories of bugs that get eliminated while also getting more coverage for less lines of test-code.

https://www.typescriptlang.org/docs/handbook/utility-types.html#parameterstype

Schopenhauer made easy:

There are two kinds of people in this world. Avoid both of them.

pg_typeof

An allergy that occurs in a particular season is known as a seasonal allergy. The best way to avoid allergies is that you should know allergy types and symptoms and take precautions according to that. In India, there are only 3 prominent seasons- summer, monsoon, and winter. All three can cause different allergies and can trigger different seasonal allergy symptoms but the most common of them is hay fever. Read the article to know more about allergies.

.

Original post is here.

This explanation should be combined with 24 Days of GHC Extensions: Rank N Types (see related hypothes.is note).

From Turning a map of data constructors into a row type (purescript discourse):

rows don’t have corresponding values, they only exist at the type level. If you do only purely want a row and not something like a Variant result you could return a proxy though.

My main issue with this book is that the difficulty is exponentially increasing, and by "keeping it simple" (i.e., trying to use simple terms) it is even harder to do a proper research.

For example:

1. The name of this chapter

This chapter should have been called Explicitly quantified type or Explicit universal quantification as it is too general as is, and doing a search to get to know more when someone has no formal/previous functional programming background, makes very hard.

Most importantly though, even if Haskell not mentioned, the word "explicit" would have been important.

It is also more about generic parameters than about quantification itself, and forall is kind of introduced but it is totally misleading.

2. forall

The post “forall” is the type-level “lambda” (saved) is the best, most succinct explanation of forall that I ever found. Unfortunately not before going down the rabbit hole.. (See links below.) One still needs to know about

• typeclasses
• generic parameters
• constraints
• what pragmas are but after that, it is straightforward.

(Jordan's Reference section on forall also doesn't help much.)

forall is also mandatory in PureScript (which is also not mentioned when introducing it), and I believe a comparison (the way the above post did) with Haskell is important, but at the right time. At least Jordan's Reference tries to put it off until later, but still before explaining concepts required to understand it.

3. The "rabbit hole" links

These are all good resources, but not for uninitiated mortals, and at a lower level (such as where I am now) they raise more questions than answers.

• Explicit forall (r/purescript reddit)]

  (Started here initially, but the single sentence there prompted a search for scoped type variables and rank-n types (or Rank N types).)

Type system is the foundation of GraphQL