|
|
|
|
|
by choobacker
483 days ago
|
|
I agree with his issues with dependencies. But I'm not sure about his other stuff. "Avoid features that add disproportionate cost" I expect part of the problem here is that it's often not clear what the value of features until it's available to customers. Even the costs of bloat are unclear. Take his bank website example. Do we really think many bank customers are choosing banks based on their website's latency? Banks compete on things users actually care about, like interest rates or fees. Lots of software inevitably won't meet our ideal standards, because given the cost of developers it's not worth doing things The Right Way. |
|
I definitely stay with my bank (Lloyds in the UK) partly because they have a good website, and I will not bank with HSBC because their app will not work if you install things from outside the Google App store (and logging into the website needs the app, at least for me at the moment - I think that can be solved).