Team hive mind

I'm always surprised how many developers don't got the habit of using company wiki. Wiki is a must-have for any development team that wants to be productive in the long run.

• If you don't share the details of your system's architecture on the wiki, how can you expect your team to understand the application they are working on?
• If you don't share the description of your development process, how can you expect your team to follow it?
• If you don't describe your coding practices and standards on shared wiki page, how can you expect your team to apply them?
• If you don't document the results of the research that took you a week, how can you expect your team not to loose another week on reinventing the wheel?
• If you don't share your knowledge and keep it in a single place, how can you even think about leaving the company for a week of a holiday?

Whenever somebody within your team asks you a project-related question, ask yourself why this information is not documented in the wiki in the first place.