Agile in a Flash

Tim Ottinger & Jeff Langr present the blog behind the versatile
Pragmatic Programmers reference cards.

Feel Like You've PARTIED With Mobbing

›
A new AIAF post by Tim Ottinger / Jeff Langr. Mob programming sounds like a chaotic way of developing software: Get everyone into a room wi...

Why Test-After Coverage Is Lower

›
Unit testing after the fact? We do just enough test-after development (TAD) to please our manager, and no more. Just Ship It!  Onc...

Top Ten Agile Dangers

›

Interview with Tim

›
Tim had a nice mini-interview  with Michael Hall of  UGTastic , who is also (as far as I'm concerned) the public face of the Software Cr...

Continuous Improvement In A Flash

›
Jeff and I have been busy working independently. I borrowed the "brand" but Continuous Improvement In A Flash is a whole differ...

Premature Passes: Why You Might Be Getting Green on Red

›
Red, green, refactor.  The first step in the test-driven development (TDD) cycle is to ensure that your newly-written test fails before ...

Simplify Design With Zero, One, Many

›
Programmers have to consider cardinality in data. For instance, a simple mailing list program may need to deal with people having multipl...

The "Flash a Friend" Contest: A Covert Agile Give-Away!

›
If you're reading this blog, you're probably a believer that a good agile process can make a difference. And maybe you've recogn...
2 comments:

Seven Steps to Great Unit Test Names

›
You can find many good blog posts on what to name your tests . We present instead an appropriate strategy for when and how to think ab...
9 comments:

Is Your Unit Test Isolated?

›
(Kudos to the great software guru Jeff Foxworthy for the card phrasing.) An effective unit test should follow the FIRST prescriptio...
2 comments:
›
Home
View web version
Powered by Blogger.