vault backup: 2025-12-17 17:03:56
This commit is contained in:
@@ -0,0 +1,37 @@
|
||||
---
|
||||
id:
|
||||
aliases: []
|
||||
title: Ambiguity in Construction Estimating
|
||||
tags:
|
||||
- authorship/original
|
||||
- destiny/permanent
|
||||
- status/incomplete
|
||||
- topic/ambiguity
|
||||
- topic/construction
|
||||
- topic/estimating
|
||||
- type/cross-topic
|
||||
---
|
||||
# Ambiguity in Construction Estimating
|
||||
|
||||
Cross-topic of [[ambiguity]] and [[construction-estimating]].
|
||||
|
||||
I hate to come off as pedantic,
|
||||
but I care a lot about standardized terminology
|
||||
because spending a few minutes to be more thoughtful in specification
|
||||
can save hundreds of people cumulative hours of confusion.
|
||||
And the problem with standardization, of course,
|
||||
is that sometimes it works,
|
||||
and undoing years of poor conditioning is... not easy.
|
||||
|
||||
## Naming Conventions (Use Case vs. Description)
|
||||
|
||||
Related: [[realism-vs-instrumentalism]]
|
||||
|
||||
Naming by use case is intuitive for those without estimating or field experience,
|
||||
but has the side effect that those accustomed to the names
|
||||
will inevitably _treat them as descriptive_.
|
||||
|
||||
| Use Case | Description |
|
||||
| ------------------- | ------------- |
|
||||
| Hi-Hat | Daisy-Chain |
|
||||
| Furnished By Others | Rough-In Only |
|
||||
Reference in New Issue
Block a user