vault backup: 2026-03-03 14:58:23

2026-03-03 14:58:23 -05:00
parent ccd51d7685
commit a62b1a701a
25 changed files with 108 additions and 43 deletions
@@ -71,12 +71,12 @@ What's being done to prevent it from re-emerging?
 It is my belief that the most practical solution
 is the frequent rotation of estimators in senior teams.
 It is in the interest of estimators
-that their personal heuristics not depend on who they're working for,
+that their personal [[heuristics]] not depend on who they're working for,
 so they can be expected to call attention to inconsistency
 allowing it to be addressed permanently.

 The only other option I can imagine
-is to document exact procedures for every scenario,
+is to document _exact_ procedures for _every_ scenario,
 which is obviously foolhardy.

 ### Less Important