There was a discussion here last week about technical debt, and I think this is a great example of it. You incur debt when you make a decision like this one. W

There was a discussion here last week about technical debt, and I think this is a great example of it. You incur debt when you make a decision like this one. When you make thousands of decisions like it, they add up to a whole lot of debt. The problem is that this debt is nearly impossible to quantify, so it's often invisible to the business team. A decision like keeping two copies of Notebook around thus seems like the correct decision to the business team at the time, but later proves to cost a lot more down the road. So while it's true that engineering supports business objectives at the macro level, a pure "business" mindset at the micro level can lead to short-sighted and ultimately costly decisions like this one.