[Jugurtha]

I use TaskWarrior[0]. Low friction..

  task add +read "Book title. Mentioned in interview [link for the resource] by X with Y. Useful because [reasons].

Then I annotate the task

  task 180 annotate (triple quotes)(multi line thoughts)(triple quotes)(return)

I also add notes there. I also used markdown files and MKDocs [old link: https://jhadjar.gitlab.io/kbase/]

This stuff served as the seed of our knowledge base where I work.

- [0]: https://taskwarrior.org/

[sarvagyavaish]

Wow! That is some dedication to building a 2nd brain :)

I am doing some market research on folks that go above and beyond to take notes to document their learnings while podcasting. I would love to talk to you for 20 mins and ask you a few questions. As a thank you, i'd like to buy you a coffee (via paypal / venmo). Let me know if i can reach out to you.

[Jugurtha]

Here are some of my replies:

- https://news.ycombinator.com/item?id=19924100 (understanding codebases, etc.)

- https://news.ycombinator.com/item?id=22873103 (making the most out of meetings, leveraging your presence)

- https://news.ycombinator.com/item?id=22827841 (product development)

- https://news.ycombinator.com/item?id=20356222 (giving a damn)

- https://news.ycombinator.com/item?id=25008223 (If I disappear, what will happen)

- https://news.ycombinator.com/item?id=24972611 (about consulting and clients, but you can abstract that as "stakeholders", and understanding the problem your "client", who can be your manager, has.)

- https://news.ycombinator.com/item?id=24209518 (on taking notes. When you're told something, or receive a remark, make sure to make a note and learn from it whether it's a mistake, or a colleague showing you something useful, or a task you must accomplish.. don't be told things twice or worse. Be on the ball and reliable).

- https://news.ycombinator.com/item?id=24503365 (product, architecture, and impact on the team)

- https://news.ycombinator.com/item?id=22860716 (onboarding new hires to a codebase, what if it were you, improve code)

- https://news.ycombinator.com/item?id=22710623 (being efficient learning from video, hacks. Subsequent reply: https://news.ycombinator.com/item?id=22723586)

- https://news.ycombinator.com/item?id=21598632 (communication with the team, and subsequent reply: https://news.ycombinator.com/item?id=21614372)

- https://news.ycombinator.com/item?id=21427886 (template for taking minutes of meetings to dispatch to the team. Notes are in GitHub/GitLab so the team can access them, especially if they haven't attended).

- https://news.ycombinator.com/item?id=24177646 (communication, alignment)

- https://news.ycombinator.com/item?id=21808439 (useful things for the team and product that add leverage)

- https://news.ycombinator.com/item?id=20323660 (more meeting notes. Reply to a person who had trouble talking in corporate meetings)

- https://news.ycombinator.com/item?id=22715971 (management involvement as a spectrum)

- https://news.ycombinator.com/item?id=25922120 (researching topics)

- https://news.ycombinator.com/item?id=26147502 (keeping up with a firehose of information)

- https://news.ycombinator.com/item?id=26123017 (fractal communication: communication that can penetrate several layers of management and be relevant to people with different profiles and skillsets)

- https://news.ycombinator.com/item?id=26179539 (remote work, use existing tooling and build our own. Jitsi videos, record everything, give access to everyone so they can reference them and go back to them, meetings once a week or two weeks to align)

Some of them may be more relevant to you, such as the one "keeping up with a firehose of information", and the ones dealing with taking notes, alignment, communication, etc.

I don't really do "podcasts", but I use these strategies when I collect papers (or watch technical talks), cherry pick the relevant ones, read them, summarize them, and then send the notes to my colleagues.