vault backup: 2026-02-02 17:10:34

.gitignore

@@ -3,9 +3,4 @@
 /.obsidian/plugins/recent-files-obsidian/data.json
 /.obsidian/plugins/novel-word-count/data.json
 /out/
-
-
-
-
-# Ignore Smart Environment folder
-.smart-env
+/ref/

.obsidian/plugins/pdf-plus/data.json

@@ -110,8 +110,8 @@
   "recordPDFInternalLinkHistory": true,
   "alwaysRecordHistory": true,
   "renderMarkdownInStickyNote": false,
-  "enablePDFEdit": false,
-  "author": "",
+  "enablePDFEdit": true,
+  "author": "ZaneMeyers",
   "writeHighlightToFileOpacity": 0.2,
   "defaultWriteFileToggle": false,
   "syncWriteFileToggle": true,

2026-02-01.md

@@ -10,6 +10,3 @@ tags:
 dg-publish: true
 ---
 # 2026-02-01
-
-## 2026-02-01 08:51
-

2026-02-02.md

@@ -53,9 +53,47 @@ function Import-Markdown {
 }
 ```
 
-That pattern is bizarre, and it needs better error handling,
+That match expression is bizarre,
+and the whole thing needs better error handling,
 but it works.
 
 A `Where-Markdown` for filtering by tags
 and a `{Verb}-Markdown` for modifying tags
 would be idiomatic.
+
+## 2026-02-02 12:18
+
+### Sleeving Takeoff Breakdown Direction
+
+Updated [[sleeving-takeoff#Breakdowns]]
+per clarification with Joel.
+Previous direction below.
+
+> * `Area` = "01 - Feeders/Risers ..."
+> * `Phase` = "Feeders"
+> * `System` = "FRR - Feeders and Risers"
+> 
+> For all sleeving, regardless of application.
+
+I feel certain I received this from someone I trust
+because I've been doing it against my better judgement,
+but either it wasn't Joel (Ben maybe?)
+or he was referring to a different scenario
+(which my notes no longer cover).
+
+***
+
+I asked Joel if he could think of any direction
+that I might have misinterpreted
+to get to that above,
+but he said he could not.
+
+***
+
+I spoke with Willie about it,
+he says he's always put sleeving in each relevant system.
+I told him I knew it had to have been spoken
+because I remember it being justified as WBS allocation thing,
+but I think now Joel told me correctly at the time,
+that is, gave me the same direction he gave me today,
+I just somehow heard the complete opposite.

how-to-measure-anything-in-project-management.md

@@ -0,0 +1,10 @@
+---
+id:
+aliases: []
+title: _How to Measure Anything in Project Management_
+tags: []
+---
+# _How to Measure Anything in Project Management_
+
+> [!quote] [[How to Measure Anything in Project Management - Douglas W. Hubbard & Alexander Budzier & Andreas Bang Leed.pdf#page=112&selection=40,0,41,60]]
+> The analogy of this to project planning is that we can keep trying to design better solutions to a problem before we commit to it.

sleeving-takeoff.md

@@ -32,11 +32,10 @@ Seek additional clarification.
 
 ## Breakdowns
 
-* `Area` = "01 - Feeders/Risers ..."
-* `Phase` = "Feeders"
-* `System` = "FRR - Feeders and Risers"
-
-For all sleeving, regardless of application.
+> [!quote] Joel Jansen 2026-02-02 12:10, while reviewing Howard University East Towers (pp.)
+> Match breakdowns of the relevant system,
+> i.e. don't change breakdowns after taking off
+> the assembly to be sleeved.
 
 ## Item Selection