KCS is important. It helps to organize the knowledge and makes it easy to share. But what’s more important is to think about what to capture and how to do it.

It helps you to avoid naming an article like this:

1. How to install [product name] with concrete components via command-line interface?
   – And build a house via SSH!
2. If auto-responder is switched on until September 13th, will it be switched off at that date?
   – You forgot to mention it’s also Friday. You don’t wanna be less accurate.

…Or providing contradicting info in it:

• Q: Is it possible to use Git extension with the remote repository?
  A: It is not possible, as it is not supported yet. [Here is a link that tells otherwise.]

Type: KCS
Score: Bad
Reason: The captured knowledge has to provide a value and some sort of elegance.