2 ms·
> Currently it seems that faulty design and code are actively harming the businesses. So long as a human exists to work around the faulty code, the harm to bus
by falcolas 8y ago
> Currently it seems that faulty design and code are actively harming the businesses.
So long as a human exists to work around the faulty code, the harm to businesses is minimal. For example, many companies sell feature-full, but absurdly slow and buggy, software to other businesses. The customers aren't going anywhere, and they've protected their niches with a minefield of patents.
So, the features hook the execs, and the end-users work around the bugs and slowness, the business sees no blowback from this.
My favorite anecdote was a front end engineer claiming "I went in and profiled our code and made an action go from 5 seconds to under a tenth of a second!" To which I can only go "Wait, there was a user-space action that took 5 seconds?!"
- TeMPOraL 8y ago> My favorite anecdote was a front end engineer claiming "I went in and profiled our code and made an action go from 5 seconds to under a tenth of a second!" To which I can only go "Wait, there was a user-space action that took 5 seconds?!" And I'm guessing there was, and you didn't notice it (or stopped noticing it at some point), because that's what people do. They get used to this nonsense. Especially if they have no power to improve it.
- thoughtspile 8y agoI'm actually pragmatic about it) 5 seconds is fast enough for an infrequent or complex action — it's not a week, come on! You might as well throw the feature away in a month. If it turns out the action is more useful than originally planned, you should take time to optimize it.