60 lines
1.2 KiB
Markdown
60 lines
1.2 KiB
Markdown
---
|
|
id: 2026-04-15T15:15:07-0400
|
|
title: 2026-04-15 15:15:07
|
|
tags:
|
|
- status/draft
|
|
- topic/meta
|
|
date-created: 2026-04-15T15:15:07-04:00
|
|
daily: "[[2026-04-15]]"
|
|
---
|
|
# 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.
|
|
|
|
> Timestamped notes are still labeled by time like dailies,
|
|
> but they aren't grouped.
|
|
|
|
### 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
|
|
|