## Notes - If the intent is still the same and the ideas are still in the document, having to refactor into atomic notes is more tedious and prevents you from just doing the work - Despite being finished still working inside because he is working under same goal - Mini essays are constrained by a niche topic, which can lead to english-style BS to fill the requirements - focus should be on just revisiting ideas to refine - supports jargon - this is the practice part of [[Ecological Dynamics]] - Feynman technique fails to account for repetition without repetition since it's purely just to a "simple" audience - Content creation is attempt to further understand, it is not an end. - prevented by atomic essay principles: - one idea - word count - simplicity - You don't need atomic notes on things that aren't reusable, reminds me of [[DRY programming principles]] and knowing when to refactor code - In terms of his workflow, his projects-based workflow in relation to mine is split into brainstorms and goals - [[Brainstorms]] where there are no such atomic rules, focus is on the topic. his topics are to develop understanding - [[Projects]] are similar but the intent is to have that context-specific information that is not relevant, and also be better accomodated in my periodic reviews - All related conceptual notes should be acknowledged during periodic reviews by attaching it to a specific project or just by **reviewing brainstorms as a whole** - The counter to atomic notes is sure information is organized, but what about the actual application of ideas? Under the assumption that application is more effective at testing and developing understanding - [[USV and Personal Knowledge Management#Productivity]] - A more knowledge-oriented approach to the underlying goal of the PARA method rather than actionable? - Lol brilliant learning style is actually relevant to ecological psychology