vault backup: 2026-04-18 19:02:34

This commit is contained in:
2026-04-18 19:02:34 -04:00
parent 0743e6f194
commit fabb84866b
12 changed files with 541 additions and 37 deletions
-1
View File
@@ -5,7 +5,6 @@ title: 2025-07-18 ??:??:??
tags:
- topic/construction
- topic/estimating
- type/anecdote
dg-publish: true
daily: "[[2025-07-18]]"
---
-10
View File
@@ -1,10 +0,0 @@
---
id: 2026-04-18_00-37-27
aliases: []
title: 2026-04-18_00-37-27
tags: []
dg-publish: true
daily: "[[2026-04-18]]"
---
# 2026-04-18_00-37-27
+19
View File
@@ -0,0 +1,19 @@
---
id: 2026-04-18_15-40-55
aliases: []
title: 2026-04-18_15-40-55
tags: []
dg-publish: true
daily: "[[2026-04-18]]"
---
# 2026-04-18_15-40-55
Follow-up to [[2026-04-15_19-28-06#"Obsidian for Learning Part II: Process"]]:
While I have nothing else positive to say about the video,
I do like, and have implemented, the `up` property.
Recently I've been less certain that [[tags]] serve a useful function.
`up` appeals to me because it is intuitive but versatile.
I'm using it now for implementations of templates
like [[recipes]] and [[conest-projects]].
+28
View File
@@ -0,0 +1,28 @@
---
id: 2026-04-18_18-44-11
aliases: []
title: 2026-04-18_18-44-11
tags: []
dg-publish: true
daily: "[[2026-04-18]]"
---
# 2026-04-18_18-44-11
I don't see many anymore
on account of my change in workplace,
but I think often of [[construction-estimating|estimators]]
like I once knew well,
who somehow managed to be in the industry for decades
while believing that it is poor estimating
to accept any risk in a bid,
that all uncertainty must be clarified.
Of course,
they didn't believe that with their actions,
only their words.
Suppose though we take them at those words,
like you do when you're a new estimator
who barely knows what the word means,
you're just happy to be out of the field
where it's hot and no one is ever happy.