Taking notes during meetings isn't to improve understanding, or to "read" afterwards.
They're a record of what was discussed and decided, with any important facts that came up. They're a reference for when you can't remember, two weeks later, if the decision was A and B but not C, or A and C but not B.
Or when someone else delivers the wrong thing because they claim that's what the meeting decided on, and you can go back and find the notes that say otherwise.
I probably only need to find something in meeting notes later once out of every twenty meetings. But those times wind up being so critically important, it's why you take notes in the first place.
Still I think it's better to discuss "action points" in that case and give a clear owner to those points. This always helps me to understand who's accountable and what actions actually need follow up.
Notes do. Ideally there is a meeting owner who produces official notes and emails them to everyone, but frequently that never happens. And when it does happen, sometimes they're wrong and you need to correct them.
Which is why you need your own meeting notes. Plus, like I said, there are facts that come up that you want to document as well, that aren't part of the action items, but have value.
I think the person you're replying to is suggesting that the shared place for recording these things in a medium-large software department would be in project tracking software like Jira or Github Projects.
The kind of stuff stored in Jira is a very specific subcategory of all the types of things that get mentioned and decided in meetings. It doesn't cover all of it, not even close. And the person putting the information in might also get part of it wrong, that happens surprisingly frequently. It's not a substitute for personal meeting notes.
It also lets me ask questions like “When did we decide to change the login modal?” and get an accurate response.
Does anyone know if a plugin for this?
Like, a history buff could just tell the LLM "quiz me on the Taiping Rebellion, who what where when and why."
The LLM then enters this instruction into an API that handles the spaced repetition data and algorithms.
The LLM could pull that API daily and quiz you daily.
Actually knowing all this stuff sounds so much better than having a bunch of notes in a fancy graph.
For learning new material, make your LLM assume a Socratic position. Kagi Assistant has a custom Study model that does this. The key is causing the model to increase your friction (causing learning and memory) instead of decreasing it.
I suspect it would be less effective to learn similar-yet-slightly-different LLM-generated content generated every time you want to study.
When the LLM enters the "card" into the API it would define the required information, and then every time it would ensure you cover the required information. You could tell the LLM, "make sure I remember the date of this historical event", and then the LLM would ensure you mention the date when answering the card. If you get the date wrong, then it does the API equivalent of pressing "wrong / again" in Anki.
Yes, this is like listening a guided meditation in 2x speed because it is faster.
Isn't that pretty much the whole selling point of AI coding tools?
Where the value for me comes from is sending them out immediately after the meeting, not archiving them in a vault I never look at. "Here's the summary of what we discussed, and the distilled action items we each agreed to take."
Like the author, I've gone out of my way to avoid hosting my personal stuff with Big Tech providers, but when it comes to work, I give in to whatever we use, because I just don't have capacity to also be IT support for internal technology. It's still uncomfortable, but I have to be honest about what I have time for.
Honest question: Do you actually read any of these notes? I think there is a fundamental flaw with not taking notes. I'm convinced taking notes forces you to properly consider what is being said and you store the information in your brain better that way.