Decades ago, when Mathew Thomas was a young programmer for a pager company, he learned a valuable lesson that many veteran coders have likely learned, too: If the weekend is almost here, don’t touch anything. “If you really want to anger the gods of software, deploy new software on a Friday afternoon,” Thomas, now SVP of engineering at KnowBe4, told us, recalling how a well-meaning colleague at the time who’d wanted to optimize a database by changing indexes, but did not change all of the code that uses the indexes. Software at that pager company connected a customer relationship management (CRM) network to a network of pagers. The changes accidentally took down the CRM system, Thomas said, and there was the risk that two million customers could not manage their devices. “It was what we call a potential extinction-level event. I mean, it was that type of bug,” he told us, remembering working the weekend to solve the problem. Veteran coders like Thomas spoke with us about the coding bugs that can ruin a Friday or a whole weekend—and what mechanisms (like emergency rollbacks) should be in place before everyone heads to happy hour. Why weekend work can wait.—BH |