Reading the summary, it's clear the problem is that people are confusing what it means to take an iterative approach to development.

Production code is production code, and they should never have stopped shipping production code. The amount of scrutiny/rigor applied to code shipped in an agile environment should not decrease vs. waterfall. You're just shipping smaller chunks a lot more frequently.

All this means test, test, test, the entire time.

Thanks for letting us know you watched An Inconvenient Truth.

Tolkein? Is that you?

Whups, lol, year fail.

I hear this fallacy a lot.

When I work from home, I'm still pairing up with another developer over skype/tmux, and I am super productive doing it.

It's 2012, there's no reason remote working should incur a penalty in collaboration.

Why does everyone wonder why locally produced food costs so much, instead of wondering why the over processed megacorp garbage is so cheap?

Pointers are pretty essential to a kernel.

Does that quote imply Doug Stanhope believes in God and free will?

When the smartcard is given a public/private key pair, it registers the public key with a basic centralized keystore. Then the ssh server starts refusing key authentication with any client not trying to authenticate against one of the public keys generated by the smartcard setup process.

Due to my moderation threshold missing the comment you were replying to, I had assumed that you were one of those fundie-athiests bringing up religion out of nowhere just to let everyone know how stupid you thought religion was.

But then I read the comment you were replying to and then yours made total sense.

Carry on.

So you assume the bad guys have a first name of Mohammed? :)

So what you're really saying is something more like, "you know, I've met Muslims that weren't terrorists, but at the same time, it seems like all terrorists who want to destroy the US happen to be Muslim."

I don't buy this "the world needs people like RMS" B.S.

Either his ideas are correct, in which case we should adopt them, or they aren't, in which case we shouldn't.

Most methodologies work well in a "development team where everyone is technically solid and works well with others."

Regular 2-4 week iterations, mandatory automated testing, replacing boring waterfall meetings with short 10 minute scrums, and keeping the stakeholders involved at all times are things that every solid developer should welcome.

That's about as far in to "Capital A" Agile I've ever cared to go. Any more than that and we're too focused on process, IMO.

"All religion is toxic and all defense of it merits relentless attack."

Wow, dude. Good luck with that jihad of yours.