The reason I manage system test teams is because I’m paid to
Directly it gets boring I’ll do something else.

It’s always exciting then? A white-knuckle ride on the front seat of technology? 
Er no. Sometimes it is very exciting but mostly for the wrong reasons. Like something doesn’t work and management is going ballistic and clients are concerned, and users (poor souls) are becoming deeply, deeply depressed.

After having experienced this a few times and having warned management that there would be problems if they didn’t ...
... and having been carefully ignored, I decided to write a book setting out what I believe to be a better way.
And the better way lies in being a control freak, ensuring that everything gets nailed down and tested well and watching systems go up and stay up.
And listening to some bright person say:
Well it works perfectly - no need to have spent all that time testing.

And since every self-respecting book needs a support blog, here’s this one.

If it can go wrong it will not go wrong until the last opportunity to fix it has passed

Peter Farrell-Vinay

If you think testing’s expensive, try an accident

A test manager