vault backup: 2026-05-23 01:26:08
This commit is contained in:
@@ -12,4 +12,4 @@ Below is a plot of [[pdi-estimating]] error for every estimate stage.
|
||||
The data is not ideal, being sourced from the default bid sheet data.
|
||||
The majority have baseline dates in 2020 to 2022.
|
||||
|
||||
![[pdi-estimating-error-kde.png]]
|
||||
> _I've removed this plot because it misrepresented the data._
|
||||
|
||||
@@ -0,0 +1,44 @@
|
||||
---
|
||||
id: 2026-05-22T11:57:18-0400
|
||||
title: 2026-05-22 11:57:18
|
||||
tags: []
|
||||
daily: "[[2026-05-22]]"
|
||||
---
|
||||
# 2026-05-22 11:57:18
|
||||
|
||||
## ConEst's Purpose Considering its Accuracy
|
||||
|
||||
I removed [[2026-05-21_16-18-20]]'s plot
|
||||
because I screwed up the error calculation.
|
||||
After more rigorous investigation
|
||||
and more recent project data
|
||||
(the same new bids are based on)
|
||||
I'm happier with this one.
|
||||
|
||||
![[pdi-estimating-error-kde.png]]
|
||||
|
||||
The plot suggests that [[conest]]'s role
|
||||
is not in decreasing cost [[uncertainty]],
|
||||
because it does not appear to do so more than marginally.
|
||||
|
||||
I'm lead to speculate that our purpose is in determining crew loading,
|
||||
which is cool with me,
|
||||
labor is the more interesting part of [[construction-estimating]],
|
||||
however our methods are not well suited to the purpose.
|
||||
After all, the majority of it is calculated in [[ms-excel]].
|
||||
See [[pdi-labor-plan]].
|
||||
|
||||
> A less cautious man than I might wonder
|
||||
> if the negative bias apparent in Bid and ConEst
|
||||
> is indicative of systematic [[incentives|incentive]] gaming,
|
||||
> since if it we could change nothing of our process
|
||||
> and simply add contingency to address it.
|
||||
|
||||
***
|
||||
|
||||
> Our use of "WBS" is technically inaccurate.
|
||||
> The [[pdi-wbs|PDI "WBS"]] is more accurately called
|
||||
> [[earned-value-management#Schedule|the project schedule]],
|
||||
> which is the document which defines the planned value of each task.
|
||||
> On the other hand, project schedule is a terrible name for a specific document,
|
||||
> so I don't blame us for stealing WBS.
|
||||
@@ -0,0 +1,84 @@
|
||||
---
|
||||
id: 2026-05-22T13:11:50-0400
|
||||
title: 2026-05-22 13:11:50
|
||||
tags: []
|
||||
daily: "[[2026-05-22]]"
|
||||
---
|
||||
# 2026-05-22 13:11:50
|
||||
|
||||
## Editor Enhancements for Obsidian
|
||||
|
||||
### Conditional Soft Wrapping
|
||||
|
||||
As noted in [[2026-05-20_12-23-54#Footnotes as Sidenotes for Obsidian]]
|
||||
I'm enjoying using the [[obsidian]] editor's `Readable Line Length` option,
|
||||
but in source mode it guarantees that lines with external links will be wrapped.
|
||||
|
||||
I'd prefer if link URL's were allowed to spill into the gutter like tables.
|
||||
|
||||
| this | table | has | long | lines, | but | they | will | not | be | wrapped |
|
||||
| ---- | ----- | --- | ---- | ------ | --- | ---- | ---- | --- | --- | ------- |
|
||||
| | | | | | | | | | | |
|
||||
|
||||
#### Rules
|
||||
|
||||
Syntax made less readable by wrapping
|
||||
(i.e. tables)
|
||||
should never be wrapped.
|
||||
|
||||
Syntax that can not be hard wrapped
|
||||
(i.e. headers, callout titles)
|
||||
must be soft wrapped.
|
||||
|
||||
The active line should be soft wrapped.
|
||||
|
||||
#### Implementation
|
||||
|
||||
This should be possible with CSS snippets.
|
||||
I was briefly able to disable _all_ wrapping,
|
||||
but in trying to limit the application
|
||||
I forgot the original selector.
|
||||
|
||||
This one should work, doesn't.
|
||||
|
||||
```css
|
||||
/* select divs with only class cm-line */
|
||||
/* this excludes most special lines and the active line */
|
||||
div[class="cm-line"] {
|
||||
white-space: pre;
|
||||
text-wrap-mode: nowrap;
|
||||
}
|
||||
```
|
||||
|
||||
### Render-Time Text Replacement Rules
|
||||
|
||||
There are several plugins which replicate [[ms-word]]'s behavior
|
||||
of substituting digraphs with special characters as you type,
|
||||
but what I'm looking for
|
||||
is [[asciidoc]]-style [character replacement substitutions](https://docs.asciidoctor.org/asciidoc/latest/subs/replacements/).
|
||||
These would limit ambiguous Unicode.
|
||||
|
||||
I have found one community plugin which approaches this behavior,
|
||||
[Dynamic Text Concealer](https://github.com/mattcoleanderson/obsidian-dynamic-text-concealer),
|
||||
but, as now seems typical of implementations of features I want,
|
||||
it is a buggy, poorly-translated mess which is missing key functionality.
|
||||
|
||||
Obsidian's Markdown to HTML transpiler
|
||||
will always wrap with a space, so
|
||||
|
||||
```markdown
|
||||
lorem ipsum---
|
||||
set amet.
|
||||
```
|
||||
|
||||
will render as "lorem ipsum--- set amet".
|
||||
|
||||
> My use of triple hyphens (`foo---bar`)
|
||||
> is unfortunately quite niche.
|
||||
> There are two common digraphs
|
||||
> used to represent em dashes with a limited character set
|
||||
> which have been around since the typewriter:
|
||||
> `foo - bar`, which is an assault on the eyes,
|
||||
> lacking any of the authority of the em dash;
|
||||
> and `foo--bar`, which is better
|
||||
> but would be ambiguous with the en dash.
|
||||
@@ -0,0 +1,22 @@
|
||||
---
|
||||
id: 2026-05-22T19:11:54-0400
|
||||
title: 2026-05-22 19:11:54
|
||||
tags: []
|
||||
daily: "[[2026-05-22]]"
|
||||
---
|
||||
# 2026-05-22 19:11:54
|
||||
|
||||
## AACE International
|
||||
|
||||
[[aace-international|AACE]] is for [[construction]]
|
||||
what [[project-management-institute|PMI]] is for [[software]].
|
||||
|
||||
[[merrow_2022_contract-strategies]] suggests that prioritizing cost control
|
||||
is associated with overrun and schedule slip.
|
||||
|
||||
### Canons of Ethics
|
||||
|
||||
Having a defined code of ethics is very cool,
|
||||
I only wish they took a stronger stance on [[incentives]].
|
||||
|
||||
![[aacei-canons-of-ethics#II.15]]
|
||||
Reference in New Issue
Block a user