Re:How to build a second brain as a software developer
by cpb on Thursday November 11, 2021 @12:01PM
(#29190236)
The second brain is emerging out of this. I keep these notes as a sibling project to all the software projects I'm interacting with.
When shooting my shotgun for finding more references, what I've done/know/questioned about a piece of code shows up too.
For my own practices, I've added in a bit of an OODA loop process. My intent is to systematically balance between deciding and executing, focusing on accumulating knowledge towards achieving a goal.
When I'm stuck, or dealing with unknowns, the brainstorming in each of Observe, Orient and Decide enable me to gain some flow.
Later, I can observe where I had blindspots, or anchored to certain contexts or scopes. I'm noticing I could develop checklists to go through to avoid repeating those biases.