There are key advantages to having a private workspace for development. The biggest is that you can work in isolation from other changes around you. It is important to understand how the private workspace is used so that it is managed in the best way possible. With this in mind, it’s critical that the private workspace is used in the context of the project and that the forces influencing the project and programmer are understood. This is where the study of patterns and anti-patterns is valuable in constructing actual working processes that fit the working environment.
In particular, understanding the concepts of anti-patterns and how they can disrupt the adoption of good practice will lead to establishing practices that fit within a group. For example, if there is a very ambitious quality manager who thinks they can introduce CMMi Level 5 without first understanding the culture of the company in adopting such practices, the effort will be short lived. If the company has had poor results in even understanding a process and operates ad hoc (CMMi Level 1) and there is no reward system for adoption of CMM, then the forces currently in play within the organization will likely lead this effort to become low priority (or people will avoid them) and ultimately fail to take root.
Defining an Anti-pattern and Private Workspace
It is important to have a consistent definition of what is a private workspace and what is an anti-pattern.