vault backup: 2026-02-02 17:10:34
This commit is contained in:
+39
-1
@@ -53,9 +53,47 @@ function Import-Markdown {
|
||||
}
|
||||
```
|
||||
|
||||
That pattern is bizarre, and it needs better error handling,
|
||||
That match expression is bizarre,
|
||||
and the whole thing needs better error handling,
|
||||
but it works.
|
||||
|
||||
A `Where-Markdown` for filtering by tags
|
||||
and a `{Verb}-Markdown` for modifying tags
|
||||
would be idiomatic.
|
||||
|
||||
## 2026-02-02 12:18
|
||||
|
||||
### Sleeving Takeoff Breakdown Direction
|
||||
|
||||
Updated [[sleeving-takeoff#Breakdowns]]
|
||||
per clarification with Joel.
|
||||
Previous direction below.
|
||||
|
||||
> * `Area` = "01 - Feeders/Risers ..."
|
||||
> * `Phase` = "Feeders"
|
||||
> * `System` = "FRR - Feeders and Risers"
|
||||
>
|
||||
> For all sleeving, regardless of application.
|
||||
|
||||
I feel certain I received this from someone I trust
|
||||
because I've been doing it against my better judgement,
|
||||
but either it wasn't Joel (Ben maybe?)
|
||||
or he was referring to a different scenario
|
||||
(which my notes no longer cover).
|
||||
|
||||
***
|
||||
|
||||
I asked Joel if he could think of any direction
|
||||
that I might have misinterpreted
|
||||
to get to that above,
|
||||
but he said he could not.
|
||||
|
||||
***
|
||||
|
||||
I spoke with Willie about it,
|
||||
he says he's always put sleeving in each relevant system.
|
||||
I told him I knew it had to have been spoken
|
||||
because I remember it being justified as WBS allocation thing,
|
||||
but I think now Joel told me correctly at the time,
|
||||
that is, gave me the same direction he gave me today,
|
||||
I just somehow heard the complete opposite.
|
||||
|
||||
Reference in New Issue
Block a user