91–100 of 304 posts
[1] https://tiomsu.com [2] https://www.youtube.com/watch?v=mx7Ai-PhvAM
For any system you build, keep in mind a few general truths: 1) The system isn’t just “the wiki” or “Notion”. The system is composed of both the tools you’re using AND the habits/expectations of the humans who use them. So, this is not just a matter of buying a tool. Its a matter of choosing tools AND designing a process made of humans habits. 2) The system will get messy and unused unless there is regular attention…
RuntimeException Map literal must contain an even number of forms clojure.lang.Util.runtimeException (Util.java:221)
The setup we use is a monolithic MS OneNote notebook stored on MS Sharepoint.
I know this setup is dependent on your shop buying the "expensive MS stuff", but we already had it anyway...
This setup gives us the following "features":
- Everyone can edit at the same time
- Changes are tracked and identifiable by username (you can rewind the file history)
- Editing process is very easy and user friendly (you can drag in files, images etc into your notes, and it just integrates seamlessly. particularly with the rest of the MS Office suite)
- OneNote notebook layout is actually pretty good (horizontal tab based main sections, that can each hold multiple pages of content. these pages can be visually organized in a hierarchy)
- It has good search functionality
Earlier quoted context omitted.
IMO you should disclose (and it is a disclosure, not a disclaimer) your employer at the top, because it makes the rest of your comment something nearer to marketing copy than user review.
I agree: this trick of saying that you are using Notion as a source of truth when you work at Notion had left a bitter aftertaste, on a product I should love overwise.
Cacher was built for the express purpose of team knowledge sharing via code snippets and Markdown docs. It has also been successfully scaled out to teams of dozens, with a few customers rolling out to hundreds of members.
We believe successful knowledge sharing comes down to several parts:
1) Organization via categorization. While retrieving knowledge, labels/tags are an important heuristic shortcut. We often have trouble remembering but details but can usually recall the purpose of the piece of knowledge.
2) Integration with existing tools. People hate changing their workflows. We've found that engineers who are used to coding in VSCode or IntelliJ would rather not leave their editor to retrieve snippets. The context switching is just too expensive. Cacher is integrated with major editors/IDEs for this reason.
3) The ability to keep other team members updated on progress and changes. A proper knowledge system uses notifications judiciously to keep everyone on the same page. Cacher does this via customizable desktop/email/Slack notifications.
4) A professional understanding of the knowledge workflow. It is important, regardless of which tool you adopt, to come to a consensus on how the knowledge will be used. Marketing and e-commerce teams use us to store HTML/CSS with the intent of creating a large library of components and patterns. Technical support teams create snippets for remembering how to update a user's billing account. Before settling on a tool, consider what kind of knowledge is important day-to-day and agree as a group on how you'd like to retrieve it.
I hope that helps! If you're team is looking to try it out and would like thoughts on how to set up an adoptable workflow, feel free to ping me: rui[at]cacher.io
Notion: https://notion.so [edit: I work at Notion. I’ve added some more color about that to the top here. This isn’t marketing spam I’m commenting from bed on my phone - sorry that it came off slimy] Notion is a malleable collaborative wiki that also has relational databases. We build Notion, so it figures that Notion is our single source of truth. I think the way we use Notion internally works pretty well - with bet…
Notion is great - the most important thing to my mind is that it's easy to find information later (by navigation, rather than search. The search UX is... not great). I use Notion to record everything that doesn't belong in git, but still needs a canonical place to live. >- Mobile performance could be better. This is the reason I still use Evernote on mobile, even though I pay for Notion. Sometimes I'll even bend Trel…
Notion: https://notion.so [edit: I work at Notion. I’ve added some more color about that to the top here. This isn’t marketing spam I’m commenting from bed on my phone - sorry that it came off slimy] Notion is a malleable collaborative wiki that also has relational databases. We build Notion, so it figures that Notion is our single source of truth. I think the way we use Notion internally works pretty well - with bet…
IMO you should disclose (and it is a disclosure, not a disclaimer) your employer at the top, because it makes the rest of your comment something nearer to marketing copy than user review.
Spaced repetition [0] systems like Anki are usually used to study technical subjects or languages, but one of my "decks" is titled "my truths" and it contains insights I want to internalize. Repeated exposure is absolutely central actually making an idea part of yourself and acting accordingly. So instead of maintaining a large knowledge database, I'd recommend sticking to solid principles and reviewing them on a reg…
I tried to start with Anki, but didn't really figure out how. If you have a "truth" you want to remember, do you need to split it up into some sort of question / answer format to put on the front and back sides of a card? I am already scoring well on the "annoying my team with repetitive statements in discussions" front.
TiddlyWiki: https://tiddlywiki.com/