"Working software over comprehensive documentation"? Yeah, good luck debugging your undocumented code.
This seems to be something that causes a lot of confusion, and a lot of knee jerk dismissal of agile principles. "Working software over comprehensive documentation" isn't saying that documentation is unnecessary - just that it's better to expend effort on getting your software working than trying to document each and every aspect of the system. If it's important that users have strong passwords, it is far better to write the code to ensure that users have strong passwords than it is to spend your time deciding and documenting exactly what a strong password is. I've worked in companies in the past where a simple change like modifying the password policy would involve a couple of days of documentation, discussion and sign off. Often the code changes would take around half a day, maybe just a couple of hours, but we still had to go through the documentation and sign off no matter what. Agile is kicking against that, and saying that it's better to just get stuff done. Documentation is still important - coding is just more important.
... in the future of USA and the world, there are more STD's from your disgraceful behaviour now in your time then there ever was in 30 years ago
This is Slashdot. Around here, an STD should be worn like a medal. "Hey, guys, I've had sex, AND I can prove it!"
"The four building blocks of the universe are fire, water, gravel and vinyl." -- Dave Barry