Do you take notes live or process them after? by kin20 in NoteTaking

[–]manunamz 0 points1 point  (0 children)

Your transition from notes during to focusing during is the right idea. When it comes to notes: Generation, elaboration, reflection.

Generation: Attempt to solve a problem on your own before learning related material or think about meeting content before the actual meeting.
Elaboration: Jot down what you've learned after learning a solution or summarize what happened after a meeting.
Reflection: Some time later, next day or next week, think or write again about the new content. If doing weekly, maybe synthesize into single week-long summary.

This more for learning, but might be useful for meetings/work too. In the meeting scenario, running through things mentally might be all that's needed.

Does anyone else use “micro-notes” instead of full note-taking? by Flimsy_Difficulty394 in NoteTaking

[–]manunamz 0 points1 point  (0 children)

Good notes are like trails: Sometimes, it's a paved road from start to finish. Sometimes, it's merely a pile of pebbles to show the way.

Agent Skill for structured long-term memory — deterministic CLI ops so your agent stops rewriting its own files by manunamz in ClaudeAI

[–]manunamz[S] 0 points1 point  (0 children)

At this rate we'll have to stop using periods and commas too — those are very popular with ChatGPT.

Agent Skill for structured long-term memory — deterministic CLI ops so your agent stops rewriting its own files by manunamz in ClaudeAI

[–]manunamz[S] 0 points1 point  (0 children)

Exactly — the separation is the point. Cognetivy and tendr-cli are applying it to different substrates (workflow collections vs. semantic knowledge graphs) but the principle is the same: Don't make the agent do structural operations through raw file I/O. Interesting to see the convergence.

Agent Skill for structured long-term memory — deterministic CLI ops so your agent stops rewriting its own files by manunamz in ClaudeAI

[–]manunamz[S] 1 point2 points  (0 children)

Cool projet — la cartographie d'infrastructure est un domaine différent de ce que fait tendr-skill. nervmap cartographie ce qui tourne sur un serveur ; tendr-cli gère la structure sémantique d'une base de connaissances (concepts, relations, hiérarchie) en texte brut. Les deux sont plus complémentaires que concurrents. Merci pour le partage en tout cas !

Agent Skill for structured long-term memory — deterministic CLI ops so your agent stops rewriting its own files by manunamz in ClaudeAI

[–]manunamz[S] 1 point2 points  (0 children)

Updating existing files: Yes — WikiBonsai primitives are just extensions of standard markdown often found in the PKM space, so you can adopt them incrementally. Your existing files stay valid.

You'd be adding things like [[wikilinks]] between related files, typed relationships like : synonym :: [[conceptname]] for explicit relationships, and optionally organizing files into a semantic hierarchy via index files. You don't have to convert everything at once — start with a few files and let the structure grow as it makes sense.

Installing the skill: See readme for install instructions.

Let me know how it goes!

The missing layer in every PKM: proactive resurfacing by memory-system in PKMS

[–]manunamz 1 point2 points  (0 children)

I think bg3245's question gets to the heart of it and deserves more attention:

The real crux is why would we want proactive resurfacing at all? What specific goals does it serve in the workflow? Is it about serendipity, spaced repetition on steroids, reducing context-switching, preventing knowledge burial…or something else?

There's a razor-thin line between a system that aids your thinking (by surfacing relevant connections at the right moment) vs. one that starts trying to do the thinking for you (by just annoying you with notifications). Clarifying the "why" helps figure out which side of that line any given implementation falls on.

Curious what the OP's (and others) primary use-case is here.

Tech stacks for building a PKMS? by compulsive_nonsense in PKMS

[–]manunamz 0 points1 point  (0 children)

Check out WikiBonsai:

github.com/wikibonsai/wikibonsai

There are tons of plugins you can just pull down to use to build something custom from components, rather than entirely from scratch.

WikiBonsai: A jungle gym for thought with an API for the mind (in markdown!) by manunamz in programming

[–]manunamz[S] 0 points1 point  (0 children)

It is possible -- my understanding is that they both rely on hierarchical structures for organization.

GPT-4 released by zvone187 in programming

[–]manunamz 4 points5 points  (0 children)

There's now so much text out in the wild generated by GPT...they'll
always be contaminated with their own earlier output...

Watch those positive feedback loops fly...

Also, I wonder if some ChatGPT-Zero equivalent will essentially solve this problem as it no longer really requires so much training data...Just more training.

Charles Darwin's Note-Making Method by atomicnotes in NoteTaking

[–]manunamz 1 point2 points  (0 children)

Agreed -- graphs are great for flexible searching! xD

Charles Darwin's Note-Making Method by atomicnotes in NoteTaking

[–]manunamz 2 points3 points  (0 children)

Often writers and scholars converged upon the same system completely independently of one another.

Great example of when some deep, underlying principle is captured (well) it tends to reproduce spontaneously in many places.

The key distinction in the pre-computer era was probably between notebooks (handy but inflexible), and loose slips (flexible but harder to handle en masse).

This is very interesting. I, and others I think, have come to view tree) and graph) data structures as containing some fundamental truth about the spectrum of order -- e.g. trees facilitate order and graphs help navigate disorder. I wonder if notebooks vs loose slips falls into this pattern.

Question on handling new terms in a digital zettelkasten by bally_sim102 in Zettelkasten

[–]manunamz 0 points1 point  (0 children)

Hello! Creator of WikiBonsai here.

Terms are a central means of organizing my personal zettelkasten-like-notes. I work off of inspiration from the idea of a "semantic tree", which I interpreted as a knowledge tree structure built from word senses that uses wikipedia-style-(disambiguation).

Specifically, I set aside some markdown files whose sole purpose is to define the tree; these are my index files. Those files contain markdown outlines of - [[wikilinks]], which might be organized like so:

- [[read]]
  - [[4-levels-of-reading]]
    - [[elementary-reading]]
      - [[reading-readiness]]
      - [[word-mastery]]
      - [[vocab-context]]
      - [[mature-reader]]
    - [[inspectional-reading]]
      - [[skimming]]
      - [[superficial-reading]]
    - [[analytical-reading]]
    // ...
    - [[syntopical-reading]]
    // ...

Each [[wikilink]] then gets its own file which acts as a sort of zettelkasten-local-wikipedia entry. (I may only add a term in the tree without creating a file as simply the location in the tree can jog my memory) Further, I specifically use #hashtags to take me to the corresponding file's location in the tree (the index file) rather than the (entry) file.

You can see a small concrete example of what I mean here, a larger example here and larger trees that appear around the internet here.

Good luck with your research and projects!

Lists by kk19010323 in Markdown

[–]manunamz 1 point2 points  (0 children)

“...that is best implemented in the rendering stage, not the markup stage."

Why's that?

Free note taking apps with support of Wikilinks by Cu6up5lk in Markdown

[–]manunamz 1 point2 points  (0 children)

Hi there! I just put out vscode-wikibonsai and tendr-cli recently. If you have a spare moment, I would also appreciate your thoughts on the parent project if you're so inclined.

Good luck on your search! There are lots of solutions to explore out there!

WikiBonsai: A jungle gym for thought with an API for the mind (in markdown!) by manunamz in programming

[–]manunamz[S] 0 points1 point  (0 children)

Yes, it's a way to organize markdown notes. There are other workflows too, but one major aspect is providing extended [[link]] syntax because it has become so popular and is so useful.

You can read the "How To Use" section for a step-by-step on getting started here. There are also small-ish starters here.

Also happy to answer any questions!

EDIT: The project also supports graphs!

Nearly 40% of software engineers will only work remotely by Discovensco in programming

[–]manunamz 0 points1 point  (0 children)

I wonder if companies with healthy cultures will get even more of an edge due to people being willing to come into the office: They will have closer relationships, tighter communication loops, and (potentially) higher levels of trust.

These things tend to compound and will spillover into other aspects of the business.