wired could be good for skill practice
Table of Contents
On one constraint: the skill should only involve fixed, easy, pre-programmed things. You don’t need to do any design or big picture, the skill just decentralizingly works bit by bit.
1. example: batch process
One example is batch processing. When I’m batch processing my notes, I typically do one of 4 things:
- devide it to seperate points
- merge some of the similar(or delete repeated points)
- reliterate it to zettel, and move it into my zettelkasten implementation
- reliterate it to task, and move it into my my GTD integration.
And those are it. Nothing more would be expected, and when I notice there’s something big that I would want to do(like devide index into smaller navigation notes), my capture place is right by my hand and I could just add it to a capture or a task, to be done later, as I normally would.
As such, it is fine to get wired as it can do no harm, and the enhenced focus could come in handy letting my get more notes processed.
2. Downside of being wired on skill practice
The major downside however is that wiredness narrows, and quality skill practice often would require focus and balance on a range of objects.
For note processing, the end of the road is that you’d be copy and pasting your capture notes to your zettelkasten, which is a disgusting practice. (it messes your zettelkasten up to journal without page order)
Backlinks
wired
Wired/wiredness/staticity refers to the state where:
- your attention is [intensively] projected to a fixed, small space [screen, cat, mostly screen]
- the state tends to enhence itself, resulting in you focusing on a fixed, small space for a long time.