> If you have made it, document it, so you don't have to answer questions. Dont' communicate one-to-one, but always on an (internal) public medium, preferrably

> If you have made it, document it, so you don't have to answer questions. Dont' communicate one-to-one, but always on an (internal) public medium, preferrably more persistent than chat. - Need to explain something to someone? Write it a wiki and send them the link. - Have a great idea that needs brainstorming? Document it as a proposal and open a pullrequest to discus and have it merged into architecture documentation. - People asking questions about your code in a pullrequest? Don't explain in the PR why you did it, make your code and comments speak for itself so questions are not raised in the first place.