I will say that my favorite new methodology can be found here: http://programming-motherfucker.com/
You will not ship complex business software by just "Programming, motherfucker". You will build the wrong thing if you talk to the customer for one hour and then go off on a mad programming frenzy for the next 6 months. You need constant iteration and feedback (agile), or completely up front agreed-upon specs (waterfall), to not build the wrong thing. Both of these are absolutely not programming.
Next to that:
> "We are tired of being told we're socialy awkward idiots who need to be manipulated to work in a Forced Pair Programming chain gang without any time to be creative because none of the 10 managers on the project can do... Programming, Motherfucker."
This seems very stereotyping. Does anyone actually experience this? In this job market? The companies I've worked at are generally very happy to have a software engineering professional in the team, and are trusting of my word/estimations.
If someone would call me a "socially awkward idiot" at work, I'd have no problem finding another workplace that does respect me.
> This seems very stereotyping. Does anyone actually experience this? In this job market?
While not directly spoken to engineers' faces, there are absolutely people who think this way. And I know former coworkers who have worked in pair programming shops, so that part is actually factual. Innocence is bliss, though (;