3 ms·
I've spent a few years dealing with fuzzy requirement myself. And we tell outselves it hurts noone when a bug happens, but we're being deliberately obtuse in th
by markdennehy 17y ago
I've spent a few years dealing with fuzzy requirement myself. And we tell outselves it hurts noone when a bug happens, but we're being deliberately obtuse in those cases I think. Does it really hurt noone if an online test which comprises a percentage of someones final degree grade, crashes repeatedly while the course tries to take the test? Does it really hurt noone if bad UIs cause people to lose time or money, especially when you add up all that time?
I'm not suffering from an absolutist morality here - I'm pointing out that there are consequences to piss-poor engineering, and it is necessary for engineers to take the viewpoint of those being hurt rather than that of those trying to make money selling the product; because after four hundred years of training engineers, that's the best way we've found of preventing disasters. And the same should be true of developers, because just as civil and mechanical engineering before it, computer and software engineering are increasingly forming an integral part of the infrastructure we live our lives in.
- eugenejen 17y agoAnd that means there are tons of improvements to be done and lessons to be learned while you need to make money to support your live and maybe that's why you can exploit those bad products and design better one to kill off them! You seem to hang up at the concept that it has to be perfect from the first time from your writing.