first commit
This commit is contained in:
@@ -0,0 +1,29 @@
|
||||
---
|
||||
tags:
|
||||
- estimating/philosophy
|
||||
---
|
||||
# Estimating Philosophy
|
||||
|
||||
Construction estimating is a highly opinionated field, and I am no exception.
|
||||
This page collects my opinions on topics related to the subject,
|
||||
usually as a response to those held by my peers.
|
||||
|
||||
## The Purpose of Construction Cost Estimation
|
||||
|
||||
The purpose of construction cost estimation in practice
|
||||
is not to determine the cost of the scope,
|
||||
which would take far longer than allotted for bid,
|
||||
|
||||
## Estimating Tools
|
||||
|
||||
I am likely one of likely very few estimators with the necessary background
|
||||
to appreciate the compromise-based nature of [[construction-estimating-software]].
|
||||
It's for this reason that I am so fiercely critical of existing examples of it.
|
||||
I am a fervent advocate for [[software-based-estimating]] _as a philosophy_,
|
||||
however, I'm on the fence if current examples implement it well enough to justify their use.
|
||||
|
||||
There is an observable lack of creativity
|
||||
in the construction estimating software development space,
|
||||
consistent with ignorance of consumer need.
|
||||
[[ai-in-estimating]] is a depressing example
|
||||
of how little estimators can expect for innovative features from these companies.
|
||||
Reference in New Issue
Block a user