Providing higher quality code than necessary is an instance of the handicap principle in the software world. Basically, signaling you are skilled by doing your job in a more costly way. Examples: using strongly typed formal languages, extensive test coverage, hefty documentation
-
-
Perhaps you overdo it on the easy to observe dimensions of quality, in order to convince observers that you are also good enough quality on the harder to observe dimensions.
-
Makes sense. Balancing organizational priorities (time to ship, right amount of QA to manage cost of potential bugs) is harder than just maxing out software quality on easily measurable dimensions.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.