2 ms·
Don't forget what I call "technological supremacy" bias: https://news.ycombinator.com/item?id=14902333 https://news.ycombinator.com/item?id=14902333
by jaclaz 9y ago
Don't forget what I call "technological supremacy" bias:
https://news.ycombinator.com/item?id=14902333 https://news.ycombinator.com/item?id=14902333
- alkonaut 9y agoOf course, and having system requirements is obviously a good thing. While it's obviously a fact that devs have more powerful machines than their users, I'd argue that the tolerance for performance is MUCH lower among devs. When my IDE does a GC pause for 5 seconds I go insane. Yet I have users that use the software I write, and somehow insist on using enormous datasets in it (much more than we would have imagined) meaning completely ridiculous delays (minutes if not more). When I ask if it doesn't drive them crazy, they say "no, because in the past thus job took a week with pen and pencil" or "the old program didn't have this feature at all, so of course a minute wait is OK in the new program!". A developer would never say that about the new shiny feature in their IDE or similar "yeah I like the new go-to-symbol even though it takes 15 seconds..." (and it might SAVE us time still, compared to doing it the old way). But we'd complain like crazy. So our technological supremacy bites us some times too.