Why is ancestral code called “shit mountain”?

The only way to navigate a mountain of shit is not to refactor, but not to refactor. Why can someone add functionality to shit mountain? It’s very simple: pull apart the mountain of shit, smell each piece, find the shit that corresponds to the function you want to change, wrap (encapsulate) the shit, and you can pretend it’s not shit, it’s chocolate . Then, pull a new poo next to it, wait for it to air dry and form (the test passes) and you can call it a day.

This article is reprinted from: https://ldqk.xyz/2152
This site is for inclusion only, and the copyright belongs to the original author.

Leave a Comment