vault backup: 2026-05-15 00:04:10
This commit is contained in:
Vendored
+1
-1
@@ -1,6 +1,6 @@
|
||||
{
|
||||
"livePreview": false,
|
||||
"readableLineLength": false,
|
||||
"readableLineLength": true,
|
||||
"strictLineBreaks": true,
|
||||
"propertiesInDocument": "visible",
|
||||
"showLineNumber": true,
|
||||
|
||||
@@ -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
|
||||
@@ -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
|
||||
|
||||
Reference in New Issue
Block a user