First Rule of Software Development
We had a great email go out today from Brian Windheim, one of the Architects here. He said I could share it. It was sent internally to his team. I like Brian's style.
Frank broke the First Rule of
Fight Club Software Development yesterday:
Never commit code just before you leave for the day.
The CCNET (Continuous Integration) build subsequently broke – despite the fact that he ran a local build first – and team members who were still in the office had difficulty progressing with their work for several hours.
First, the remedy. If this ever happens again, simply revert the source repository to the prior known-good state using SVN’s revert changes. Don’t try to apply band-aids, and don’t waste time solving a problem that the original developer could probably solve in about two minutes. Using the tools correctly saves oodles of time.
Second, the reaction. Folks, don’t panic. Ever. If a quick peek doesn’t find the answer, don’t be afraid to pick up the phone and call the dude who broke the build. In 15 years of software development I have many times been the guy that broke the build, fixed the build, got mad when I was working at midnight to fix something broken by the guy that just went to Mexico on vacation for two weeks, reprimanded the guy the broke the build, been reprimanded for breaking the build, and so on. Get used to it.
Third, the lesson. Don’t commit things without waiting for CCNET to tell you that you can go home. All the more reason to have a faster build, no?
Broken builds break hearts, I say.