vault backup: 2026-03-23 17:15:27
This commit is contained in:
@@ -28,7 +28,7 @@ and something very specific.[^3]
|
||||
especially to someone unfamiliar with the specifics of either.
|
||||
|
||||
For lack of a better term I've been thinking of this as an SEO problem,
|
||||
but the bigger problem is that it invites [[ambiguity#Category Mistake|Category Mistake]],
|
||||
but the bigger problem is that it invites [[category-mistake]],
|
||||
whereby the ignorant listener associates traits unique to the example
|
||||
to all things that the name could describe.
|
||||
|
||||
|
||||
@@ -30,6 +30,6 @@ That is, quantifying the influence of an input on the output.
|
||||
When an estimator says that some factor is not worth consideration ("it's pennies")
|
||||
it is usually meant that the estimate is not especially **sensitive** to that factor.
|
||||
|
||||
Sensitivity, I think, is a much quicker concept to grasp
|
||||
than [[uncertainty#Value of Information|the value of information]],
|
||||
[[sensitivity|Sensitivity]], I think, is a much quicker concept to grasp
|
||||
than [[value-of-information|the value of information]],
|
||||
even if VOI can explain the same motivations and more completely.
|
||||
|
||||
@@ -0,0 +1,57 @@
|
||||
---
|
||||
id: 2026-03-23T12:48:49-04:00
|
||||
aliases: []
|
||||
title: 2026-03-23 12:48:49
|
||||
tags:
|
||||
- authorship/original
|
||||
- destiny/permanent
|
||||
- status/draft
|
||||
- type/periodic/timestamped
|
||||
- occupational
|
||||
dg-publish: true
|
||||
date-created: 2026-03-23T12:48:49-04:00
|
||||
daily: "[[2026-03-23]]"
|
||||
weekly: "[[2026-W13]]"
|
||||
monthly: "[[2026-03]]"
|
||||
quarterly: "[[2026-Q1]]"
|
||||
yearly: "[[2026]]"
|
||||
---
|
||||
# 2026-03-23 12:48:49
|
||||
|
||||
Joel asked me to give feedback on the project engineer
|
||||
I've had shadowing and helping me on [[charlotte-south-end-hotel]].
|
||||
|
||||
They've been exceptionally engaged,
|
||||
with an impressive ability to follow along with procedures
|
||||
that are based in electrical and general construction considerations
|
||||
that they weren't already familiar with.
|
||||
I told Joel the same.
|
||||
|
||||
I added that I appreciated that their engagement extends
|
||||
to my explanations of my thought processes during takeoff,
|
||||
which can be quite abstract.
|
||||
|
||||
I found the PE's receptivity
|
||||
a pleasant surprise.
|
||||
|
||||
In my experience training estimating,
|
||||
both at Ace and PDI,
|
||||
I have to be _very_ careful with my words
|
||||
to prevent unintended interpretation.
|
||||
More than once I have said casually
|
||||
that some low-[[sensitivity]] consideration "doesn't matter",
|
||||
finding later that the student has over-generalized the direction
|
||||
and is not properly discriminating
|
||||
between significantly different cases.
|
||||
Other times,
|
||||
the student continues to discriminate between nearly identical cases
|
||||
even despite repeated instruction
|
||||
that consideration of the differences is not worth their effort.
|
||||
|
||||
I think both behaviors indicate an inability for abstract thinking.
|
||||
The first case seems like over-abstraction,
|
||||
but in practice it is usually rooted in the principle of least effort.
|
||||
That is, the student assumes
|
||||
that considerations that would be _unpleasant_ to account for
|
||||
are the same as those that are not worth accounting for,
|
||||
which is a [[category-mistake]].
|
||||
Reference in New Issue
Block a user