vault backup: 2025-08-05 17:00:05
This commit is contained in:
@@ -1,7 +1,10 @@
|
||||
---
|
||||
id:
|
||||
aliases: []
|
||||
tags:
|
||||
- estimating
|
||||
- software
|
||||
- type/idea
|
||||
---
|
||||
# Estimating Ergonomics
|
||||
|
||||
@@ -41,7 +44,7 @@ Suppose you were to sketch a takeoff indicating a run
|
||||
2. up to the ceiling
|
||||
3. across the building
|
||||
4. down to a disconnect
|
||||
5. out through a flex connection
|
||||
5. out through a flex connection
|
||||
6. to a piece of equipment
|
||||
|
||||
that's a very complex assembly,
|
||||
@@ -119,7 +122,7 @@ that Trimble or anybody else has.
|
||||
Something that I've realized that really bothers me
|
||||
about the the traditional methods
|
||||
(e.g. database-based takeoff, audit-trail-type-abstraction)
|
||||
is the the *enforced linearity*,
|
||||
is the the _enforced linearity_,
|
||||
which is at odds with the reality of takeoff.
|
||||
|
||||
No matter how you slice it,
|
||||
|
||||
Reference in New Issue
Block a user