Introducing the WACD Methodology

Pronounced 'whacked', WACD is short for:

• W - Wild
• A - Ass
• C - Cowboy
• D - Development

Key WACD Tenets

• Use IDD (Instinct Driven Development). After all, you’re the one who has to build it.
• Always code alone. Other opinions rarely help, so, in the end, they just slow you down.
• Always don’t test. You know what you're doing. Like opinions, this is just more drag.
• Document when asked but never again. You’re not a writer. Who’s going to read it anyway?
• Keep information to yourself. Anything else just risks you losing your job.
• CM with zip. You're stuff is archived. You know where it is – that’s all that really matters.

Benefits of a WACD Team

• Overdue projects
• Low levels of usability
• Lots of application bugs
• Costly O&M
• High staff turnover

Comments

[FredO]

Wow! All these years I thought I was just struggling with mismanagment and chaos.

You have distilled a well defined methodology from the craziness. Well done!

Now when I am consulting, I can say, "Hmmmm... there seems to be a methodology to your madness!"

[Justin Carmony]

This is a great, to the point, explanation! I hope this definition becomes common terminology among developers. Its an easy way to say "my development job is insane" in a simple acronym. :)

[Ben]

No kidding! I run across more WACD stuff everyday. Will probably extend this little anti-pattern parody again, soon.