Looking around at the blogosphere, OSS repos and conferences, it might be easy to assume that test-driven development is all about frameworks — unit-testing frameworks, mocking frameworks and frameworks for dealing with frameworks.

Most frameworks evolve as responses to other frameworks, which means they are often anchored (or stuck) in a particular point of view. And often that point of view is fairly narrow and, somewhere along the line, influenced by JUnit. What makes TDD effective is focus, clear progress and expression of intent; frameworks do not typically change what is possible, simply what is convenient.

This talk reconnects with the essentials by taking a lo-fi approach to framework usage.

Additional Resources

About the Speaker(s)

I'm an independent consultant, speaker, writer and trainer. My software development interests are in patterns, programming, practice and process. I've been a columnist for various magazines and web sites. I'm co-author of A Pattern Language for Distributed Computing and On Patterns and Pattern Languages, two volumes in the Pattern-Oriented Software Architecture series, and editor of 97 Things Every Programmer Should Know.