Live data from Hacker News

How to build a second brain as a software developer

aseemthakar.com

11–20 of 177 posts

Re: How to build a second brain as a software developer

#11
I've tried to incorporate some of the ideas of the "second brain" and it didn't really give me that much. My lessons:

1. It's always super helpful to write things down. Taking notes from what I read/learn is a great way to verify that I understand it. It sharpens my thinking.

2. However, maintaining the "second brain" is a lot work. It's not only about "linking" together notes. You also need to maintain some consistency between them. I ended up spending a lot of time thinking about the structure instead of actually thinking about the content.

3. Most of my notes/thoughts fall into two categories: (1) Either they are critical for something I'm actively working on or (2) it's just loose concepts that I'm toying with. For (1) I immediately end up playing with it in code — which is far more concrete and tangible than notes. And for (2) it was rarely important to retain the knowledge accurately many weeks/months later.

What I've ended up with is taking a lot of notes, but I hardly focus on organizing them.

Re: How to build a second brain as a software developer

#12
post #3

Pretty graphs, but I wonder how it stands up to the tests of the real world. I've personally tried to use mind maps (a bit more general than solving technical problems) but gave up pretty quickly. I think part of the problem was the technology itself, mind map apps are mostly desktop only and the mobile experience navigating a 2D diagram is kind of clunky. The other part was just laziness, after building a mind map f…

Mobile is a challenge for all these PKM systems, esp capture but also retrieval. Luckily most knowledge work is still done with a big screen.

Re: How to build a second brain as a software developer

#13
post #3

Pretty graphs, but I wonder how it stands up to the tests of the real world. I've personally tried to use mind maps (a bit more general than solving technical problems) but gave up pretty quickly. I think part of the problem was the technology itself, mind map apps are mostly desktop only and the mobile experience navigating a 2D diagram is kind of clunky. The other part was just laziness, after building a mind map f…

Writing as someone who uses mind maps as part of my kit, I empathize with your comment. For my purposes, I've found that it helps to focus the map around a specific objective, project, etc. If I'm preparing a paper or presentation, it's helpful to see how the content can be structured, what can be pruned and what relationships between concepts there are. For project work or other objectives, I find them to be helpful in tracking and guiding learning.

FWIW, I use iThoughts across a couple of different devices. It's been around for a while now and has a good mix of usability and functionality.

Re: How to build a second brain as a software developer

#16
All the tools you mentioned are nice.

However, none are built for software developers. If you want to know why, ask yourself — does anything here make me feel special as a developer? My guess is the response is "No".

I'm the founder of archbee.io, and although it's an early stage product, I built it for engineers — and you can see that by the features: architecture diagrams, GitHub integration, markdown shortcuts, very speedy, API docs with GraphQL and OpenAPI, custom domain hosting, Mermaid diagrams and more.

Please check it out and let me know what you thought!

:)

Re: How to build a second brain as a software developer

#17

My second brain is the 400 browser tabs that I have open

You might have meant this as a joke, but I honestly think this is a better way of doing things than a rigourously designed system of organisation and workflows and all that.

There are a million ways to approach this kind of thing, and whilst browser tabs aren't nessecarily the best way, they're certainly up there

Re: How to build a second brain as a software developer

#18
I still believe that all those "second brain" solutions lack an essential feature: spaced repetition, which I built my solution[] around.

Spaced repetition is a way to automate the reviewing schedule of the notes you took, which is essential if you want your knowledge to linger. It allows you to iterate and improve notes on the topics you probably know better now than when you wrote them.

https://rekowl.com

Post reply on HN