Profile cover photo
Profile photo
Andrew Coulton
Andrew's posts

Post has attachment
We're recruiting! We have a full time vacancy in our development team for a creative and methodical web artisan early in their career. If you want to build your skills by working on a mix of challenging and bespoke projects in a supportive environment this could be just the job you're looking for.

See our website for more details.

Post has attachment
Andrew Coulton commented on a post on Blogger.
But if you don't have tests, how do you know whether the working code you're refactoring is still working? By checking it by hand (or with acceptance tests) each time? That's going to be time consuming and/or risky - and may therefore deliver negative business value compared to leaving the DIRTI implementation alone.

And if you write tests after the fact, how do you know they're actually testing everything that needs to be tested?

The only difference between your DIRTI approach and the way I practice TDD is when the tests get written. There's no reason you can't write a dirty test and a dirty solution - before you understand what needs to be written - and then refactor both together as the abstractions emerge.

I found that Uncle Bob's videos at and gave a very clear demonstration of how to practice TDD without delivering less business value.
Wait while more posts are being loaded