Have you ever faced the fallout of a bad software code check-in? You will see nasty feedback coming your way for not doing good code reviews and testing!
There are immediate rumblings of delays, rollbacks, expectations management, and escalations. Because you added incorrect code, that does work!
The discipline of running a pre-check-in routine was precisely developed to remind us what needs to happen before the code is checked-in.
It provides a way to define completeness criteria for the conclusion of work. Put in place, it provides a safety net for avoiding costly mistakes after completing the work.
In a way, the pre-check-in routine acts as the gatekeeper. Something that does not let you go past without the required due diligence.
A pre-check-in routine is usually an added step before committing to doing something important. When we are sure about having done the checks and balances for the work and the interactions we are involved in, we have a lesser chance of making mistakes.
This applies to almost anything we are involved in. Check what needs to happen, who needs to be notified, and who is impacted. Do we carry everything in the bag we require?
Check and then commit!
Comments
Post a Comment