3 ms·
While I find Joel's articles interesting and often enlightening, I don't think "someone" needs to treat them as the Word From On High of software development or
by donaq 17y ago
While I find Joel's articles interesting and often enlightening, I don't think "someone" needs to treat them as the Word From On High of software development or program management.
Anyway, that's still not impossible to solve. After the design phase, reward for every module shipped, then deduct points for every bug reported by users. If the programmer is able to hide bugs such that they never manifest in production, I say all power to him.
- cousin_it 17y agoNow the programmer has an incentive to make their subsystem hard to use, so users don't go there and report bugs. C'mon, add some more epicycles.
- donaq 17y agoWhy would the bug reporting mechanism be in a subsystem? Unless every subsystem had its own bug reporting mechanism, which makes zero sense. [Edit] Oh ok, I think I see what you mean. Well, firstly, if a subsystem weren't integral to the app, why develop it in the first place? Secondly, you could always track the usage of the subsystem and provide additional incentives for its success. Lastly, who says subsystems have to be directly accessible to the user? If tasked to write a module that runs in the background, one can hardly make it deliberately obtuse.