3 ms·
One can assume writing documentation and comments is covered by both approaches. Still, the fastest scenario would be the most productive one. I agree with you
by vmateixeira 9y ago
One can assume writing documentation and comments is covered by both approaches. Still, the fastest scenario would be the most productive one.
I agree with your view regarding maintenance cost, but I don't think that's what's at stake here. We can go further and try to compare the amount of time needed to fix rat's nest with the amount of time needed to write the software all over again. Covering the rat's nest is in many occasions faster (on which I'm considering more productive) than rewriting.
- hn_throwaway_99 9y agoYou're never going to get around the fact that most of these things are qualitative assumptions. Is your documentation good? There's really no completely objective way to measure maintainability, because maintainability is often about how easy it is to handle unknown future change requests. Years ago "function points" were bandied about as a truly objective measure of software output and value. It turned out to be trivially game-able and added 0 value to software development estimation.