| ▲ | lukasgelbmann 13 hours ago | |
Insightful article. The author makes some great points about the dynamics of technical debt in organizations. I think a sinking ship is a reasonably good metaphor though. A sunken ship is a horrible, terrible outcome. In the metaphor, a codebase is sunken when it’s unviable to continue using it. The organization stops working on it and no longer runs it. At this point, the code is completely worthless to the business, like a ship at the bottom of the ocean. True, you could imagine the code getting worse theoretically. But in reality, it will just sit there and rot.[0] The business might attempt a rewrite or just discontinue the product. It’s possible, but not a given, that a business sinks with one of its codebases. This can happen with a ship too, if a business relies heavily on it. | ||