vault backup: 2026-03-02 12:37:43

2026-03-02 12:37:44 -05:00
parent fad3e9cd5c
commit 8afa7c41e5
125 changed files with 428 additions and 330 deletions
@@ -0,0 +1,17 @@
+---
+id: 2026-02-27
+aliases: []
+title: 2026-02-27
+tags:
+  - authorship/original
+  - destiny/permanent
+  - status/draft
+  - type/periodic/daily
+dg-publish: true
+date-created: 2026-02-27T09:44:15-05:00
+weekly: "[[2026-W09]]"
+monthly: "[[2026-02]]"
+quarterly: "[[2026-Q1]]"
+yearly: "[[2026]]"
+---
+# 2026-02-27
@@ -0,0 +1,17 @@
+---
+id: 2026-02-28
+aliases: []
+title: 2026-02-28
+tags:
+  - authorship/original
+  - destiny/permanent
+  - status/draft
+  - type/periodic/daily
+dg-publish: true
+date-created: 2026-02-28T09:44:05-05:00
+weekly: "[[2026-W09]]"
+monthly: "[[2026-02]]"
+quarterly: "[[2026-Q1]]"
+yearly: "[[2026]]"
+---
+# 2026-02-28
@@ -0,0 +1,17 @@
+---
+id: 2026-03-01
+aliases: []
+title: 2026-03-01
+tags:
+  - authorship/original
+  - destiny/permanent
+  - status/draft
+  - type/periodic/daily
+dg-publish: true
+date-created: 2026-03-01T09:43:00-05:00
+weekly: "[[2026-W09]]"
+monthly: "[[2026-03]]"
+quarterly: "[[2026-Q1]]"
+yearly: "[[2026]]"
+---
+# 2026-03-01
@@ -45,8 +45,8 @@ dg-publish: true

 | Hunter A \ Hunter B | Hunter B: Hunt Stag  | Hunter B: Hunt Hare  |
 |:------------------- |:--------------------:|:--------------------:|
-| Hunter A: Hunt Stag | Eat stag \ Eat stag  | Go hungry \ Eat hare |
-| Hunter A: Hunt Hare | Eat hare \ Go hungry | Eat hare \ Eat hare  |
+| **Hunter A: Hunt Stag** | Eat stag \ Eat stag  | Go hungry \ Eat hare |
+| **Hunter A: Hunt Hare** | Eat hare \ Go hungry | Eat hare \ Eat hare  |

 ### Ultimatum Game

@@ -1,7 +1,7 @@
 ---
 id: "{{date:YYYY-[Q]Q}}"
 aliases: []
-title: "{{date:YYYY-[Q]Q}}"
+title: {{date:YYYY-[Q]Q}}
 tags:
  - authorship/original
  - destiny/permanent
@@ -1,7 +1,7 @@
 ---
 id: {{date:YYYY-MM-DDTHH:mm:ssZ}}
 aliases: []
-title: "{{date:YYYY-MM-DD HH:mm:ss}}"
+title: {{date:YYYY-MM-DD HH:mm:ss}}
 tags:
  - authorship/original
  - destiny/permanent
@@ -1,7 +1,7 @@
 ---
 id: 2025-08-26T00:00:00-04:00
 aliases: []
-title: 2025-08-26
+title: 2025-08-26 ??:??:??
 tags:
  - authorship/original
  - destiny/permanent
@@ -29,4 +29,4 @@ p1.y = 6.0d;

 // ??? = Pathfinder.Taxicab(p1, p2)

-```
+```
@@ -1,7 +1,7 @@
 ---
 id: 2025-10-20T00:00:00-05:00
 aliases: []
-title: 2025-10-20
+title: 2025-10-20 ??:??:??
 tags:
  - authorship/original
  - destiny/permanent
@@ -1,7 +1,7 @@
 ---
 id: 2025-10-26T18:36:00-05:00
 aliases: []
-title: 2025-10-26
+title: 2025-10-26 18:36:??
 tags:
  - authorship/original
  - destiny/permanent
@@ -1,5 +1,5 @@
 ---
-id:
+id: 2025-11-01T05:41:00
 aliases: []
 title: 2025-11-01 05:41:??
 tags:
@@ -1,5 +1,5 @@
 ---
-id:
+id: 2025-11-01T07:06:00
 aliases: []
 title: 2025-11-01 07:06:??
 tags:
@@ -1,5 +1,5 @@
 ---
-id:
+id: 2025-11-01T08:25:00
 aliases: []
 title: 2025-11-01 08:25:??
 tags:
@@ -5,8 +5,8 @@ title: 2025-11-04 14:52:05
 tags:
  - authorship/original
  - destiny/permanent
-  - status/complete
  - occupational
+  - status/complete
  - type/minutes
 dg-publish: true
 ---
@@ -1,5 +1,5 @@
 ---
-id:
+id: 2025-11-10T06:53:00
 aliases: []
 title: 2025-11-10 06:53:??
 tags:
@@ -1,12 +1,12 @@
 ---
-id:
+id: 2025-11-10T10:40:00
 aliases: []
-title:
+title: 2025-11-10 10:40:??
 tags:
-  - type/timestamped
-  - topic/estimating
  - occupational
  - original-format/digital-text
+  - topic/estimating
+  - type/timestamped
 dg-publish: true
 ---
 # 2025-11-10 10:40:??
@@ -14,4 +14,4 @@ dg-publish: true
 A significant change from Ace to PDI in my mentality during takeoff
 is that I now tend to expect that (within reason)
 "holes" in takeoff scripts are _intentional omissions_,
-not holes in cost coverage.
+not holes in cost coverage.
@@ -1,11 +1,11 @@
 ---
-id:
+id: 2025-11-10T11:14:00
 aliases: []
-title:
+title: 2025-11-10 11:14:??
 tags:
-  - type/timestamped
  - occupational/takeoff
  - original-format/digital-text
+  - type/timestamped
 dg-publish: true
 ---
 # 2025-11-10 11:14:??
@@ -28,10 +28,10 @@ when I noticed a strange paragraph:
 > > Types NM and NMC cables shall not be permitted as follows:
 > >
 > > 1. In any dwelling or structure not specifically
-> >   permitted in 334.10(1), (2), (3)
+> > permitted in 334.10(1), (2), (3)
 > > 
 > > 2. ==Exposed in dropped or suspended ceilings==
-> >   in other than one- and two-family and multifamily dwellings
+> > in other than one- and two-family and multifamily dwellings

 This analysis of 334.12(A)(2) is flawed.

@@ -54,4 +54,4 @@ It's unclear to me if this a genuine misunderstanding
 or just a [[heuristics|rule of thumb]] to cover the case
 that guestrooms are not interpreted to be dwelling units.
 If it's the latter, I believe it's far too conservative
-to be used whole-cloth on all estimates.
+to be used whole-cloth on all estimates.
@@ -1,11 +1,11 @@
 ---
-id:
+id: 2025-11-10T15:15:00
 aliases: []
-title:
+title: 2025-11-10 15:15:??
 tags:
-  - type/timestamped
-  - topic/construction/electrical
  - original-format/digital-text
+  - topic/construction/electrical
+  - type/timestamped
 dg-publish: true
 ---
 # 2025-11-10 15:15:??
@@ -19,4 +19,4 @@ I'm certain I misuse it frequently.

 It _does not_ include power conductors to
 [[nfpa-70_100_definitions#Utilization Equipment.|utilization equipment]],
-those are [[nfpa-70_100_definitions#Branch Circuit.|branch circuit]] conductors.
+those are [[nfpa-70_100_definitions#Branch Circuit.|branch circuit]] conductors.
@@ -1,12 +1,12 @@
 ---
-id:
+id: 2025-11-10T20:00:00
 aliases: []
-title:
+title: 2025-11-10 20:00:??
 tags:
-  - type/timestamped
-  - topic/estimating
  - occupational
  - original-format/typewritten-print
+  - topic/estimating
+  - type/timestamped
 dg-publish: true
 ---
 # 2025-11-10 20:00:??
@@ -1,11 +1,11 @@
 ---
-id:
+id: 2025-11-11T06:06:00
 aliases: []
-title:
+title: 2025-11-11 06:06:??
 tags:
-  - type/timestamped
-  - topic/estimating
  - original-format/typewritten-print
+  - topic/estimating
+  - type/timestamped
 dg-publish: true
 ---
 # 2025-11-11 06:06:??
@@ -32,4 +32,4 @@ facts of our role:

 In these ways we're actually more like court
 wizards than artists, which is an understandably
-desirable position.
+desirable position.
@@ -1,12 +1,12 @@
 ---
-id:
+id: 2025-11-11T14:41:00
 aliases: []
-title:
+title: 2025-11-11 14:41:??
 tags:
-  - type/timestamped
+  - original-format/digital-text
  - topic/estimating
  - topic/transparency
-  - original-format/digital-text 
+  - type/timestamped
 dg-publish: true
 ---
 # 2025-11-11 14:41:??
@@ -1,10 +1,10 @@
 ---
-id:
+id: 2025-11-13T08:03:00
 aliases: []
-title:
+title: 2025-11-13 08:03:??
 tags:
-  - type/timestamped
  - topic/hobbies/writing
+  - type/timestamped
 dg-publish: true
 ---
 # 2025-11-13 08:03:??
@@ -16,4 +16,4 @@ even though I don't imagine myself approaching them differently.
 I imagine I _would_ speak like I write,
 but that to use the same constructions
 would require a level of forethought
-that I'm not capable of under the pressure of conversation.
+that I'm not capable of under the pressure of conversation.
@@ -1,11 +1,11 @@
 ---
-id:
+id: 2025-11-13T08:19:00
 aliases: []
-title:
+title: 2025-11-13 08:19:??
 tags:
-  - type/timestamped
-  - topic/estimating
  - occupational
+  - topic/estimating
+  - type/timestamped
 dg-publish: true
 ---
 # 2025-11-13 08:19:??
@@ -1,5 +1,5 @@
 ---
-id:
+id: 2025-11-13T00:00:00
 aliases: []
 title: 2025-11-13 ??:??:??
 tags:
@@ -1,10 +1,10 @@
 ---
-id:
+id: 2025-11-13T20:41:00
 aliases: []
-title:
+title: 2025-11-13 20:41:??
 tags:
-  - type/timestamped
  - topic/hobbies/shorthand
+  - type/timestamped
 dg-publish: true
 ---
 # 2025-11-13 20:41:??
@@ -6,9 +6,9 @@ tags:
  - authorship/original
  - destiny/permanent
  - status/draft
-  - topic/meta 
-  - topic/hobbies/music/banjo 
+  - topic/hobbies/music/banjo
  - topic/hobbies/shorthand
+  - topic/meta
  - type/timestamped
 dg-publish: true
 ---
@@ -1,13 +1,13 @@
 ---
 id: 2025-11-20T08:46:00-05:00
 aliases: []
+title: 2025-11-20 08:46:??
 tags:
  - authorship/original
  - destiny/permanent
+  - occupational
  - status/draft
  - type/periodic/daily
-  - occupational
-title: 2025-11-20 08:46:??
 dg-publish: true
 ---
 # 2025-11-20 08:46:??
@@ -1,10 +1,10 @@
 ---
-id:
+id: 2025-12-02T10:40:00
 aliases: []
-title:
+title: 2025-12-02 10:40:??
 tags:
-  - type/timestamped
  - topic/construction/electrical
+  - type/timestamped
 dg-publish: true
 ---
 # 2025-12-02 10:40:??
@@ -18,4 +18,4 @@ dg-publish: true
 > depending on how the field changed in the past.
 > Such a system is called **hysteretic**.

-![[alternating-current#Ferroelectric Hysteresis]]
+![[alternating-current#Ferroelectric Hysteresis]]
@@ -1,7 +1,7 @@
 ---
-id:
+id: 2025-12-02T10:57:00
 aliases: []
-title:
+title: 2025-12-02 10:57:??
 tags:
  - type/timestamped
 dg-publish: true
@@ -25,4 +25,4 @@ sharing some but not all elements.
 * $B \not\subseteq A$:
    "$B$ is not a subset of $A$"
    ($B$ has at least one element not in $A$).
-    Equivalent to $B \setminus A \neq \varnothing$.
+    Equivalent to $B \setminus A \neq \varnothing$.
@@ -1,7 +1,7 @@
 ---
-id:
+id: 2025-12-02T13:20:00
 aliases: []
-title:
+title: 2025-12-02 13:20:??
 tags:
  - type/timestamped
 dg-publish: true
@@ -6,9 +6,9 @@ tags:
  - authorship/original
  - destiny/permanent
  - status/draft
-  - type/timestamped
  - topic/estimating
  - topic/transparency
+  - type/timestamped
 dg-publish: true
 ---
 # 2025-12-03 15:54:22
@@ -5,11 +5,11 @@ title: 2025-12-10 10:45:19
 tags:
  - authorship/original
  - destiny/permanent
-  - status/draft
-  - type/timestamped
  - occupational/takeoff
+  - status/draft
  - topic/ambiguity
  - topic/transparency
+  - type/timestamped
 dg-publish: true
 ---
 # 2025-12-10 10:45:19
@@ -1,7 +1,7 @@
 ---
-id:
+id: 2025-12-16T09:20:52
 aliases: []
-title:
+title: 2025-12-16 09:20:52
 tags:
  - type/timestamped
 dg-publish: true
@@ -10,4 +10,4 @@ dg-publish: true

 [Probability Management](https://www.probabilitymanagement.org/)

-[Handbook of Decision Analysis | Wiley Online Books](https://onlinelibrary.wiley.com/doi/book/10.1002/9781118515853)
+[Handbook of Decision Analysis | Wiley Online Books](https://onlinelibrary.wiley.com/doi/book/10.1002/9781118515853)
@@ -1,7 +1,7 @@
 ---
-id:
+id: 2025-12-16T20:04:00
 aliases: []
-title:
+title: 2025-12-16 20:04:??
 tags:
  - type/timestamped
 dg-publish: true
@@ -1,7 +1,7 @@
 ---
-id:
+id: 2025-12-17T05:39:00
 aliases: []
-title:
+title: 2025-12-17 05:39:??
 tags:
  - type/timestamped
 dg-publish: true
@@ -42,4 +42,4 @@ to the conceivably far more broad

 ### Ambiguity

-New Note: [[ambiguity]]
+New Note: [[ambiguity]]
@@ -1,10 +1,10 @@
 ---
-id:
+id: 2025-12-17T12:32:00
 aliases: []
-title:
+title: 2025-12-17 12:32:??
 tags:
-  - type/timestamped
  - topic/ambiguity
+  - type/timestamped
 dg-publish: true
 ---
 # 2025-12-17 12:32:??
@@ -1,11 +1,11 @@
 ---
-id:
+id: 2025-12-18T08:32:18
 aliases: []
-title:
+title: 2025-12-18 08:32:18
 tags:
  - type/timestamped
 dg-publish: true
 ---
 # 2025-12-18 08:32:18

-[[uncertainty-in-construction-estimating]]
+[[uncertainty-in-construction-estimating]]
@@ -1,10 +1,10 @@
 ---
-id:
+id: 2025-12-18T10:38:00
 aliases: []
-title:
+title: 2025-12-18 10:38:??
 tags:
-  - type/timestamped
  - topic/meta
+  - type/timestamped
 dg-publish: true
 ---
 # 2025-12-18 10:38:??
@@ -15,4 +15,4 @@ rather than separate fleeting notes
 is superior.

 The unfortunate reality is I'll never look at most of them again,
-so better that they don't crowd out my main notes.
+so better that they don't crowd out my main notes.
@@ -1,7 +1,7 @@
 ---
-id:
+id: 2025-12-18T14:18:00
 aliases: []
-title:
+title: 2025-12-18 14:18:??
 tags:
  - type/timestamped
 dg-publish: true
@@ -31,4 +31,4 @@ whether organization historicals are freely available
 or must be questioned like project details.

 The most interesting part of this problem is choosing when to stop,
-since it requires one to estimate their certainty of their estimate.
+since it requires one to estimate their certainty of their estimate.
@@ -1,7 +1,7 @@
 ---
-id:
+id: 2025-12-18T15:22:00
 aliases: []
-title:
+title: 2025-12-18 15:22:??
 tags:
  - type/timestamped
 dg-publish: true
@@ -11,4 +11,4 @@ dg-publish: true
 PDI has moved up the schedule to transition to Accubid Anywhere
 and will be signing a contract with Trimble in late January.

-[Drawer AI | Automated Electrical Takeoff & Estimating](https://drawer.ai/)
+[Drawer AI | Automated Electrical Takeoff & Estimating](https://drawer.ai/)
@@ -1,7 +1,7 @@
 ---
-id:
+id: 2025-12-18T15:30:00
 aliases: []
-title:
+title: 2025-12-18 15:30:??
 tags:
  - type/timestamped
 dg-publish: true
@@ -1,10 +1,10 @@
 ---
-id:
+id: 2025-12-19T10:44:00
 aliases: []
-title:
+title: 2025-12-19 10:44:??
 tags:
-  - type/timestamped
  - occupational/takeoff
+  - type/timestamped
 dg-publish: true
 ---
 # 2025-12-19 10:44:??
@@ -1,10 +1,10 @@
 ---
-id:
+id: 2025-12-19T10:44:00
 aliases: []
-title:
+title: 2025-12-19 10:44:??
 tags:
-  - type/timestamped
  - occupational/takeoff
+  - type/timestamped
 dg-publish: true
 ---
 # 2025-12-19 10:44:??
@@ -1,7 +1,7 @@
 ---
-id:
+id: 2026-01-02T10:10:18
 aliases: []
-title:
+title: 2026-01-02 10:10:18
 tags:
  - type/timestamped
 dg-publish: true
@@ -14,4 +14,4 @@ dg-publish: true

 * [ ] [[electrical-takeoff|Electrical]]
 * [x] [[telecom-takeoff#Backbone Riser|Telecom Backbone]]
-* [x] [[distributed-antenna-systems-takeoff|DAS]]
+* [x] [[distributed-antenna-systems-takeoff|DAS]]
@@ -1,7 +1,7 @@
 ---
-id:
+id: 2026-01-02T19:21:00
 aliases: []
-title:
+title: 2026-01-02 19:21:??
 tags:
  - type/timestamped
 dg-publish: true
@@ -1,7 +1,7 @@
 ---
-id:
+id: 2026-01-06T07:47:00
 aliases: []
-title:
+title: 2026-01-06 07:47:??
 tags:
  - type/timestamped
 dg-publish: true
@@ -17,4 +17,4 @@ dg-publish: true
    others appreciate it

 3. Person feels that they are doing a service
-    by not engaging in said toxic behavior
+    by not engaging in said toxic behavior
@@ -1,7 +1,7 @@
 ---
-id:
+id: 2026-01-06T10:00:00
 aliases: []
-title:
+title: 2026-01-06 10:00:??
 tags:
  - type/timestamped
 dg-publish: true
@@ -89,4 +89,4 @@ If I had a job where some were significantly more full than others
 I _might_ do something similar,
 but I'd probably name them
 "... 1-Section, ~25% Fill"/"... 1-Section, ~75% Fill" instead.
-But that's a lot of mental overhead.
+But that's a lot of mental overhead.
@@ -1,7 +1,7 @@
 ---
-id:
+id: 2026-01-06T10:57:00
 aliases: []
-title:
+title: 2026-01-06 10:57:??
 tags:
  - type/timestamped
 dg-publish: true
@@ -1,7 +1,7 @@
 ---
-id:
+id: 2026-01-07T06:41:00
 aliases: []
-title:
+title: 2026-01-07 06:41:??
 tags:
  - type/timestamped
 dg-publish: true
@@ -23,4 +23,4 @@ dg-publish: true
 > (though we obey the orders of some prosaic person every day) our own masters,
 > when the truth is that our masters are sleeping.
 > One wakes within us and we are ridden like beasts,
-> though the rider is but some hitherto unguessed part of ourselves.
+> though the rider is but some hitherto unguessed part of ourselves.
@@ -1,7 +1,7 @@
 ---
-id:
+id: 2026-01-07T10:03:00
 aliases: []
-title:
+title: 2026-01-07 10:03:??
 tags:
  - type/timestamped
 dg-publish: true
@@ -9,4 +9,4 @@ dg-publish: true
 # 2026-01-07 10:03:??

 At Ace, "residential" always meant single-family/duplex construction,
-but I think now we were the outliers.
+but I think now we were the outliers.
@@ -1,7 +1,7 @@
 ---
-id:
+id: 2026-01-07T10:05:00
 aliases: []
-title:
+title: 2026-01-07 10:05:??
 tags:
  - type/timestamped
 dg-publish: true
@@ -20,4 +20,4 @@ in that an estimator may use the area classifications of the design
 or according to their own understanding of each term.
 For lack of a better example,
 whether a "101 - KITCHEN", without provisions for cooking,
-would be broken down under "Kitchen".
+would be broken down under "Kitchen".
@@ -1,8 +1,11 @@
 ---
-id:
+id: 2026-01-07T10:42:00
 aliases: []
-title:
+title: 2026-01-07 10:42:??
 tags:
+  - authorship/original
+  - occupational
+  - topic/estimating
  - type/timestamped
 dg-publish: true
 ---
@@ -45,4 +48,4 @@ I suspect is even less.
 It's curious to me that the possibility of scope revisions
 doesn't seem to be at the front of every estimator's mind
 when doing takeoff or considering process changes,
-like it was for my mentors and peers at Ace.
+like it was for my mentors and peers at Ace.
@@ -1,12 +1,12 @@
 ---
-id:
+id: 2026-01-07T12:13:00
 aliases: []
-title:
+title: 2026-01-07 12:13:??
 tags:
-  - type/timestamped
  - occupational
  - topic/estimating
  - topic/organization
+  - type/timestamped
 dg-publish: true
 ---
 # 2026-01-07 12:13:??
@@ -34,4 +34,4 @@ because otherwise it would be necessary to have double the assemblies,
 or to expect estimators to substitute each size of wire
 everywhere bare was necessary.

-See [[realism-vs-instrumentalism]].
+See [[realism-vs-instrumentalism]].
@@ -1,20 +1,21 @@
 ---
-id:
+id: 2026-01-07T16:03:00
 aliases: []
-title:
+title: 2026-01-07 16:03:??
 tags:
-  - type/timestamped
  - occupational
  - topic/estimating
  - topic/organization
+  - type/timestamped
 dg-publish: true
 ---
 # 2026-01-07 16:03:??

 There is a palpable animosity for [[pdi-estimating#Bid Estimating|Bid]]
 in [[pdi-estimating#Construction Estimating (ConEst)|ConEst]],
-stemming---I believe---from an lack of buy-in on Bid's part.
-Their lack is easily explained by their [[estimating-culture#Incentives|incentive structure]]:
+stemming (I believe) from an lack of buy-in on Bid's part.
+
+The lack is easily explained by their [[estimating-culture#Incentives|incentive structure]]:
 Since throughput is systematically prioritized over accuracy,
 ConEst has a strictly antagonistic role
 because it slows down the bid process.
@@ -1,23 +1,25 @@
 ---
-id:
+id: 2026-01-08T13:33:34
 aliases: []
-title:
+title: 2026-01-08 13:33:34
 tags:
  - type/timestamped
 dg-publish: true
 ---
 # 2026-01-08 13:33:34

-### 2100 Crystal Drive Takeoff Review
+## 2100 Crystal Drive Takeoff Review

-#### Generators
+[[2100-crystal-drive]]
+
+### Generators

 > [!failure]
 > Generators were erroneously broken down in switchgear.

 [[switchgear-takeoff#Generator|Generator]]

-#### Switchgear
+### Switchgear

 Switchgear cost comp
 "\\EgnyteDrive\Shared\Estimating\11 Bid Estimating Spreadsheets\Switchgear Pricing Tool Version 2 (2.02.2024) (Template) - Copy.xls"
@@ -26,7 +28,7 @@ Includes
 * submetering
 * coordination study

-#### Composite Cleanup
+### Composite Cleanup

 1 day per week

@@ -37,13 +39,13 @@ $$
 > It occurs to me I don't know all the rules of our calendar
 > [Gregorian calendar - Wikipedia](https://en.wikipedia.org/wiki/Gregorian_calendar)

-#### Temp Power
+### Temp Power

 $10,000 per [[heavy-equipment#Swing Stage Scaffolding|swing stage]]

 [[temp-power-takeoff]]

-#### Unit Typicals
+### Unit Typicals

 I asked Joel about using unit typicals as described in
 [[2025-12-19_10-44-01]].
@@ -1,24 +1,28 @@
 ---
-id:
+id: 2026-01-09T10:00:03
 aliases: []
-title:
+title: 2026-01-09 10:00:03
 tags:
  - type/timestamped
 dg-publish: true
 ---
 # 2026-01-09 10:00:03

-### 2100 Crystal Drive
+## 2100 Crystal Drive Closeout
+
+[[2100-crystal-drive]]
+
+### Extension

 `#600 ? WHITE ?` had incorrect sort codes.

-#### Lighting Control
+### Lighting Control

 I took off lighting per plans (E510)
 in spite of proposal stating "local control".
 Will have to be changed.

-#### Labor Factor
+### Labor Factor

 Fire Alarm
 Switchgear
@@ -29,7 +33,7 @@ Amenity
 Retail
 Units

-#### Fixtures
+### Fixtures

 > [!failure]
 > Several fixtures were erroneously based on NM cable.
@@ -38,16 +42,16 @@ I built some fixtures with \#12/3 in areas with emergency lighting
 to be an unswitched hot.
 Joel is having me change them to \#12/2.

-#### Units
+### Units

 > [!failure]
 > One unit type typical was missing `Area` quantities.
 > Another had no takeoff.

-#### Labor Plan
+### Labor Plan

 $$
 \mathbb{E}\left[\frac{\text{Hours Per Unit}}{\text{Openings Per Unit}}\right] \approx .75~\text{Hours Per Opening}
 $$

-High Rise .110--.120 hr/sqft
+High Rise .110--.120 hr/sqft
@@ -1,7 +1,7 @@
 ---
-id:
+id: 2026-01-09T12:00:00
 aliases: []
-title:
+title: 2026-01-09 12:00:??
 tags:
  - type/timestamped
 dg-publish: true
@@ -24,4 +24,4 @@ $$
 $$
 \frac{52.1775~\text{Weeks Per Year}}{12~\text{Months Per Year}}
 = 4.348125~\text{Weeks Per Month}
-$$
+$$
@@ -1,7 +1,7 @@
 ---
-id:
+id: 2026-01-09T14:45:00
 aliases: []
-title:
+title: 2026-01-09 14:45:??
 tags:
  - type/timestamped
 dg-publish: true
@@ -20,4 +20,4 @@ $t>0$ is time until the final payment.
 > ![250](https://upload.wikimedia.org/wikipedia/commons/thumb/8/89/Log-normal-pdfs.png/960px-Log-normal-pdfs.png)
 >
 > Figure: lognormal distributions with the same [location](https://en.wikipedia.org/wiki/Location_parameter)
-> varied by [scale](https://en.wikipedia.org/wiki/Scale_parameter).
+> varied by [scale](https://en.wikipedia.org/wiki/Scale_parameter).
@@ -1,7 +1,7 @@
 ---
-id:
+id: 2026-01-09T16:28:00
 aliases: []
-title:
+title: 2026-01-09 16:28:??
 tags:
  - type/timestamped
 dg-publish: true
@@ -11,7 +11,7 @@ dg-publish: true
 ---
 # 2026-01-10 08:42:??

-I've been writing a C# library based on the specifications of [[music-theory-as-code]],
+I've been writing a [[csharp|C#]] library based on the specifications of [[music-theory-as-code]],
 but the problem of parsing overwhelms me whenever I think about implementation.

 I'd like to try to get [ANTLR](https://github.com/antlr/antlr4) working,
@@ -1,7 +1,7 @@
 ---
-id:
+id: 2026-01-11T09:00:00
 aliases: []
-title:
+title: 2026-01-11 09:00:??
 tags:
  - type/timestamped
 dg-publish: true
@@ -12,4 +12,4 @@ dg-publish: true

 [[bid-price-modeling]]

-[[decrease-in-sigma]]
+[[decrease-in-sigma]]
@@ -1,7 +1,7 @@
 ---
-id:
+id: 2026-01-11T11:00:00
 aliases: []
-title:
+title: 2026-01-11 11:00:??
 tags:
  - type/timestamped
 dg-publish: true
@@ -1,9 +1,10 @@
 ---
 id: 2026-01-12T10:00:00-05:00
+aliases: []
 title: 2026-01-12 10:00:??
 tags:
-  - type/timestamped
  - occupational
+  - type/timestamped
 dg-publish: true
 ---
 # 2026-01-12 10:00:??
@@ -12,4 +13,4 @@ dg-publish: true

 For Executed Contract Revisions, Bid GP% must be maintained.
 In this case a negative variance was added to the buyout budget
-in order to compensate for an increase in permit fee coverage.
+in order to compensate for an increase in permit fee coverage.
@@ -1,9 +1,10 @@
 ---
 id: 2026-01-12T10:42:30-05:00
+aliases: []
 title: 2026-01-12 10:42:30
 tags:
-  - type/timestamped
  - occupational
+  - type/timestamped
 dg-publish: true
 ---
 # 2026-01-12 10:42:30
@@ -16,4 +17,4 @@ Drawings show 2 separate duplex receptacles for dishwasher and disposal
 Takeoff used `DW & DISPOSAL DUAL CIR - ...`,
 which includes only one receptacle.

-According to Joel this takeoff is correct for the scenario.
+According to Joel this takeoff is correct for the scenario.
@@ -1,15 +1,16 @@
 ---
 id: 2026-01-12T12:23:00-05:00
+aliases: []
 title: 2026-01-12 12:23:??
 tags:
-  - type/timestamped
  - occupational
+  - type/timestamped
 dg-publish: true
 ---
 # 2026-01-12 12:23:??

 Travelling with Brian Smarslok and Joel Jansen on [[2026-01-15]]
-to visit [[#Woodbury Heights|an awarded project]] in New Jersey.
+to visit [[woodbury-heights|an awarded project]] in New Jersey.
 Flying from TPA to PHL, departure @ 7:00AM.
 We'll be meeting with the developer, [Greystar](https://www.greystar.com/).

@@ -63,4 +64,4 @@ and more generally if he has a strategy for figuring out,
 between BPM, The Hub, and however many other places we can look.

 I doubt very seriously that mismanagement
-can be blamed for any significant portion of variance that extreme.
+can be blamed for any significant portion of variance that extreme.
@@ -1,9 +1,10 @@
 ---
 id: 2026-01-12T13:02:00-05:00
+aliases: []
 title: 2026-01-12 13:02:??
 tags:
-  - type/timestamped
  - topic/construction
+  - type/timestamped
 dg-publish: true
 ---
 # 2026-01-12 13:02:??
@@ -1,8 +1,17 @@
+---
+id: 2026-01-12T13:02:00
+aliases: []
+title: 2026-01-12 13:02:??
+tags:
+  - authorship/original
+  - destiny/permanent
+  - occupational
+  - type/timestamped
+---
 # 2026-01-12 13:02:??

-#occupational
-
-Joel attributes the [[#GP Variance|apparent variance]] to
+Joel attributes the [[#GP Variance|apparent variance]]
+of [[woodbury-heights]] to
 1. missed Polaris lugs for feeders for one building,
 2. insufficient budget for equipment rental, and
 3. upfront costs already paid (construction is 50% complete).
@@ -5,9 +5,9 @@ title: 2026-01-13 11:28:14
 tags:
  - authorship/original
  - destiny/permanent
+  - occupational
  - status/draft
  - type/timestamped
-  - occupational
 dg-publish: true
 ---
 # 2026-01-13 11:28:14
@@ -29,7 +29,7 @@ dg-publish: true

 #### Lighting Control

-Follow up to [[2026-01-09#Lighting Control]]
+Follow up to [[2026-01-09_10-00-03#Lighting Control]]

 Josh stated my takeoff was correct per drawings,
 but that concessions would need to be made for the scope
@@ -5,17 +5,17 @@ title: 2026-01-14 13:27:20
 tags:
  - authorship/original
  - destiny/permanent
+  - occupational
  - status/draft
  - type/timestamped
-  - occupational
 dg-publish: true
 ---
 # 2026-01-14 13:27:20

-Follow-up to [[2026-01-13#Lighting Control]]
+Follow-up to [[2026-01-13_11-28-14#Lighting Control]]

 > [!quote] Conversation between Joel Jansen and Christian Pereiro regarding lighting control for [[2100-crystal-drive]]:
-> 
+>
 > **Joel:** "It was sold as local."
-> 
+>
 > **Christian:** "Yeah, but you can't do that."
@@ -1,13 +1,13 @@
 ---
-id:
+id: 2026-01-15T08:11:10
 aliases: []
-title:
+title: 2026-01-15 08:11:10
 tags:
  - type/timestamped
 dg-publish: true
 ---
 # 2026-01-15 08:11:10

-Follow-up to [[2026-01-12_12-23-??|2026-01-12 12:23]]
+Follow-up to [[2026-01-12_12-23-00]]

-Left Apartment at 05:30, at terminal around 06:10.
+Left Apartment at 05:30, at terminal around 06:10.
@@ -1,7 +1,7 @@
 ---
-id:
+id: 2026-01-15T08:15:00
 aliases: []
-title:
+title: 2026-01-15 08:15:??
 tags:
  - type/timestamped
 dg-publish: true
@@ -1,5 +1,6 @@
 ---
 id: 2026-01-19T11:57:39-05:00
+aliases: []
 title: 2026-01-19 11:57:39
 tags:
  - type/timestamped
@@ -16,4 +17,4 @@ for the sort of formatting I've been doing recently.

 [[semantic-line-breaks]]

-[[2025-10-26_18-36-?? --- Sunday evening]]
+[[2025-10-26_18-36-00]]
@@ -1,18 +1,19 @@
 ---
 id: 2026-01-19T12:32:00-05:00
+aliases: []
 title: 2026-01-19 12:32:??
 tags:
-  - type/timestamped
  - topic/construction
  - topic/estimating
+  - type/timestamped
 dg-publish: true
 ---
 # 2026-01-19 12:32:??

 Real example of [[location-vs-scope]]:

-450-460 James Robertson Parkway Phase II (fka James Roberston Pkwy Mixed Use Development)
+[[450--460-james-robertson-parkway|450-460 James Robertson Parkway Phase II (fka James Roberston Pkwy Mixed Use Development)]]

 Project is two buildings: Residential and Hotel,
 entirely separate physically and electrically.
-Generators for both are located on a lower roof of Residential.
+Generators for both are located on a lower roof of Residential.
@@ -1,5 +1,6 @@
 ---
 id: 2026-01-19T18:13:00-05:00
+aliases: []
 title: 2026-01-19 18:13:??
 tags:
  - type/timestamped
@@ -16,9 +17,9 @@ A programmable thermostat is at the top of my todo list,
 for energy efficiency, but mostly habit enforcement.
 I can not sleep without blankets, and I can not sleep hot.
 Turning on the lights as an alarm is usually effective,
-but when it's cold I find it hard not cover my face and go back to sleep.
+but when it's cold I find it hard not to cover my face and go back to sleep.

-In general the ability to make one's house unfit for relaxation
+In general, the ability to make one's house unfit for relaxation
 at certain hours of the week is very powerful.

 Google's Nest is the stereotypical smart thermostat,
@@ -1,5 +1,6 @@
 ---
 id: 2026-01-20T09:09:12-05:00
+aliases: []
 title: 2026-01-20 09:09:12
 tags:
  - type/timestamped
@@ -12,4 +13,4 @@ Stumbled upon this line while waiting on my computer to restart.
 > [!quote] [[hubbard_2020_failure#The Measurement Inversion]]
 > Unless we estimate the value of information,
 > we may go down the deep rabbit hole of adding more and more detail to a model
-> and trying to gather data on less relevant issues.
+> and trying to gather data on less relevant issues.
@@ -1,5 +1,6 @@
 ---
 id: 2026-01-20T10:10:00-05:00
+aliases: []
 title: 2026-01-20 10:10:??
 tags:
  - type/timestamped
@@ -14,4 +15,4 @@ I added a [[small-tasks|task]] for it.

 I'm now certain that common estimating calculators
 (e.g. voltage drop)
-could be easily replaced with documents like this one.
+could be easily replaced with documents like this one.
@@ -1,5 +1,6 @@
 ---
 id: 2026-01-20T14:25:00-05:00
+aliases: []
 title: 2026-01-20 14:25:??
 tags:
  - type/timestamped
@@ -1,9 +1,10 @@
 ---
 id: 2026-01-22T09:55:42-05:00
+aliases: []
 title: 2026-01-22 09:55:42
 tags:
-  - type/timestamped
  - occupational
+  - type/timestamped
 dg-publish: true
 ---
 # 2026-01-22 09:55:42
@@ -16,4 +17,4 @@ I knew this was understood to be prohibited,
 but could not have provided a code reference.

 [[nfpa-70_110_requirements#110.26(D) Illumination.|110.26(D)]]
-is the relevant section.
+is the relevant section.
@@ -1,9 +1,10 @@
 ---
 id: 2026-01-22T11:58:00-05:00
+aliases: []
 title: 2026-01-22 11:58:??
 tags:
-  - type/timestamped
  - occupational
+  - type/timestamped
 dg-publish: true
 ---
 # 2026-01-22 11:58:??
@@ -20,4 +21,4 @@ Effective date: [[2026-01-21]]
 * [x] Loan approval due by [[2026-02-11]]
 * [ ] Title commitment due by [[2026-02-27]]

-Closing: [[2026-03-04]]
+Closing: [[2026-03-04]]
@@ -1,9 +1,10 @@
 ---
 id: 2026-01-22T14:56:00-05:00
+aliases: []
 title: 2026-01-22 14:56:??
 tags:
-  - type/timestamped
  - topic/estimating
+  - type/timestamped
 dg-publish: true
 ---
 # 2026-01-22 14:56:??
@@ -1,5 +1,6 @@
 ---
 id: 2026-01-23T08:18:53-05:00
+aliases: []
 title: 2026-01-23 08:18:53
 tags:
  - type/timestamped
@@ -18,4 +19,4 @@ As it turns out, the potential validity of slippery slope arguments is well stud
 [Fuzzy logic](https://en.wikipedia.org/wiki/Fuzzy_logic)

 Strictly speaking, a slippery slope argument is only fallacious
-if it is not _necessarily_ true that one event must follow another.
+if it is not _necessarily_ true that one event must follow another.
@@ -1,5 +1,6 @@
 ---
 id: 2026-01-23T12:34:00-05:00
+aliases: []
 title: 2026-01-23 12:34:??
 tags:
  - type/timestamped
@@ -15,4 +16,4 @@ Migrated several notes from Google's Keep

 [[my-resoluute-banjo]]

-[[pats-browning-a5]]
+[[pats-browning-a5]]
@@ -1,9 +1,10 @@
 ---
 id: 2026-01-25T18:46:00-05:00
+aliases: []
 title: 2026-01-25 18:46:??
 tags:
-  - type/timestamped
  - topic/finance
+  - type/timestamped
 dg-publish: true
 ---
 # 2026-01-25 18:46:??
@@ -55,4 +56,4 @@ $$

 $$
 \text{APR} = \frac{\frac{\text{Interest} + \text{Fees}}{\text{Principle}}}{\text{Term Years}}
-$$
+$$
@@ -1,5 +1,6 @@
 ---
 id: 2026-01-25T21:02:00-05:00
+aliases: []
 title: 2026-01-25 21:02:??
 tags:
  - type/timestamped
@@ -20,7 +21,7 @@ without acknowledging that _Fermi_ supplied the decomposition.
 Hubbard also references [[macgregor_1994_judgemental-decomposition]]
 which is a similar case.
 Neither of these examples suggest that decomposition is a magic bullet,
-or even that a layman's decomposition wouldn't be worse than nothing.
+_or even that a layman's decomposition wouldn't be worse than nothing._
 Despite this, Hubbard ends the section without qualifier:
 "Clearly, decomposition helps estimates."

@@ -28,4 +29,4 @@ This section comes only pages after
 [[hubbard_2020_failure#The Measurement Inversion]]
 in which Hubbard warns against seeking detail for the sake of it.

-See also [[the-failure-of-risk-management#_Exsupero Ursus_]].
+See also [[the-failure-of-risk-management#_Exsupero Ursus_]].
@@ -1,5 +1,6 @@
 ---
 id: 2026-01-25T22:59:00-05:00
+aliases: []
 title: 2026-01-25 22:59:??
 tags:
  - type/timestamped
@@ -17,7 +18,7 @@ when the work was done by the researchers,
 especially when some of their decompositions really suck.

 > ##### Circumference of 50¢ coin
-> 
+>
 > * Diameter in inches of a 50¢ coin
 > * Number of pieces of string the length of the diameter needed to wrap around circumference

@@ -31,7 +32,7 @@ that's a harder problem than it was before.
 > * Number of bushels of wheat consumed per person per year
 > * Proportion of wheat wasted per year

-I might have included how much a bushel is,[^1]
+I might have included _how much a bushel is_,[^1]
 there's an order of magnitude right there.

 [^1]: $1~\text{US bushel} \equiv 9\frac{3571}{11550}~\text{US Gallons} \approx 9.3~\text{US Gallons}$
@@ -6,15 +6,15 @@ tags:
  - authorship/original
  - destiny/permanent
  - status/draft
+  - topic/hobbies/reading
  - type/timestamped
-  - topic/hobbies/reading 
 dg-publish: true
 ---
 # 2026-01-27 17:31:??

 ### BLAME! Coelacanth

-Follow-up to [[2026-01-26#BLAME! Coelacanth]]
+Follow-up to [[2026-01-26_06-48-00#BLAME! Coelacanth]]

 BLAME! Master Edition, Volume 5

@@ -1,9 +1,10 @@
 ---
 id: 2026-01-28T09:51:08-05:00
+aliases: []
 title: 2026-01-28 09:51:08
 tags:
-  - type/timestamped
  - occupational
+  - type/timestamped
 dg-publish: true
 ---
 # 2026-01-28 09:51:08
@@ -29,4 +30,4 @@ as to be useless to an experienced estimator.

 Voluntary commitment to responsibility.
 An estimator adding their initials
-knows they are expected to be familiar with the scope.
+knows they are expected to be familiar with the scope.
@@ -1,9 +1,10 @@
 ---
 id: 2026-01-28T10:02:00-05:00
+aliases: []
 title: 2026-01-28 10:02:??
 tags:
-  - type/timestamped
  - topic/meta
+  - type/timestamped
 dg-publish: true
 ---
 # 2026-01-28 10:02:??
@@ -1,9 +1,10 @@
 ---
 id: 2026-01-29T10:07:37-05:00
+aliases: []
 title: 2026-01-29 10:07:37
 tags:
-  - type/timestamped
  - topic/estimating
+  - type/timestamped
 dg-publish: true
 ---
 # 2026-01-29 10:07:37
@@ -23,4 +24,4 @@ which an estimator without field experience (which the senior has)
 would be unlikely to be able to provide.
 Their dismissal of legitimate _instrumental_ complaints
 (misplaced effort, and deviation from more widely accepted standards)
-speaks to a fundamental misunderstanding of the purpose of estimating.
+speaks to a fundamental misunderstanding of the purpose of estimating.
@@ -1,9 +1,10 @@
 ---
 id: 2026-01-29T17:57:00-05:00
+aliases: []
 title: 2026-01-29 17:57:??
 tags:
-  - type/timestamped
  - topic/finance
+  - type/timestamped
 dg-publish: true
 ---
 # 2026-01-29 17:57:??
@@ -1,9 +1,10 @@
 ---
 id: 2026-01-30T08:44:29-05:00
+aliases: []
 title: 2026-01-30 08:44:29
 tags:
-  - type/timestamped
  - topic/meta
+  - type/timestamped
 dg-publish: true
 ---
 # 2026-01-30 08:44:29
@@ -1,9 +1,10 @@
 ---
 id: 2026-01-30T09:06:00-05:00
+aliases: []
 title: 2026-01-30 09:06:??
 tags:
-  - type/timestamped
  - topic/meta
+  - type/timestamped
 dg-publish: true
 ---
 # 2026-01-30 09:06:??
@@ -11,4 +12,4 @@ dg-publish: true
 I tried the Smart Connections community plugin.
 I can't imagine who it could be useful for.
 It seems to just identify large blocks of similar content,
-which means that every daily note is connected to every other.
+which means that every daily note is connected to every other.
@@ -5,6 +5,7 @@ title: 2026-01-31 17:49:00
 tags:
  - authorship/other
  - destiny/permanent
+  - exclude-from-word-count
  - status/draft
  - type/timestamped
 daily: "[[2026-01-31]]"
@@ -6,10 +6,10 @@ tags:
  - authorship/original
  - destiny/permanent
  - status/draft
-  - type/timestamped
  - topic/meta
-dg-publish: true
+  - type/timestamped
 daily: "[[2026-02-02]]"
+dg-publish: true
 ---
 # 2026-02-02 06:50:00

@@ -5,11 +5,11 @@ title: 2026-02-02 12:18:00
 tags:
  - authorship/original
  - destiny/permanent
+  - occupational/takeoff
  - status/draft
  - type/timestamped
-  - occupational/takeoff
-dg-publish: true
 daily: "[[2026-02-02]]"
+dg-publish: true
 ---
 # 2026-02-02 12:18:00

@@ -5,11 +5,11 @@ title: 2026-02-03 08:34:00
 tags:
  - authorship/original
  - destiny/permanent
+  - occupational
  - status/draft
  - type/timestamped
-  - occupational
-dg-publish: true
 daily: "[[2026-02-03]]"
+dg-publish: true
 ---
 # 2026-02-03 08:34:00

@@ -6,10 +6,10 @@ tags:
  - authorship/original
  - destiny/permanent
  - status/draft
-  - type/timestamped
  - topic/estimating
-dg-publish: true
+  - type/timestamped
 daily: "[[2026-02-03]]"
+dg-publish: true
 ---
 # 2026-02-03 15:04:00

@@ -5,11 +5,11 @@ title: 2026-02-03 16:17:00
 tags:
  - authorship/original
  - destiny/permanent
+  - occupational
  - status/draft
  - type/timestamped
-  - occupational
-dg-publish: true
 daily: "[[2026-02-03]]"
+dg-publish: true
 ---
 # 2026-02-03 16:17:00

@@ -5,11 +5,11 @@ title: 2026-02-04 08:07:00
 tags:
  - authorship/original
  - destiny/permanent
+  - occupational
  - status/draft
  - type/timestamped
-  - occupational
-dg-publish: true
 daily: "[[2026-02-04]]"
+dg-publish: true
 ---
 # 2026-02-04 08:07:00

@@ -6,10 +6,10 @@ tags:
  - authorship/original
  - destiny/permanent
  - status/draft
-  - type/timestamped
  - topic/ergonomics/organizational
-dg-publish: true
+  - type/timestamped
 daily: "[[2026-02-04]]"
+dg-publish: true
 ---
 # 2026-02-04 09:00:00

@@ -28,23 +28,23 @@ representing project scale buckets.
 > [!example] [T-Shirt Sizing in Agile --- Project Management Pathways](https://www.projectmanagementpathways.com/project-management-articles/tshirt-sizing-in-agile-projects)
 > * **XS (1-2 days):** Simple UI changes or minor bug fixes
 > 
->     Example: "Update button color on checkout page"
+> Example: "Update button color on checkout page"
 >
 > * **S (2-3 days):** Feature enhancements with minimal complexity
 > 
->     Example: "Add product sorting by price"
+> Example: "Add product sorting by price"
 >
 > * **M (5-7 days):** Features requiring moderate integration
 > 
->     Example: "Implement basic search filters"
+> Example: "Implement basic search filters"
 >
 > * **L (8-10 days):** Complex features affecting multiple components
 > 
->     Example: "Create shopping cart functionality"
+> Example: "Create shopping cart functionality"
 >
 > * **XL (2+ weeks):** Major features requiring breaking down
 > 
->     Example: "Implement payment gateway integration"
+> Example: "Implement payment gateway integration"

 The buckets chosen should be wide enough
 that scale can be confidently estimated
@@ -5,11 +5,11 @@ title: 2026-02-04 13:42:00
 tags:
  - authorship/original
  - destiny/permanent
+  - occupational/takeoff
  - status/draft
  - type/timestamped
-  - occupational/takeoff
-dg-publish: true
 daily: "[[2026-02-04]]"
+dg-publish: true
 ---
 # 2026-02-04 13:42:00

--- a/Show More
+++ b/Show More