Our tech lead left a mess in the database. He turned his screw-up into an architectural discussion, weighing the benefits of duplicated, messy data vs. keeping it consistent. He suggested that, instead of fixing his broken script and cleaning the mess, we should break all of the other scripts and have them trash the database, too.

They almost believed it.

What a clever maneuver. I wish he would use his cleverness to make good software, instead.