[62619] in North American Network Operators' Group
RE: Worst design decisions?
daemon@ATHENA.MIT.EDU (Ron Snyder)
Fri Sep 19 18:12:02 2003
From: Ron Snyder <snyder@roguewave.com>
To: nanog@nanog.org
Date: Fri, 19 Sep 2003 15:04:17 -0700
Errors-To: owner-nanog-outgoing@merit.edu
> overdesigned rather than poorly designed. even if nobody
> can use it, it's just an extraneous feature. an atm built
> into the concrete that you'd have to stop short of and
> get out of your car to use. now that would be poorly
> designed.
</lurk>
Do you mean overdesigned in the sense that because that atm has features
that wouldn't be needed in it's current location, that it shouldn't have
those features? What about just making inventory tracking easier? (eg. "We
have 32 ATMs that are all featurewise identical and they're all
interchangeable" vs. "We have 22 ATMS with feature X and 10 w/o feature X")
Now, to get it somewhat related to network stuff:
s/atm/router/
s/features/capabilities/
s/location/network function/
<lurk>\
