Flutterby™! : Verbosity Difference

Next unread comment / Catchup all unread comments User Account Info | Logout | XML/Pilot/etc versions | Long version (with comments) | Weblog archives | Site Map | | Browse Topics

Verbosity Difference

2009-08-19 15:25:50.883102+00 by Dan Lyke 1 comments

The Verbosity Difference, on OOP and programming language verbosity:

The problem is that the marginal cost of adding a new class is greater than the marginal cost of extending an existing class. If it was easier to make a new class, we would have done so. But we would also have made a new class if it was harder to add methods to an existing class, because then the trade-off would have been different. In other words, what matters is the difference in verbosity between the “right way” and the “wrong way”, not the absolute level of verbosity.

[ related topics: Software Engineering ]

comments in ascending chronological order (reverse):

#Comment Re: made: 2009-08-20 04:56:49.953934+00 by: spc476

It could also depend upon coding conventions. I have a friend who's coding style mandates a huge, 20+ comment block for every function, regardless of how trivial a function (which includes a hand-maintained change log per function). So inadvertently he's created an environment where it's easier to add functionality to an unrelated function than to create a new function.

But it's the way he's always done it, and it's the way he'll always do it.