Zen and the Art of Merging Code
A team declared the old system unmaintainable and began a complete rewrite. Two years later, they shipped. Within months, developers were calling the new system unmaintainable. The senior developer mused, “If the disease followed us, perhaps we did not leave it behind.” Then: “What did we rewrite, the code or ourselves?” The Teaching Unfolds There […]
A junior developer ran the program, and a stack trace fifty lines deep appeared. The junior cried, “There are so many places where this went wrong!” The senior developer asked, “Did the error happen in fifty places, or in one?” The junior pointed to the topmost line. The senior smiled. “And from where did that […]
The team achieved 100% test coverage. They celebrated their thoroughness. The senior developer asked, “What percentage of your understanding is covered?” And then, “If every line is tested, what remains untested?” Understanding the Koan We treat code coverage as a destination, a number that validates our diligence. When that metric reaches 100%, we feel we’ve […]
“We must pay down this debt!” declared the team lead. The senior developer asked, “If you pay it all, what will you owe then?” And, “Who is the creditor of technical debt?” Reflections We speak of technical debt as if it were a financial obligation, complete with interest rates and creditors waiting impatiently for payment. […]
