Hi HN!,

Patryk here, creator of https://know.dev - knowledge base dedicated
for developers.

Motivation behind the project:

I was always interested in the topic of storing my personal dev-related knowledge like:

* ideas

* code snippets, cli commands, docker commands, etc. for easy/fast find and copy & paste

* tutorial/book notes

* dev theory

* solutions for installation problems with packages, gems, libraries etc. (which are related to my specific configuration)

* ... and other dev-related stuff which is nice to have easily categorized/tagged and fast to find

solution I wanted to use had to be fast in use, always available online and strictly dedicated for dev-related data (not cluttered with massive, not-related functionalities). I know there are many knowledge base related applications / wikis to setup and use - and many of them are general purpose with lot of stuff, some of them need to be self-hosted or configured on server/local computer.

The other important thing I have noticed in my developer career is: having possibility to test my knowledge before exam, meeting or interview - and I would like to use my personal knowledge base to do this.

So those things are part of daily developer's live - in general - operate on knowledge. I am also very curious about the fact how fleeting our memory is. I was always interested in topic: how other developers remember things and which things they remember: some of them are better in "dev theory", so talk really nicely about topics, patterns etc... but have not good memory to details, other devs are really good in remembering CLI commands, parts of code, some really specific details but can't nicely talk about theory. This is how human's brain works - remember things which are important for personality and other inner factors of the person: in general we can't remember everything. One developer need to store more theoretical data, other more know-how or specific parts of code they can use quickly in they work. In other words there are always things to remember but some kind of information does not stick with memory well but is needed in the work/project.

I was always unsatisfied with fact that I can't remember one solution which I learned and used some months ago. Often don't remember the flow or commands needed to fix the same error on my configured system which I had some months ago .... or unsatisfied about fact that don't remember CLI command with params shortcuts I was using some weeks ago: of course I can find this command in manual with all needed params - but time is counting 10 minutes, 20 minutes sometime 45 minutes or longer - use search engines, try and repeat sometimes.

Development world is BIG, REALLY BIG. Amount of knowledge is massive and we as developers have limited time and resources - it is not possible to put everything into our memory, so I build app to easily store and categorize the knowledge + refresh my memory using flashcards (before meeting, interview, exam). It is "search oriented" - so I can quickly type keywords or click category or tag. If I am preparing for interview or exam - I can use virtual flashcards made from my knowledge items.

One important thing to mention is limit category to one level and using tags. From my perspective as a developer it is good to have only one-level categories to limit myself (to not build trees of categories where I put my knowledge items) and it is faster to search, for example: if I want to store one CLI command to use with git, I can create category git and tag cli, so in the future I can easily type in search: git cli (what will list me all my knowledge items from this category and tag). Multi-category trees are hard to remember and search as it can be sometime hard to remember sub-categories names of each category etc.

There is also code syntax highlighting available under "CB" in editor - with most of the programming languages.
The other aim is to have it all in markdown (and markdown via WYSIWYG editor) as this is more "dev way" (for further share, copy & paste etc).

Knowledge items can be shared publicly like example here: https://know.dev/p/prKF2l , so you can share you knowledge item with somebody (I plan to add more share functionality, but at the moment there is possibility to do it via public link). But the idea is to have your personal, private, life-time knowledge base.

Personally I am using this app multiple-times daily to store or get knowledge or copy & paste snippets in CLI or write there my daily report for standups. I found it useful as a developer and would like to share with you.

Signup is fast can be via social account or short form (any account can be self-deleted from settings page, so do not hesitate to try it if you want).

Thank you for reading. I would love to hear any feedback from you, if you find it useful or not or have any idea related to it.