Worried that TDD will slow down your programmers? Don't. They probably need slowing down.

Non-local variables are simply implicit parameters to every block of code in your entire system. So limit them.

Photo: A model for improving the names of variables, fields, interfaces, classes and namespaces in a system http://tumblr.com/x3k30dct93

When your company starts going agile, you will appear to slow down; this happens because you were going too fast.

int main(int argc, char** argv) { printf("Goodbye, Dennis.\n"); return 0; }

@kentbeck Developing intuition about design:  http://link.jbrains.ca/gmeMhh 

Writing more precise specifications is neither sufficient, nor necessary, to get the software you need. Feedback is necessary.

In job descriptions, substitute "We need an expert in X" with "We have many idiots doing X; we expect you to compensate for that." #protip

Everyone can stop now. I've declared a winner. Maximum WTF density in a single tweet about programming:  http://link.jbrains.ca/11Ywlqv 

I'm sick of fucking amateurs writing software. Get your heads out of your fucking asses and do some testing.

The World's Best Intro to TDD (demo video) -  http://link.jbrains.ca/13lwRjb 

"Please... GREATLY reduce the number of unit tests." The Daily WTF http://bit.ly/hrUFfx

TDD is a technique for driving bad habits out of programmers.

Instead, sell TDD as a way to maintain a steady, predictable flow of features. Add BDD to make those smallest, better features.

You're a programmer. Maybe you haven't read this. Read it; it's quick.  http://c2.com/ppr/checks.html 

To all frustrated mentors of programmers: it took me 1,000 hours of practice to go from test-first to even a little test-driven.

Top 10 Things Which Make Your Code Hard to Test: http://t.co/YHD86AGU

Universal "definition of done": can anyone in this room think of anything more to do on this story? Yes? Not done.

A good overview of current thinking on the value of software project estimates. http://t.co/YqKC9VuA /via @duarte_vasco 

For example: BDD without talking in examples with the customer is essentially automated testing in COBOL.