Long gone are the days when a developer blindly pushed code to the sourcecontrol without caring what happens after. Or at least they should be. The codewe write needs to compile, build, be deployed and somewhat function before beingtested. And how can a developer be certain that his code does all of the abovewithout testing it? No matter if we talk about functional testing on yourmachine, or writing unit tests, some testing effort needs to be put in it by adeveloper. Understanding and seeing how the code behaves after you have writtenit, or how it integrates into the bigger picture makes for a better developer.Whenever you are in doubt if you should be testing, ask yourself this "Am Icomfortable in deploying the software in production without it being tested bythe QA and take full responsibility for any defects?"