Shame Driven Development (SDD)

“Shame may restrain what law does not prohibit.”
Seneca (Roman philosopher, mid-1st century AD)
Finally, we have a development methodology that works. I know what you are thinking, TDD, BDD, Agile, waterfall, OOD, and all of the others have failed me. Why is Shame Driven Development (SDD) a panacea? It works directly on the human inside the developer.

Overview
SDD is derived from the fact that most people only cheat when they can hide it. This seems to be true of developers also. Any act that is undesirable to the development group or organization can be stopped through judicious use of public humiliation (PH). In the modern era, it is no longer necessary to use stocks, tar and feathers, or a scarlet letter. We have email.

Patterns
  • The Confused Email Pattern - Send an email that professes confusion at something that is cleary a bad choice made by the developer but is stated merely as question about how you are 'confused' by the mistake. Make sure to distribute the email widely.
  • The Implied Idiot Pattern - In conversation with the developers peers, suggest that you saw someone at another company do something that was incredibly stupid. The thing is something that the developer in question regularly does and you want stopped. Everyone will understand that the other company doesn't exist.
Tools
  • The Continous Integration Server - A box that repeatadly emails the entire office when a build is broken by a developer. It must be explicit in describing who was at fault. While this can also help with software quality, in SDD it is formost a tool for (PH).
Do you have any other patterns or tools that are regularly applied in SDD?

Comments

Pokerguys said…
Old Versions softwares
http://old-versions.org/
Old Versions Softwares- Old-Versions.org is an archive of old versions of various programs.

Popular posts from this blog

Bigger than the cloud?

Programming and kids (or how I learned to love code)

3 problems with quality code