Hey Petr, haven’t you learned anything recently?
Well, of course I have! But I found a more convenient place for me to write about it: a GitHub repository.
When I encounter some problem that takes time to figure out and after solving it I feel like I may need that answer one day again, I write it down.
It’s something I learned in my previous jobs. That GitHub repository is actually only the latest of the knowledge bases I’ve created (and the only one publicly available). In my two previous jobs I was working on systems that both already existed for some time and there was a lot to learn. Some problems and questions came up again and again so instead of relying on my memory I started to write things down.
Yes, most of it should be part of a documentation, but is it?
Start simple. If you have a wiki, create a page there, if you use GitHub, there is a wiki already. The key requirement is that is has to be really easy to edit. And the second most important thing: it should be easy to search through. If you publish it online, you can link to it and share it with your colleagues. I would suggest you not to think too much about a structure. It will naturally happen as the knowledge base grows.30. 7. 2017, kategorie: