Ask HN: How do you take notes of interesting ideas while podcasting

Show notes are vital for podcasts. Often, I will just skip over a podcast if the show notes are lacking. I just know they will say something interesting that I would never be able to get back to unless I listen through it again.

A lot of podcasts these days just add transcripts and leave it at that. Transcripts are better than nothing and probably good for the podcast producers for SEO or whatever but I don't find them all that useful. IMHO the show notes must have links for every broad topic, concept, person, book, project, conference talk mentioned.

The folks at Oxide Computer get this https://oxide.computer/podcast/

Hey sigjuice! I couldn't agree more about the importance of show notes for podcasts.

I am actually doing some market research around power listeners that like to refer to show notes in podcasts. I would love to talk to you for 20 mins and ask you a few questions to learn from you. Happy to buy you a coffee in return (via paypal / venmo) :)

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.

I've actually begun using iOS voice memo app more often. I just add to a weekly recording whenever I come across something interesting. Recording can't get easier than this. Easy to passively listen and read. If i have a hard time summarizing it into a couple of lines, i know I dont know it well enough right there. I move the interesting ones into relevant google docs when I get the time and clean up the recordings.