Selfish moron.

But yes. Mobile media display, iTunes remote control, web browsing. In a stable platform that I don't have to screw with.

That's a lot of "That's it".

There is testing that isn't unit testing. Knowing when it's sufficient is one of the things that separates good coders from highly productive coders.

Only unit test what needs to be unit tested. If it needs to be tested the testing will pay for itself. If it's simple enough that it doesn't need testing, then you're wasting your time writing those tests.

Half the benefit of the unit tests/test-first methodology is that they force you to design even your internal interfaces in a reliable way. The other half is knowing you didn't introduce regressions in that oh-so-clever code.

For most projects you don't need a whole lot of tests but there will be a couple of subsystems that you almost can't manage without them.

There's nothing I hate more than the IDE deciding to display the new value of a variable by overwriting the old one, making it impossible to track the history of a variable without a piece of paper. Try debugging tricky races without that history.

Real debuggers give you a log, in your window, of all your actions and of the previous state you examined. No IDE I know of gives you that.

Job is easily 9-10 a day.

Useful work is capped around 5.

Overhead chews (from expense reports to travel arranging, to yet another bozo who couldn't be bothered coming to the meeting needing to be filled in) up the rest.