vault backup: 2026-04-15 17:43:32
This commit is contained in:
@@ -0,0 +1,32 @@
|
||||
---
|
||||
id: 2026-04-15T09:18:45-04:00
|
||||
aliases: []
|
||||
title: 2026-04-15 09:18:45
|
||||
tags:
|
||||
- authorship/original
|
||||
- destiny/permanent
|
||||
- status/draft
|
||||
- type/periodic/timestamped
|
||||
dg-publish: true
|
||||
date-created: 2026-04-15T09:18:45-04:00
|
||||
daily: "[[2026-04-15]]"
|
||||
weekly: "[[2026-W16]]"
|
||||
monthly: "[[2026-04]]"
|
||||
quarterly: "[[2026-Q2]]"
|
||||
yearly: "[[2026]]"
|
||||
---
|
||||
# 2026-04-15 09:18:45
|
||||
|
||||
[[snyder_2020_voltage-drop-calculations]]
|
||||
closes with this string of [Morse code](https://en.wikipedia.org/wiki/Morse_code):[^1]
|
||||
|
||||
```morse
|
||||
.-. . ... .--. . -.-. - ..-. ..- .-.. .-.. -.-- ... ..- -... -- .. - - . -..
|
||||
```
|
||||
|
||||
[^1]: Original characters were converted to ASCII, whitespace normalized.
|
||||
The sequence reads "RESPECTFULLYSUBMITTED".
|
||||
|
||||
A Morse code translator,
|
||||
including parser and beeper,
|
||||
would be a great beginner programming project.
|
||||
@@ -0,0 +1,34 @@
|
||||
---
|
||||
id: 2026-04-15T11:00:38-04:00
|
||||
aliases: []
|
||||
title: 2026-04-15 11:00:38
|
||||
tags:
|
||||
- authorship/original
|
||||
- destiny/permanent
|
||||
- status/draft
|
||||
- type/periodic/timestamped
|
||||
dg-publish: true
|
||||
date-created: 2026-04-15T11:00:38-04:00
|
||||
daily: "[[2026-04-15]]"
|
||||
weekly: "[[2026-W16]]"
|
||||
monthly: "[[2026-04]]"
|
||||
quarterly: "[[2026-Q2]]"
|
||||
yearly: "[[2026]]"
|
||||
---
|
||||
# 2026-04-15 11:00:38
|
||||
|
||||
## Equipment Grounding Conductor Sizing
|
||||
|
||||
[[virginia-live-casino-and-hotel]]
|
||||
one-lines specify ~~a feeder~~ as
|
||||
`(6) SETS OF: 4#600, 1#450G, 4"C.`
|
||||
|
||||
The use of 450kcmil for the EGC is strange:
|
||||
|
||||
* It is not a size specified by
|
||||
[[nfpa-70_250_grounding#Table 250.122 Minimum Size Equipment Grounding Conductors for Grounding Raceway and Equipment|Table 250.122]]
|
||||
|
||||
* it is a non-standard size anyway,
|
||||
not appearing in [[nfpa-70_ch09|Chapter 9]] tables,
|
||||
the [[neca-mlu]],
|
||||
or our Accubid database.
|
||||
@@ -0,0 +1,38 @@
|
||||
---
|
||||
id: 2026-04-15T14:54:00-04:00
|
||||
aliases: []
|
||||
title: 2026-04-15 14:54:00
|
||||
tags:
|
||||
- authorship/original
|
||||
- destiny/permanent
|
||||
- status/draft
|
||||
- type/periodic/timestamped
|
||||
dg-publish: true
|
||||
date-created: 2026-04-15T14:54:00-04:00
|
||||
daily: "[[2026-04-15]]"
|
||||
weekly: "[[2026-W16]]"
|
||||
monthly: "[[2026-04]]"
|
||||
quarterly: "[[2026-Q2]]"
|
||||
yearly: "[[2026]]"
|
||||
---
|
||||
# 2026-04-15 14:54:00
|
||||
|
||||
## Working While Standing for Focus
|
||||
|
||||
Yesterday Baker (our current project engineer)
|
||||
asked if I use the standing mode of my desk often.
|
||||
I told him I really didn't,
|
||||
except to show multiple people something on my screens.
|
||||
Thinking of [[kahneman_2011_thinking]],
|
||||
I stated that this was a conscious choice
|
||||
because one can not think as deeply while standing as while sitting.[^1]
|
||||
|
||||
[^1]: This is mostly justification for a preexisting behavior.
|
||||
I think the largest part of my tendency
|
||||
is that I don't like people watching me work.
|
||||
|
||||
He clarified that he did this in order to _focus_,
|
||||
which I have heard before but never gave much credit.
|
||||
I then made the now obvious connection
|
||||
that impairing deep thinking is exactly the method
|
||||
by which standing improves focus.
|
||||
@@ -0,0 +1,65 @@
|
||||
---
|
||||
id: 2026-04-15T15:15:07-04:00
|
||||
aliases: []
|
||||
title: 2026-04-15 15:15:07
|
||||
tags:
|
||||
- authorship/original
|
||||
- destiny/permanent
|
||||
- status/draft
|
||||
- type/periodic/timestamped
|
||||
- topic/meta
|
||||
dg-publish: true
|
||||
date-created: 2026-04-15T15:15:07-04:00
|
||||
daily: "[[2026-04-15]]"
|
||||
weekly: "[[2026-W16]]"
|
||||
monthly: "[[2026-04]]"
|
||||
quarterly: "[[2026-Q2]]"
|
||||
yearly: "[[2026]]"
|
||||
---
|
||||
# 2026-04-15 15:15:07
|
||||
|
||||
## Considering the Role of Daily Notes in My Vault
|
||||
|
||||
I think daily notes still have a good use case for me,
|
||||
but I'm not sure of the details.
|
||||
|
||||
What content should be daily and what timestamped
|
||||
is a matter of the logic of links and tags.
|
||||
|
||||
Daily notes should only contain content _about that day_.
|
||||
|
||||
What's tricky about this is that
|
||||
|
||||
### What Daily Notes Should Contain
|
||||
|
||||
#### Tracking
|
||||
|
||||
```
|
||||
Made recipe: [[granola]]
|
||||
```
|
||||
|
||||
### What Daily Notes Should Not Contain
|
||||
|
||||
#### Synthesis
|
||||
|
||||
The utility of timestamped notes
|
||||
is that, since the topic is self contained,
|
||||
the note's tags apply to all content within it.
|
||||
Contrast with my previous system,
|
||||
more like a traditional diary,
|
||||
where synthesis for myriad topics
|
||||
was grouped arbitrarily
|
||||
by the day I happened to make a connection.
|
||||
|
||||
### What Daily Notes Could Contain
|
||||
|
||||
#### Objective Descriptions of Events
|
||||
|
||||
I see two options, neither attractive:
|
||||
|
||||
##### Option 1: Prose
|
||||
|
||||
because it would be very boring to write.
|
||||
|
||||
##### Option 2: Standard Terse Format
|
||||
|
||||
@@ -0,0 +1,66 @@
|
||||
---
|
||||
id: 2026-04-15T15:59:02-04:00
|
||||
aliases: []
|
||||
title: 2026-04-15 15:59:02
|
||||
tags:
|
||||
- authorship/original
|
||||
- destiny/permanent
|
||||
- status/draft
|
||||
- type/periodic/timestamped
|
||||
dg-publish: true
|
||||
date-created: 2026-04-15T15:59:02-04:00
|
||||
daily: "[[2026-04-15]]"
|
||||
weekly: "[[2026-W16]]"
|
||||
monthly: "[[2026-04]]"
|
||||
quarterly: "[[2026-Q2]]"
|
||||
yearly: "[[2026]]"
|
||||
---
|
||||
# 2026-04-15 15:59:02
|
||||
|
||||
Probably the most obviously helpful convention
|
||||
of [[note-taking]]/[[personal-knowledge-management]]
|
||||
that I use in [[this-notebook]]
|
||||
is how I journal my mistakes.
|
||||
|
||||
1. The **mistake**,
|
||||
the objectionable actions taken
|
||||
that lead to the problem.
|
||||
|
||||
2. The **problem**,
|
||||
the undesirable state resulting from the mistake
|
||||
This includes the immediate outcome
|
||||
and, if applicable, the cost of correction.
|
||||
|
||||
3. The **rationale**,
|
||||
the reason for the mistake.
|
||||
|
||||
***
|
||||
|
||||
The intent is that by recording this conflict
|
||||
in as much detail as practical
|
||||
I can determine what actions I can take
|
||||
to prevent the most pain from future mistakes.
|
||||
|
||||
***
|
||||
|
||||
Rationale is the most important part of the entry.
|
||||
It's not helpful to say
|
||||
If that's truly what seems to be the cause,
|
||||
consider your state at the time:
|
||||
Were you mentally exhausted?
|
||||
If so, was it due to workload or issues at home?
|
||||
|
||||
"I was being stupid," and "I wasn't thinking,"
|
||||
are not informative rationales.
|
||||
"I will try harder," and "I will pay more attention"
|
||||
are not actionable plans.
|
||||
|
||||
***
|
||||
|
||||
"Mistake" may be a misnomer,
|
||||
because acceptability is not objective.
|
||||
For example:
|
||||
two [[conest]] senior estimators
|
||||
may disagree on the acceptability of a certain [[heuristics|heuristic]].
|
||||
It may still be useful to record criticism from the more stringent senior
|
||||
as a mistake, even if their position is less popular.
|
||||
@@ -0,0 +1,33 @@
|
||||
---
|
||||
id: 2026-04-15T17:31:57-04:00
|
||||
aliases: []
|
||||
title: 2026-04-15 17:31:57
|
||||
tags:
|
||||
- authorship/original
|
||||
- destiny/permanent
|
||||
- status/draft
|
||||
- type/periodic/timestamped
|
||||
dg-publish: true
|
||||
date-created: 2026-04-15T17:31:57-04:00
|
||||
daily: "[[2026-04-15]]"
|
||||
weekly: "[[2026-W16]]"
|
||||
monthly: "[[2026-04]]"
|
||||
quarterly: "[[2026-Q2]]"
|
||||
yearly: "[[2026]]"
|
||||
---
|
||||
# 2026-04-15 17:31:57
|
||||
|
||||
A peer, not intending to,
|
||||
convinced me I should buy my next car
|
||||
as much over email as possible.
|
||||
|
||||
Consider my requirements for a new vehicle:
|
||||
|
||||
* Reliable make: Honda or Toyota
|
||||
* Compact [body style](https://en.wikipedia.org/wiki/Car_body_style):
|
||||
Sedan, Crossover, or Hatchback
|
||||
(really just not a pickup or SUV)
|
||||
|
||||
I thought that these requirements were too open
|
||||
to make research like peer suggested impractical,
|
||||
but I realized now that they narrow my selection considerably.
|
||||
Reference in New Issue
Block a user