As of a couple of days ago, I have a file where I save lessons from such review exercises for reviewing them periodically.
Some are in weekly review category and some in monthly review. Every day when I do my daily recall I now also check through the lessons in the corresponding weekday and monthday tag.
Here’s how my file currently looks like: (I use some short codes for typing faster like “W=what”, “h=how”, “t=to”, “w=with” and maybe some more.)
- Mon - [[lesson—clarify Gs on concrete examples]] - [[lesson—delegate whenever you can (including if possible large scale responsibilities where you need to find someone competent and get funding)]] - [[lesson—notice when i search for facts (e.g. w GPT) (as opposed to searching for understanding) and then perhaps delegate if possible]] - Tue - [[lesson—do not waste time on designing details that i might want to change later]] - [[periodic reminder—stop and review what you’d do if you had pretty unlimited funding → if it could speed you up, then perhaps try to find some]] - Wed - [[lesson—try to find edge cases where your current model does not work well]] - notice when sth worked well (you made good progress) → see h you did that (-> generalize W t do right next time) - Thu - it’s probably useless/counterproductive to apply effort for thinking. rather try to calmly focus your attention. - perhaps train to energize the thing you want to think about like a swing through resonance. (?) - Fri - [[lesson—first ask W you want t use a proposal for rather than directly h you want proposal t look like]] - Sat - [[lesson—start w simple plan and try and rv and replan, rather than overoptimize t get great plan directly]] - Sun - group - plan for particular (S)G h t achieve it rather than find good general methodology for a large class of Gs - [[lesson—when possible t get concrete example (or observations) then get them first before forming models or plans on vague ideas of h it might look like]] - 1 - don’t dive too deep into math if you don’t want to get really good understanding (-> either get shallow or very deep model, not half-deep) - 2 - [[lesson—take care not to get sidetracked by math]] - 3 - [[lesson—when writing an important message or making a presentation, imagine what the other person will likely think]] - 4 - [[lesson—read (problem statements) precisely]] - 5 - perhaps more often ask myself “Y do i blv W i blv?” (e.g. after rc W i think are good insights/plans) - 6 - sometimes imagine W keepers would want you to do - 7 - group - beware conceptual limitations you set yourself - sometimes imagine you were smarter - 8 - possible tht patts t add - if PG not clear → CPG - if G not clear → CG - if not sure h continue → P - if say sth abstract → TBW - if say sth general → E (example) - 9 - ,rc methodology i want t use (and Y) - Keltham methodology. - loop: pr → gather obs → carve into subprs → attack a subpr - 10 - reminder of insights: - hyp that any model i have needs t be able t be applied on examples (?) - disentangle habitual execution from model building (??) - don’t think too abstractly. see underlying structure to be able t carve reality better. don’t be blinded by words. TBW. - don’t ask e.g. W concepts are, but just look at observations and carve useful concepts anew. - form models of concrete cases and generalize later. - 11 - always do introspection/rationality-training and review practices. (except maybe in some sprints.) - 12 - Wr down questions towards the end of a session. Wr down questions after having formed some takeaway. (from Abram) - 13 - write out insights more in math (from Abram) - 14 - periodically write out my big picture of my research (from Abram) - 15 - Hoops. first clarify observations. note confusions. understand the problem. - 16 - have multiple hypotheses. including for plans as hypotheses of what’s the best course of action. - 17 - actually fucking backchain. W are your LT Gs. - 18 - 19 - 20 - 21 - 22 - 23 - 24 - 25 - 26 - 27 - 28 - 29 - 30 - read https://www.lesswrong.com/posts/f2NX4mNbB4esdinRs/towards_keeperhood-s-shortform?commentId=D66XSCkv6Sxwwyeep
As of a couple of days ago, I have a file where I save lessons from such review exercises for reviewing them periodically.
Some are in weekly review category and some in monthly review. Every day when I do my daily recall I now also check through the lessons in the corresponding weekday and monthday tag.
Here’s how my file currently looks like:
(I use some short codes for typing faster like “W=what”, “h=how”, “t=to”, “w=with” and maybe some more.)
I now want to always think of concrete examples where a lesson might become relevant in the next week/month, instead of just reading them.