The answer to the problem of testing

slowing us down as developers is to

treat testing as a first class citizen.

It is part of our job. Thinking about

what the code should do is of course

what we do. But since we're going to be

thinking about what the code should do,

why not write that down somewhere in say

an automated test where we can actually

check that those assertions and those

assumptions are correct all the time and

when someone makes some changes, they

haven't broken some behavior that we

expected. We should also be treating it

like a first class citizen in terms of

performance. This is not something that

should just kind of like run, you know,

maybe when we want to and it takes as

long as it takes. That's okay cuz it's

over there. No, fast performing tests

are what make us productive. So treat

tests as a first class citizen. Write

tests as soon as possible to the time at

which you write your production code.

Treat them as first class citizens in

terms of the performance of those tests.

And never ever think that the time that

you spent thinking about what to test is

wasted because the thinking is the thing

that takes the time and the thinking is

the thing that we get paid for anyway.