It depends on the project you're on, and what phase of development you're in. If you work on your own, do anything you like. If you work on something being us

It depends on the project you're on, and what phase of development you're in. If you work on your own, do anything you like. If you work on something being used daily by tens of millions of people, upon which your company's lifeblood depends, you're more careful. Actually checking in code is somewhat anticlimactic; leading up to that, you've run a bunch of tests, gotten a code review, and satisfied yourself that the change is appropriate and necessary. Post-checkin, you monitor the build, make sure that BVTs work, and basically make sure you haven't broken anything. A good checkin isn't a big deal. It's the stuff around it that matters.