Thank you for sharing!

I don’t personally use Zettelkasten but I can see how it benefits from the visualization — the system itself is basically building a graph (cards are nodes and links are edges), it makes sense to have a tool that lets you work with it visually.

It’s a neat demo.

Can you give a more specific example of what you have found in this data? I already know what KB contains and how it evolved — I was the one who put things into it, after all.

Just to clarify — I am not being snarky or criticizing your project, I am genuinely curious. I like data visualization.

P.s. Also, as an unrelated tangent, please feel free to ignore it — why did you put a hypothetical wife’s insights into quotation marks?

By the time a non-tech user reaches the point of seeing an error they are cognitively overloaded and since the errors are pretty much incomprehensible to the users, the user doesn’t get the feeling of it being anything that’s tied to their actions. It’s just anxiety-inducing noise, it never registers as something that has a meaning, so even copying and pasting an error feels like a meaningless step that their overloaded and already anxious brains skip.

If errors are meant to be shared with tech support, the UX should reflect that (and some interfaces do that where you just have a button to send the crash report or smth). If errors are meant to give users agency to solve the problem on their own, the UX should reflect that too.

I'd say this would be a perfect time to introduce or update your project's contribution guide.

You can develop your own rules or use some existing spec to standardize commit messages such as Conventional Commits: https://www.conventionalcommits.org/en/v1.0.0/

Comments URL: https://news.ycombinator.com/item?id=40789796

Points: 26

# Comments: 2