3 ms·
I ran into this when some moron management -- sold by greedy, moron venders -- wanted to share an IBM tools (Rational, etc.) installation between the U.S. and I
by pasbesoin 12y ago
I ran into this when some moron management -- sold by greedy, moron venders -- wanted to share an IBM tools (Rational, etc.) installation between the U.S. and India (primarily -- also some other locations).
Damned chatty software and in many small and synchronous/sequential pieces. It ground to an utter halt and was, in its default configuration, entirely unusable. Quelle surprise.
I'd argued for testing over deliberately hindered (latency et al. injected) network links, before proceeding or at least before placing dependency upon the rollout.
It says a lot that even in this fairly technical group -- a quite significant development shop within a large organization -- no one seemed to get it. Well, one or two did, privately, but there was no effective means to rock the boat.
I'm not sure what conclusion to draw from this, other than that persistently over many years, our profession as a whole (as opposed to some more effective parts) has refused to "get" latency.
- pekk 12y agoI don't know which profession you mean; your example is a failure of consumers of technology to "get" latency more than it is a failure of producers to get it.
- pasbesoin 12y agoI guess I mean some union or intersection of information systems and information technology. The enormous private employment sphere -- a substantial part of it being significantly sized corporations -- where so many graduates go off to have "careers". It's not "sexy" employment, and careers aren't what they used to be, but there's still a lot of it around. (U.S. perspective) In other words, Scott Adams could probably write a clever strip or three about latency. Perhaps he has.