primitive action
Table of Contents
- Backlinks
- lifestyle script
- zettels as primitive
- vicinity of primitives
- use zettelkasten as software engineer
- social as primitive
- small and simple works
- preview before lecture
- emacs allow primitive programming
- developmental skill aquisition with general purpose actuator
- coding the activity
- 30 minute dumping as primitive
- 30 minute dumping as primitive
- review 2024-01-27
primitive action is defined as an atomic action that is simple and self-evident to you, such that you know how it’s done without reference. Examples would be Travel from Location A to Location B, Buy Alcohol, Cook meal.
- primitive action may not be trivial
- primitive action can be acquired
- hierarchy of primitive actions
- selection of primitives
- select thinking primitives to better mental state
- small and simple works
Backlinks
lifestyle script
(Writing lifestyle script
: primitives > Primitive Actions)
a selected set of primitive action. documentation could address the state it intends to transist from and to
zettels as primitive
Use the form of zettel to be primitive action for any reading or writing.
vicinity of primitives
vicinity of primitives refers to parts of the that can be easily reached with a few combination of primitive actions.
use zettelkasten as software engineer
primitive actions relevent to software engineer mainly comprise:
- how a thing (like sorting) is done generally (in
algorithm
level) - how a thing (like string slicing) is
implemented
in a specific [programming language] [framework] - definition of
patterns and concepts
(like steps of handelling HTTP request) andsyntax
(like function wrapper in python) - utility scripts and
snippets
for specific problem
social as primitive
in general context, use talk to people about {your idea, their idea}
as a primitive action.
small and simple works
A change/action performed by man would work (consistently) only if it is small and simple enough for one to qualify as a primitive action (a simple one).
Examples:
- all zettelkasten primitives are small and simple, one increment at a time
capture
1
idea; write1
zettel; add1
link… - Ferriss, Timothy ::: The 4-Hour Body: An Uncommon Guide to Rapid Fat-Loss, Incredible Sex, and Becoming Superhuman expilicitly attributes its robustness over other fat loss methods over (p24) “the changes are either small or simple and often both”
preview before lecture
Objective of this preview is to build an organization of primitive actions and atomic ideas.(bayesian formula, covariance, gausian distribution, localization…)
A consistent, pre-built privimitive organization make it easier to organize in lecture and recall later.
emacs allow primitive programming
primitive action in emacs refers to:
- keybindings, which could include prefix(C,M).
so f1, j, C-c C-f, M-x org- screen TAB, f4…
developmental skill aquisition with general purpose actuator
(Methodology & Expected discipline involvement)
- Handelling of signal in abstract(logic; machine learning) and in raw(signals processing; embodied robotics)
- Literature review, experiment and evaluation/organization on existing approaches
- Environemnt and task/skill design.
- Review and develop knowledge representation and self-programming techniques.
- primitive action engineering: complex action made from primitive actions.
coding the activity
(Design > Depth of design work)
How detailed should designs be? How much of the function should be completed before opening a .java
file?
3 predicates could come in handy:
- primitive
- design until whatever is left is primitive to you to write in the language
- formula
- if you have broken down a piece of the function to a formula, you are pretty much done for design
- start to end
- go through the design and see if they connect the start and the end
30 minute dumping as primitive
dumping everything worth keeping track of in last 30 minutes(or after last dumping) into capture, todos, or zettelkasten
Done at least once every 30 minutes.
Do it as a primitive action in general context
30 minute dumping as primitive
(Whys > why primitive action)
so that the state of having a clear mind
and more knowledge at my finger tip
is closer to me.
review 2024-01-27
- on Herman’s systems:
- I simplified most existing things:
- capture - I now use one capture inbox for everything: task, ideas, bookmark, so GTD capture and research capture are combined. This is a practice, not to say it is good or bad, it is simple enough to work decently
- review - I now review my zettelkasten daily, but sometimes there’s more than what I can do on the instant.(like the whole of my research system is like a big pile of nonsense right now, and so is my GTD integration; I’ll reduce, or delete them entirely very shortly after)
- tags - I don’t use it as of now. I may start it somewhere in the future, but now I don’t use it
- process - One process diagram should be enough, instead of this giant load of text
- engage - checking agenda, and that’s it. I use phone timer more often now.
- in general, this whole page is very not useful. I use current life script more now, although it does not contain information on research and stuff. I could extend it to include these though.
- I use some new concepts, like primitive action, and new set of very limited primitives in top of my mind.
- I practice slow-carb diet and use a fitness program now, they should be included.
- It is decided: I’m stuffing everything in the lifestyle script. research is a lifestyle, fitness is a lifestlye, shake the staticity off is a lifestyle, I live and I live with a style. Yet I may want to have it split into smaller pieces
- I simplified most existing things:
- on the zettelkasten
- lots of places for reduction and improvement it is not very useful in general. old, rambling note that should be discarded in second batch processing are scattering at places where I quote them, thinking they are good concise notes. A lot of places could use visuals and concise words, examples or links to concrete examples
- on the tasks
- the reduction is working, there’s a lot to think for the tasks. this means a change to the my GTD zettel is in request
- on tracking and experiments
- tracking is hard to remember. but it is damn useful.
- highlight + comment method and capture is a form of tracking thoughts
- so I think I should track some specific, explicitly measureable things, and have them noted somewhere so I don’t forget