Re:How to build a second brain as a software developer
by akouri on Thursday November 11, 2021 @05:33PM
(#29194130)
I am constantly getting flummoxed by the PARA system. It ends up taking me more time trying to figure out the nuanced rules on where to put something (Projects/Areas and Areas/Resources are the most persnickety ones) that I often end up duplicating a concept and having two folders for it, one in each hierarchy. I'm still not sold on the PARA organizational method, but maybe there's something I'm missing.
[ Parent
| on HN ]
Re:How to build a second brain as a software developer
by greymalik on Thursday November 11, 2021 @06:46PM
(#29194748)
Project: has defined goals and an end date (“be able to run 5k in 30 minutes by April 1”)
Area: an ongoing personal or professional responsibility (My Health)
Resource: impersonal knowledge that may be useful (couch to 5k training program)
Archive: any of the above that are no longer relevant to your life
Re:How to build a second brain as a software developer
by Vivtek on Thursday November 11, 2021 @05:45PM
(#29194232)
I use a sloppy meld of Zettelkasten and PARA for this very reason. I used to get nervous about the subject ontology, and the link-to-anywhere aspect of ZK's tags fixed that for me. Plus having a unique ZK tag on every file means I can move subdirectories around to suit what I'm working on at the moment without any links breaking.
Re:How to build a second brain as a software developer
by JeffRosenberg on Thursday November 11, 2021 @06:24PM
(#29194554)
For me, implementing PARA in Notion has helped with that. I have one big database just called "Content", and then links to Projects/Areas/Resources. So if I'm not sure where something goes, I just put link it to all of them.