vault backup: 2026-04-15 22:32:11
This commit is contained in:
@@ -0,0 +1,86 @@
|
||||
---
|
||||
id: 2026-04-15T19:28:06-04:00
|
||||
aliases: []
|
||||
title: 2026-04-15 19:28:06
|
||||
tags:
|
||||
- authorship/original
|
||||
- destiny/permanent
|
||||
- status/draft
|
||||
- type/periodic/timestamped
|
||||
daily: "[[2026-04-15]]"
|
||||
date-created: 2026-04-15T19:28:06-04:00
|
||||
dg-publish: true
|
||||
monthly: "[[2026-04]]"
|
||||
quarterly: "[[2026-Q2]]"
|
||||
weekly: "[[2026-W16]]"
|
||||
yearly: "[[2026]]"
|
||||
---
|
||||
# 2026-04-15 19:28:06
|
||||
|
||||
## "Obsidian for Learning Part II: Process"
|
||||
|
||||
["Obsidian for Learning Part II: Process" - No Boilerplate](https://youtu.be/Tyw6quANpiY)
|
||||
|
||||
No Boilerplate first got me into [[obsidian]]
|
||||
so to see them endorse such strange patterns without qualification is frustrating.
|
||||
I suspect that Tris is a victim of [[drinking-ones-own-kool-aid]].
|
||||
|
||||
***
|
||||
|
||||
Clearly we have different priorities for our vaults,
|
||||
but I tend to think mine are more consistent.
|
||||
|
||||
***
|
||||
|
||||
I couldn't trade git version control
|
||||
for the convenience of Obsidian Sync on mobile.
|
||||
The timeline of my understanding
|
||||
is just as important as the result.
|
||||
|
||||
***
|
||||
|
||||
Tris has repeated ~~somewhere~~
|
||||
a piece of advice for Obsidian [[personal-knowledge-management]]
|
||||
that I think ought to be nonnegotiable.
|
||||
|
||||
> You get one vault. Figure it out.
|
||||
|
||||
***
|
||||
|
||||
PKM, as I understand it, is in service of [[synthesis]],
|
||||
that if you have access to your knowledge
|
||||
without the effort and problems of recall,
|
||||
your processing power can be spent making connections.
|
||||
|
||||
***
|
||||
|
||||
The problem with titled notes
|
||||
is that titles are a barrier to writing
|
||||
that serve no purpose.
|
||||
|
||||
> [!quote] [Steph Ango "Evergreen notes turn ideas into objects that you can manipulate"](https://stephango.com/evergreen-notes)
|
||||
> * A company is a superorganism
|
||||
> * All input is error
|
||||
> * Calmness is a superpower
|
||||
> * Concise explanations accelerate progress
|
||||
> * Cross the chasm
|
||||
> * Everything is a remix
|
||||
> * Writing is telepathy
|
||||
> * You have no obligation to your former self
|
||||
> * etc
|
||||
|
||||
These are not summaries,
|
||||
this is quippy bullshit.
|
||||
If it seems like this would be a good way to organize ideas
|
||||
you are vastly underestimating the number of ideas you have.
|
||||
At scale you won't be able to distinguish between
|
||||
"Concise explanations accelerate progress"
|
||||
and "Accelerating progress explanations",
|
||||
and if titles-as-filenames doesn't aid organization
|
||||
you might as well use timestamps, which do.
|
||||
|
||||
***
|
||||
|
||||
Still I think the best way to start Obsidian
|
||||
is to install it with no expectations or introduction
|
||||
then write everything in unique notes with the core plugin.
|
||||
Reference in New Issue
Block a user