vault backup: 2026-02-04 17:41:43

.obsidian/plugins/obsidian-linter/data.json

@@ -148,7 +148,7 @@
       "enabled": true,
       "single-quote-enabled": true,
       "single-quote-style": "''",
-      "double-quote-enabled": true,
+      "double-quote-enabled": false,
       "double-quote-style": "\"\""
     },
     "remove-consecutive-list-markers": {

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

@@ -221,9 +221,9 @@
   "clearSelectionAfterAutoPaste": true,
   "respectCursorPositionWhenAutoPaste": true,
   "blankLineAboveAppendedContent": true,
-  "autoCopy": false,
+  "autoCopy": true,
   "autoFocus": false,
-  "autoPaste": false,
+  "autoPaste": true,
   "autoFocusTarget": "last-active-and-open-then-last-paste",
   "autoPasteTarget": "last-active-and-open-then-last-paste",
   "openAutoFocusTargetIfNotOpened": true,
@@ -234,11 +234,11 @@
   "executeCommandWhenTargetNotIdentified": true,
   "commandToExecuteWhenTargetNotIdentified": "switcher:open",
   "autoPasteTargetDialogTimeoutSec": 20,
-  "autoCopyToggleRibbonIcon": true,
+  "autoCopyToggleRibbonIcon": false,
   "autoCopyIconName": "highlighter",
   "autoFocusToggleRibbonIcon": true,
   "autoFocusIconName": "zap",
-  "autoPasteToggleRibbonIcon": true,
+  "autoPasteToggleRibbonIcon": false,
   "autoPasteIconName": "clipboard-paste",
   "viewSyncFollowPageNumber": true,
   "viewSyncPageDebounceInterval": 0.3,

2026-02-04.md

@@ -89,3 +89,75 @@ incentivize problematic (hare-hunting) behavior.
 Has such behavior been observed,
 or has chief strategy been organization-aligned
 in spite of the incentive?
+
+## 2025-02-04
+
+### T-Shirt Sizing
+
+"T-shirt sizing" or "T-shirt size estimation"
+is a method of project estimation
+characterized by the use of T-shirt sizes
+representing project scale buckets.
+
+> [!example]
+> * **XS (1-2 days):** Simple UI changes or minor bug fixes
+> 
+>   Example: "Update button color on checkout page"
+>
+> * **S (2-3 days):** Feature enhancements with minimal complexity
+> 
+>   Example: "Add product sorting by price"
+>
+> * **M (5-7 days):** Features requiring moderate integration
+>
+>   Example: "Implement basic search filters"
+>
+> * **L (8-10 days):** Complex features affecting multiple components
+> 
+>   Example: "Create shopping cart functionality"
+>
+> * **XL (2+ weeks):** Major features requiring breaking down
+> 
+>   Example: "Implement payment gateway integration"
+>
+> --- [T-Shirt Sizing in Agile --- Project Management Pathways](https://www.projectmanagementpathways.com/project-management-articles/tshirt-sizing-in-agile-projects)
+
+The buckets chosen should be wide enough
+that scale can be confidently estimated
+after minimal investigation.
+
+## 2025-02-04 13:42
+
+[[fire-alarm-takeoff]]
+
+> [!quote] Art Baldwin 2026-02-04 (pp.)
+> Fire, smoke, and combination fire/smoke dampers
+> may require 120V power, and thus electrical takeoff,
+> or only 24V, in which case mechanical will own the scope.
+> Assuming 120V is a budget-conservative estimating convenience,
+> which is generally considered acceptable
+> in lieu of determining specified requirements,
+> but further investigation may be expected
+> if more than a few per floor are shown.
+
+## 2025-02-04 17:02
+
+While observing takeoff for
+[[electrical-takeoff#Unit Condensing Units|unit condensing units]],
+the project engineer expressed confusion
+at the process of calculating average horizontal length,
+expressing that it was more complicated than they expected
+considering takeoff procedure for similar processes.
+The PE asked why we would not simply use the maximum
+so that we would not risk having too little overall.
+
+Their expectation surprised me,
+since it is intuitive to me
+that there must be some limit to the logic of "covering it"
+since it is always within our power to add contingency,
+and especially because, if anything,
+I feel that our procedures tend towards
+the upper end of reasonable ECI.
+(see [[value-of-information.jpg]])
+
+My response was not well formulated.

advanced-tables.md

@@ -0,0 +1,14 @@
+---
+id:
+aliases: []
+title: Advanced Tables
+tags: []
+---
+# Advanced Tables
+
+| One | Two | Three |
+| ---:| ---:| -----:|
+|   1 |  -2 |       |
+|   1 |   3 |       |
+|  -1 |  -3 |     0 |
+<!-- TBLFM: @>=(@2$3-@3) -->

diagrams.md

@@ -71,7 +71,7 @@ classDiagram
 pie title Estimating Process
     "Estimate Preparation" : 15
     "Takeoff" : 65
-    "Estension & Review" : 10
+    "Extension & Review" : 10
     "Bid Summary" : 10
 ```
 

electrical-takeoff.md

@@ -64,6 +64,13 @@ per [[fire-resistive-wiring-methods-takeoff]].
 
 #### Unit Condensing Units
 
+| Level    | Horizontal | Vertical | Length | Count |
+|:-------- | ----------:| --------:| ------:| -----:|
+| Level 01 |        150 |       40 |    190 |       |
+| Level 02 |        150 |       30 |    180 |       |
+| Level 03 |        150 |       20 |    170 |       |
+| Level 04 |        150 |       10 |    160 |       |
+
 Put homeruns on the `Area` of the dwelling unit.
 Put connections on the `Area` of the CU.
 
@@ -102,3 +109,7 @@ Max 20 disconnects per rack
 
     Takeoff: `COMMON ASSEMBLIES`/`MISC ASSEMBLIES`/`TRASH CHUTE RISER CIRCUIT...`
     * **Length** = average floor to floor height
+
+### Fire/Smoke Dampers
+
+[[fire-alarm-takeoff#Fire/Smoke Dampers (FSD's)]]

fire-alarm-takeoff.md

@@ -191,7 +191,12 @@ _Design Build (alternative method):_
 * 15ft from end of corridor,
 * then every 50ft
 
-## Fire Smoke Dampers (FSD's)
+## Fire/Smoke Dampers (FSD's)
+
+> [!info]
+> Refers to fire, smoke, and combination fire/smoke dampers.
+
+
 
 In [[pdi-building-types#High Rise|high rise construction]],
 usually found on every level with units.