Squeak, source control, subversion, versioning, monticello,
all that good stuff.
Peter at ozzard.org
Mon Jan 30 19:09:23 UTC 2006
> From: [...] Simon Kirk
> The only other need for a strict branching discipline is maverick
> developers who have a habit of refactoring large swathes of shared
> library code in the main codebase that impact other people, live
> deployments, testing, etc. How would you suggest stopping people from
> being able to do this sort of thing?
First offence: Being beaten over the head ritually with the procedures
manual, in which it is said that You Don't Do That.
Second offence: Being transferred to an XP team, where such behaviour is
Third offence (if they manage to alienate the XP people): Dynamite. Or
being assigned Wally (from Dilbert) as a pair programmer.
More seriously... there's not really a technical way of preventing this.
Human approaches are required, which can (should?) include removing the
maverick from the project, and possibly the company. Seems harsh, but
I've seen such a person wreck a project.
More information about the Squeak-dev