2 ms·
I guess it depends on your objective. If you want to create a lean, well-engineered architecture where things are always done the correct way, you take your ap
by ryanwaggoner 18y ago
I guess it depends on your objective. If you want to create a lean, well-engineered architecture where things are always done the correct way, you take your approach. If you want to build a multi-national company worth $170 billion, you go their route.
Yes, that's a fallacy, because it's not an either/or decision, but my point is that engineering supports the business objectives, not the other way around (assuming we're talking about a business).
- jsdalton 18y agoThere 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.