Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

This question was prompted by a comment left on another question pointing to this article.

What Is Clean Code?

I was thinking about how that sentiment can be applied to shared resources (servers, etc).

What are some of the ways you've found that work to ensure that when others use a shared server they clean up after themselves?

  • Delete files / folders after one time use (after a fix or upgrade)
  • Leave the desktop clean of crap
  • Don't install software that they can use on their desktop
  • Don't create filesystem shares not needed for the solution

Yes, this applies mostly to a windows server environment, in a team of developers + support staff of about 25.

I know there are a few ways to tackle the problem, so what have you found that works?

share|improve this question
up vote 2 down vote accepted

The problem is very similar to "dirty toilet" problem. The classic approach is a shield "please leave the cabin in a condition in which you would like to find it" (forgive me my poor English).

Combining this with a simple monitoring/mailing scripts should work fairly well.

share|improve this answer
Thanks, I like the idea of the monitoring scripts. Setup a set of "allowed" folders/files and then alert after 24 hours (or so) for stuff outside that. :) – Thomas James Oct 26 '10 at 21:22

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.