programming languages and flashcards

Author: codekiln

journals/2026_03_17.md

@@ -1,7 +1,7 @@
 - [[Filed]]
 	- [[tmux/Q/How can I refresh .zshrc in all of my open panes and windows in tmux?]]
 - [[tmux/Keyshort/Window/Close Window]]
-	- Filled out with a #card flashcard: shortcut `<prefix> &` then `y`, CLI `tmux kill-window` (and `-t` for a specific window), and mouse method via [[tmux/Window/Right Click]].
+	- Filled out with a flashcard: shortcut `<prefix> &` then `y`, CLI `tmux kill-window` (and `-t` for a specific window), and mouse method via [[tmux/Window/Right Click]].
 - [[TIL]]
 	- Learned that one can right-click a tmux window name in the status bar to get a context menu (e.g. Kill / close that window). Recorded what that does in [[tmux/Window/Right Click]].
 	- [[tmux/Window/Right Click]]

journals/2026_04_08.md

@@ -1,5 +1,17 @@
-## Filed
-	- [[Numtide]] does [[Nix]] packages for [[Agentic Coding Tool]]s
+## [[Filed]]
+	- ### [[Numtide]] does [[Nix]] packages for [[Agentic Coding Tool]]s
 		- [[Numtide/llm-agents.nix]]
+			- #### [[Learning]] nix
+				- I'm getting to know more of nix's surface area and some of its drawbacks.
+				- ##### What I want
+					- easily keep dependencies up to date (within at least two weeks of freshness)
+					- quickly add a new cli tool, whether that's on pip or npm or some other system
+				- ##### What I have so far
+					- what works
+						- there is often a way to do it in the nix ecosystem, whether that's managing [[dotfiles]] with [[Nix/home-manager]], managing system-level dependencies, managing [[Python Versions]], managing [[NodeJS/v]]
+					- what doesn't
+						- [[nixpkgs]] is often lagging a month to a year behind the latest packages in terms of freshness
+							- it takes time to find yet alone vet community-submitted package collections (such as [[Numtide]])
+							- it's unclear whether security solutions like [[HeelerAI]] or [[Snyk]] are going to work well with [[Nix]]; they seem pretty oriented at more traditional package managers
 	- [[GitHub/CoPilot/CLI/BYOK]]
 	- [[GitHub/CoPilot/CLI/Install/Nix]]

journals/2026_04_09.md

@@ -0,0 +1,27 @@
+## en garde(ning)
+	- ### getting carded
+		- Did some flashcards this morning. The [[Logseq/Flashcard/Review]] UI (the one in the side-panel) is a bit confusing. It  has a drop down menu to select different categories of flashcards, which in theory is convenient. Currently, in this garden, though, many items appear more than once, and some of the items that appear in the menu don't have any flashcards. In addition, right now I'm not prioritizing VSCode flashcards anymore (though I do still need a few; for example, being able to see the log after rebuilding devcontainers is a good one).
+		- I should probably have a better precedent for how to log [[Logseq/Flashcard]]s that are not [[Keyshort]]s; I don't want to stuff [[CLI commands]] and [[GUI/Menu/Command]]s into keyshorts if it isn't actually a [[Keyboard Shortcut]].  It might make sense to somehow tie this to my nascent [[Logseq/Entity]] system.
+	- ### on my burgeoning [[Logseq/Entity]] system
+		- It's been bugging me that the current [[Logseq/Frontmatter/Key]] for it, `logseq-entity`, implies a singular entity in a page, when really, a page may need to document more than one entity.
+			- for example, something can be a term, and also a concept, and also a software-project.
+		- This makes me wonder about how to more clearly identify *what* I'm saying a logseq entity *is*.
+			- #### [[Taxonomy]]?
+				- Is it a page that is intended to have certain structural elements?
+					- One of the motivating factors was to provide [[AI Knowledge Gardening]] with [[AI/Context]] about how to import an entity like a book or a software project. If it's the case that I'm thinking of an entity as being more like a "page template" or a "page schema" - or, and let's be more accurate here, is it more like structural typing in programming languages, except instead of describing methods and properties, the entities describe page frontmatter and headings
+					- A key aspect of how I use logseq is that I create a page so that I can refer to something by name.
+						- Usually I do this with a logseq `tags:: [[Term]]` frontmatter entry. Usually I place the term at a logical location in the namespaces for where I want it to be sorted on disk, lexicographically, so that when I look at the files in the [[Logseq/Page]] pages directory, it works a bit like [[Library/Science/Classification/Dewey]] or [[Library/Science/Classification/Library of Congress]]
+				- Is it a type of [[Digital Twin]]
+- ## garddiff
+	- ### [[Filed]]
+		- [[Programming/Language/Concept/Interface]]
+		- [[Programming/Language/Concept/Type/Nominal]]
+		- [[Programming/Language/Concept/Type/Structural]]
+		- [[Library/Science/Classification]]
+		- [[Library/Science/Classification/Dewey]]
+		- [[Library/Science/Classification/Library of Congress]]
+		- [[tmux/Q/Why doesn't prefix Alt-Left or Alt-Right resize the inner horizontal split in a nested tmux layout (outer top-bottom split and lower left-right split), while Alt-Up or Alt-Down still move the outer boundary?]]
+	- ### [[Updated]]
+		- [[Knowledge/Garden/ing/AI]]
+	- ### [[Review]]
+		- [[tmux/Q/Is there a way to do rectangular selection when using oh-my-tmux and tmux with vim visual selection mode?]] still haven't figured this out.

pages/CSharp.md

@@ -0,0 +1 @@
+alias:: [[C#]], [[Programming/Language/General Purpose/CSharp]]

pages/Knowledge___Garden___ing___AI.md

@@ -1,4 +1,4 @@
-alias:: [[AI Knowledge Gardening]]
+alias:: [[AI Knowledge Gardening]], [[AI/Knowledge/Gardening]] 
 tags:: [[Term]]
 
 - # #AI #[[Knowledge Gardening]]

pages/Kotlin.md

@@ -0,0 +1 @@
+alias:: [[Programming/Language/General Purpose/Kotlin]]

pages/Lazygit___Keyshort___Pull.md

@@ -1,10 +1,10 @@
 - [[Keyshort]] [[Lazygit]] [[Lazygit/Keyshort]]
 	- **Pull** #card
-	  card-last-interval:: 4
-	  card-repeats:: 2
+	  card-last-interval:: -1
+	  card-repeats:: 1
 	  card-ease-factor:: 2.7
-	  card-next-schedule:: 2026-04-06T05:53:23.910Z
-	  card-last-reviewed:: 2026-04-02T05:53:23.910Z
-	  card-last-score:: 5
+	  card-next-schedule:: 2026-04-10T04:00:00.000Z
+	  card-last-reviewed:: 2026-04-09T07:31:52.346Z
+	  card-last-score:: 1
 		- Shortcut: `p`
 		- Description: Performs a git pull

pages/Library___Science___Classification.md

@@ -0,0 +1,26 @@
+logseq-entity:: [[Logseq/Entity/concept]]
+tags:: [[Diataxis/Concept]]
+alias:: [[Bibliographic classification]], [[Library classification scheme]]
+see-also:: [[Library/Science/Classification/Dewey]], [[Library/Science/Classification/Library of Congress]], [[Taxonomy]]
+
+- # Library classification
+	- ## Overview
+		- **Library classification** (often **bibliographic classification**) assigns **notation** — usually a **call number** — so items can be **shelved in a predictable subject order** and browsed alongside neighbors that treat the same topic.
+		- It is one kind of **knowledge organization system**; it supports **collocation** (related works together) and a **stable shelf address**, distinct from the vocabulary used in **subject headings** or abstracts.
+	- ## Context
+		- Evolved alongside **modern cataloging** (descriptive rules, authority control); discovery today is often **online**, but spine labels still encode schedule choices for **physical** collections.
+		- Major **Anglo-American** schemes include **[[Library/Science/Classification/Dewey]]** (common in public and school libraries) and **[[Library/Science/Classification/Library of Congress]]** (common in large academic and research collections in the United States).
+		- Compare **[[Taxonomy]]** and other hierarchical knowledge organization: classification schedules are **engineered for bibliographic collections**, with tables, optional facets, and **cutter** numbers that go beyond a simple tree of labels.
+	- ## Key principles
+		- **Enumerative structure** — Schedules list **pre-coordinated** classes and subdivisions (DDC and LCC are largely enumerative; schemes such as **UDC** layer **facets** more explicitly).
+		- **Hierarchical notation** — Digits or letters often encode **broader-to-narrower** order so sorting the string sorts the concepts.
+		- **Stability vs revision** — Editors **relocate** or **expand** topics as disciplines shift; changes ripple into **relabeled** spines and **browse** indexes.
+	- ## Mechanism
+		- A classifier maps a work’s **aboutness** to schedule entries, then builds a **call number** (class + **book number** / **cutter**, plus local conventions and volume suffixes).
+		- **Relative indexes** (DDC) and **subject-heading** cross-references help mapping, but **classification** and **subject headings** answer different retrieval jobs.
+	- ## Examples
+		- **[[Library/Science/Classification/Dewey]]** — Decimal hierarchies from ten top-level classes.
+		- **[[Library/Science/Classification/Library of Congress]]** — Letter-and-number **classes** aligned with Library of Congress collections.
+	- ## Misconceptions
+		- “Classification equals cataloging” — **Too broad**; cataloging includes **description** and **access points**; classification is the **shelf-ordering notation** slice.
+		- “Call number encodes year or edition” — **Usually false**; it is primarily **subject + author/title key**; local policy varies.

pages/Library___Science___Classification___Dewey.md

@@ -0,0 +1,25 @@
+logseq-entity:: [[Logseq/Entity/concept]]
+tags:: [[Diataxis/Concept]]
+alias:: [[Dewey Decimal Classification]], [[DDC]]
+see-also:: [[Library/Science/Classification/Library of Congress]], [[Taxonomy]]
+
+- # Dewey Decimal Classification
+	- ## Overview
+		- The **Dewey Decimal Classification (DDC)** is a **decimal**, **hierarchical** library classification: **ten main classes**, subdivided with **dot notation** so longer strings mean **narrower** subjects [^1].
+		- Maintained under **OCLC**; widely used in **public**, **K–12**, and many **small academic** libraries because a single integral number sorts cleanly on the shelf.
+	- ## Context
+		- First published **1876** by **Melvil Dewey**; revised across many editions with **relocations** (notably in science and computing) as disciplines evolve.
+		- Contrasts with **[[Library/Science/Classification/Library of Congress]]**, which is **letter-led** and organized as **separate class schedules** tied to the Library of Congress print corpus.
+	- ## Key principles
+		- **Ten classes** (000–900) at the top level; further digits express **narrower** facets within each class.
+		- **Relative Index** — Alphabetical index from natural-language terms to table numbers.
+		- **Standard subdivisions** — Recurring patterns (history, geographic treatment, etc.) reused where the schedule allows.
+	- ## Mechanism
+		- Build a **class number** from the schedules (and optional **auxiliary tables** for area, period, language); append **book number** or local **cutter** so each **item** has a unique shelf string.
+	- ## Examples
+		- **500** natural sciences; **630** agriculture; computer-related classes illustrate how **discipline drift** is absorbed through **edition** updates rather than ad hoc local patches.
+	- ## Misconceptions
+		- “Dewey stops at three digits” — **False**; practical call numbers are often **much longer** for specificity.
+		- “Decimal means the schedule is about arithmetic” — **Wrong sense**; **decimal** names the **notation**, not the subject matter.
+	- ## Footnotes
+		- [^1]: https://www.oclc.org/en/dewey.html

pages/Library___Science___Classification___Library of Congress.md

@@ -0,0 +1,25 @@
+logseq-entity:: [[Logseq/Entity/concept]]
+tags:: [[Diataxis/Concept]]
+alias:: [[Library of Congress Classification]], [[LCC]]
+see-also:: [[Library/Science/Classification/Dewey]], [[Taxonomy]]
+
+- # Library of Congress Classification
+	- ## Overview
+		- **Library of Congress Classification (LCC)** is an **alphanumeric** bibliographic scheme: **capital letters** name **broad classes**, with **subclasses** and **number spans** developed for the **Library of Congress** collections and acquisitions patterns [^1].
+		- Common in **research** and **academic** libraries in the United States; **not** the same system as **Library of Congress Subject Headings (LCSH)**, though both support **subject access**.
+	- ## Context
+		- Developed across the **late 19th** and **20th** centuries as LC grew; schedules publish **class by class** (for example **H** social sciences, **QA** mathematics).
+		- **[[Library/Science/Classification/Dewey]]** uses one **decimal** stem for all fields; LCC uses **modular letter schedules**, which suits **large** stacks maintained **discipline by discipline**.
+	- ## Key principles
+		- **Class letters** (A–Z with historical gaps and special cases such as **Z** bibliography).
+		- **Hierarchy inside each schedule** — Subtopics narrow as notation grows; **Cutter numbers** (or local equivalents) distinguish **authors and titles** at the end of the string.
+		- **Schedule maintenance** — Classes can revise on **different** cycles compared to a single integrated edition story.
+	- ## Mechanism
+		- Select the **schedule volume** for the discipline; assign **class number**; add **cutter** from **Cutter tables** or vendor-assisted tools; append **volume/copy** suffixes per local policy.
+	- ## Examples
+		- **K** law; **QD** chemistry — illustrate **depth** that lives inside a **letter class** rather than a single global decimal hierarchy.
+	- ## Misconceptions
+		- “Every book with an LC call number was classified at the Library of Congress” — **Not guaranteed**; many libraries **adapt** LCC locally.
+		- “LCC replaced Dewey in all academic libraries” — **False**; **choice** depends on history, consortium, and **migration** cost.
+	- ## Footnotes
+		- [^1]: https://www.loc.gov/aba/cataloging/classification/lcc.html