From 717e5db35c0ecec080c0da8d5d6a85719bb363c9 Mon Sep 17 00:00:00 2001
From: Zane Meyers <zanemeyers@gmail.com>
Date: Fri, 15 May 2026 00:04:10 -0400
Subject: [PATCH] vault backup: 2026-05-15 00:04:10

---
 .obsidian/app.json                 |  2 +-
 periodic/daily/2026-05-15.md       | 10 ++++++++++
 timestamped/2026-05-14_17-57-07.md | 13 ++++++++-----
 3 files changed, 19 insertions(+), 6 deletions(-)
 create mode 100644 periodic/daily/2026-05-15.md

diff --git a/.obsidian/app.json b/.obsidian/app.json
index 6f7cfce..9e3dc02 100644
--- a/.obsidian/app.json
+++ b/.obsidian/app.json
@@ -1,6 +1,6 @@
 {
   "livePreview": false,
-  "readableLineLength": false,
+  "readableLineLength": true,
   "strictLineBreaks": true,
   "propertiesInDocument": "visible",
   "showLineNumber": true,
diff --git a/periodic/daily/2026-05-15.md b/periodic/daily/2026-05-15.md
new file mode 100644
index 0000000..5c058b1
--- /dev/null
+++ b/periodic/daily/2026-05-15.md
@@ -0,0 +1,10 @@
+---
+id: 2026-05-15
+title: 2026-05-15
+tags: []
+weekly: "[[2026w20]]"
+monthly: "[[2026-05]]"
+quarterly: "[[2026q2]]"
+previous: "[[2026-05-14]]"
+---
+# 2026-05-15
diff --git a/timestamped/2026-05-14_17-57-07.md b/timestamped/2026-05-14_17-57-07.md
index 963556b..e8af7b8 100644
--- a/timestamped/2026-05-14_17-57-07.md
+++ b/timestamped/2026-05-14_17-57-07.md
@@ -7,7 +7,8 @@ daily: "[[2026-05-14]]"
 # 2026-05-14 17:57:07
 
 In my years of using [[accubid|Accubid]] nearly every work day
-I've always longed for good analogies for using the wrong [[tools|tool]] for the job.
+I've always longed for good analogies
+for using the wrong [[tools|tool]] for the job.
 I found one that could almost be said to be in common use:
 "Hitting a nail with the handle of the hammer"
 But the phrase is not ideal for my purpose.
@@ -24,13 +25,14 @@ you have still failed to use it as a fastener.
 Despite its name,
 Accubid is clearly not meant for bidding.
 Bidding requires an appreciation of uncertainty and risk
-that naive [[decrease-in-sigma|zero-sigma]] "estimating" does nothing to assist.
+that naive [[decrease-in-sigma|zero-sigma]] "estimating"
+does nothing to assist.
 Estimators have to do that part, _the important part_, in their head.
 
 It ought to be glaringly obvious to Trimble
 that their software is not being used as intended.
-The use of items to be budgetary of other item
-which are not known or not present in the database
+The use of items to be budgetary of other items
+which are not known, or are not present in the database
 is perhaps universal,
 even though this false specificity is detrimental
 to both estimating and operations.
@@ -39,7 +41,8 @@ I believe Trimble may be _deliberately avoiding_ respect for uncertainty, despit
 because to support price uncertainty would call into question
 the utility of their biggest earners and up-sells.
 Tra-Ser is the industry gold standard you can't live without,
-but what good is a single price, which isn't even guaranteed for purchase _today_,
+but what good is a single price,
+which isn't even guaranteed for purchase _today_,
 compared to a range estimated for the lifetime of the project?
 If you believe we live in Trimble's fantasy world
 where you can buy out a bid BOM as-is