vault backup: 2025-10-01 17:05:32
This commit is contained in:
@@ -69,7 +69,7 @@ Optimizing the takeoff process means:
|
||||
> Recent events have complicated my philosophy above.
|
||||
> It appears that similar efforts have already been made here,
|
||||
> their success being a matter of perspective.
|
||||
> Is it acceptable that optimal
|
||||
> Is it acceptable that optimal
|
||||
|
||||
#### Naming Conventions (Use Case vs. Description)
|
||||
|
||||
@@ -145,11 +145,11 @@ Uncertainty being a necessity of estimating,
|
||||
the language and tools that we use
|
||||
must facilitate discussions of risk management.
|
||||
In estimation in fields other than construction
|
||||
it is common to give an estimate as a *confidence interval*,
|
||||
it is common to give an estimate as a _confidence interval_,
|
||||
a range in which a result has a certain percentage chance to fall.
|
||||
This interval can be determined from a population of possible prices.
|
||||
|
||||
The *accuracy* of a risk-oriented estimate remains roughly the same
|
||||
The _accuracy_ of a risk-oriented estimate remains roughly the same
|
||||
(approaching 100% with continuous input)
|
||||
through the takeoff process and, assuming no incorrect input,
|
||||
is entirely out of the hands of the estimator doing the "takeoff".
|
||||
|
||||
Reference in New Issue
Block a user