If you hear “eXtreme Programing”, it's voodoo. One of its premise is “pair-programing”, meaning, 2 programers get together, then you code while i suck you, then i code while you suck me.
XP was the rage around 2001, with tens of books written on the subject. But it has subsided, and mutated to perhaps a milder form called Agile Programing. When XP was hot, in the same time is the “design patterns” movement. Then, it bursted into a hoard of “anti-patterns”.
What these voodoo encourage is less brain, less knowledge, less responsibility, less creativity. Instead, it emphasize collaboration, good attitude, follow the template, kiss the management.
In particular, it's loved by managers who can't write a line of code.
One characteristics of these voodoo is lots jargons and use of fancy diagrams.
What “methodology” should you use? Understand mathematics, be knowledgeable, be healthy, and good general education such as history, philosophy, literature, and, be a nice person.Disqus