Comments on: OOP is a tool http://fiatdev.com/2008/04/07/oop-is-a-tool Let There Be Software! Sat, 19 Sep 2009 09:36:06 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: Daniel http://fiatdev.com/2008/04/07/oop-is-a-tool/comment-page-1#comment-570 Daniel Wed, 09 Apr 2008 15:17:17 +0000 http://fiatdev.com/?p=91#comment-570 <p>The key here is "high quality". I think the manager example is pretty clear in this regard. I'd argue that a software were you can't unit test a class properly is not high quality, even if it happens to be correct.</p> <p>A high quality software necessarily has diminished maintenance costs, and lack of strong unit tests definitily increase the cost of maintenance severely.</p> The key here is “high quality”. I think the manager example is pretty clear in this regard. I’d argue that a software were you can’t unit test a class properly is not high quality, even if it happens to be correct.

A high quality software necessarily has diminished maintenance costs, and lack of strong unit tests definitily increase the cost of maintenance severely.

]]> By: phil http://fiatdev.com/2008/04/07/oop-is-a-tool/comment-page-1#comment-569 phil Wed, 09 Apr 2008 14:13:49 +0000 http://fiatdev.com/?p=91#comment-569 <p>@Steve: very insightful. I hadn't thought of it like that, but you are right. OO isn't really a monolithic thing, it is a set of practices with varying degrees of utility.</p> @Steve: very insightful. I hadn’t thought of it like that, but you are right. OO isn’t really a monolithic thing, it is a set of practices with varying degrees of utility.

]]> By: Steve http://fiatdev.com/2008/04/07/oop-is-a-tool/comment-page-1#comment-568 Steve Wed, 09 Apr 2008 08:45:07 +0000 http://fiatdev.com/?p=91#comment-568 <p>The root cause of problems faced with use of OO is that it is talked about as a lump when it really falls apart into multiple different techniques</p> <ul> <li>Encapsulation of data and implementation</li> <li>Things sharing the same API contract (interface inheritance)</li> <li>Naive code re-use (implementation inheritance)</li> <li>partitioning of responsibilities</li> <li>probably others</li> </ul> <p>While implementation inheritance tends to be the major focus of teaching, it tends to be the least useful (& most complicated) in practice (mix-ins or composition often being a simpler route to the same end).</p> The root cause of problems faced with use of OO is that it is talked about as a lump when it really falls apart into multiple different techniques

  • Encapsulation of data and implementation
  • Things sharing the same API contract (interface inheritance)
  • Naive code re-use (implementation inheritance)
  • partitioning of responsibilities
  • probably others

While implementation inheritance tends to be the major focus of teaching, it tends to be the least useful (& most complicated) in practice (mix-ins or composition often being a simpler route to the same end).

]]> By: Ben http://fiatdev.com/2008/04/07/oop-is-a-tool/comment-page-1#comment-567 Ben Wed, 09 Apr 2008 05:14:11 +0000 http://fiatdev.com/?p=91#comment-567 <p>I think the difficulty lies in using the right amount of inheritance. There's a fine line in the overuse of inheritance and getting the usage just right. The Final==Good article was an interesting find. Thanks Phil.</p> I think the difficulty lies in using the right amount of inheritance. There’s a fine line in the overuse of inheritance and getting the usage just right. The Final==Good article was an interesting find. Thanks Phil.

]]>