4 ms·
Agreed. We have to produce a lot of paper doc in my domain, and in our bug base, there's a section dedicated to spec bugs. Just cos it's in the spec doesn't m
by bmj 16y ago
Agreed. We have to produce a lot of paper doc in my domain, and in our bug base, there's a section dedicated to spec bugs. Just cos it's in the spec doesn't make it right.
- kabdib 16y agoAnd the spec may be right, but it's still the wrong thing to do. Applications are complex, fragile things. If you care about keeping them going over time, you wind up kowtowing to a lot of workarounds. Welcome to the software industry. The attitude of "I can change library Z, be spec compliant and still sleep at night even though the change took half an industry down" might be /correct/ but it is not going to retain customers. Do it enough, and you'll see users flee.
- mgkimsal 16y ago"Do it enough, and you'll see users flee." Unless there's no where else for them to go. :)
- kabdib 16y agoIBM was a master of this: Get a customer cornered and then bleed them. There are modern versions of this, too (Oracle springs to mind). "Nice business you have here. It 'ud be a shame if something were to . . . /happen/ to it? Right?" "Right, boss." "Shaddap, I ain't talkin' to youse." It's a successful, ancient business model.