I've been adapting ZK ideas to my work flow. I am in med devices working on CE mark regulatory filings, and so ZK kinda fits well with my job, which is essentially to find product/process information, know stuff, and communicate it.
I think ZK works very well in team environment. I make "issue logs" - when something goes wrong, or there is a particular detail to understand, I force myself to write out the issue and resolution into ZK. (Force, because it is so much easier to just solve and move on without documenting)
If you can maintain some discipline in writing summaries and updating for yourself, this solves "we discussed x issue 2 months ago, but don't remember {some, all} details now"
I keep sublime text open to my Kasten at all times so using full text search in a database of curated notes is so much quicker than trying to find the right project folder, or searching outlook.
I don't worry about one file - one idea, I just break things up how they make sense to me. The "rules" for ZK don't entirely make sense for engineering work and must be bent to your needs.
My only lament with plain text is difficulty in using figures / images in discussions with myself.
I think so. I’ve been using it to document 3 types of things for the projects.
1. Code guidelines, which anyone can contribute to and we can discuss/review them via PRs. As each note is a small rule or idea, it’s easy to reason about. It aids discovery for new team members, but early days to test that bit out.
2. Application implementation patterns. I’ve added small notes in the codebase to outline how concept work, state management, styling, types, etc. Relevant to the codebase, but not specific to any individual code file.
3. DevOps playbook. I’ve been working on this in the past week and having it in a Zettelkasten format has been very beneficial to fill it out with the most important aspects. The set of markdown files covers how to do deployment, how we do security, backups, etc. Would love to turn that into a blog/video series when I’m done - which probably shows the power of having knowledge that is very reusable.
I think ZK works very well in team environment. I make "issue logs" - when something goes wrong, or there is a particular detail to understand, I force myself to write out the issue and resolution into ZK. (Force, because it is so much easier to just solve and move on without documenting)
If you can maintain some discipline in writing summaries and updating for yourself, this solves "we discussed x issue 2 months ago, but don't remember {some, all} details now"
I keep sublime text open to my Kasten at all times so using full text search in a database of curated notes is so much quicker than trying to find the right project folder, or searching outlook.
I don't worry about one file - one idea, I just break things up how they make sense to me. The "rules" for ZK don't entirely make sense for engineering work and must be bent to your needs.
My only lament with plain text is difficulty in using figures / images in discussions with myself.