Comments on: OO is Hard http://laribee.com/blog/2007/03/23/oo-is-hard/ a yeah yeah, i push models like weight Thu, 21 Aug 2008 23:05:48 +0000 http://wordpress.org/?v=2.3.3 By: Evan http://laribee.com/blog/2007/03/23/oo-is-hard/#comment-3963 Evan Mon, 09 Apr 2007 03:55:38 +0000 http://laribee.com/blog/2007/03/23/oo-is-hard/#comment-3963 Once you feel you've mastered OO, go pick up a copy of Analysis Patterns by Fowler, and be prepared to take another step backwards from what you *thought* you knew. The learning curve gets bigger and bigger the more you read, but it is turning out to be quite rewarding. Fowler's book on Object Oriented Analysis Patterns inside the domain model is quite a cool read. Once you feel you’ve mastered OO, go pick up a copy of Analysis Patterns by Fowler, and be prepared to take another step backwards from what you *thought* you knew. The learning curve gets bigger and bigger the more you read, but it is turning out to be quite rewarding. Fowler’s book on Object Oriented Analysis Patterns inside the domain model is quite a cool read.

]]> By: Dave http://laribee.com/blog/2007/03/23/oo-is-hard/#comment-2681 Dave Wed, 28 Mar 2007 02:03:46 +0000 http://laribee.com/blog/2007/03/23/oo-is-hard/#comment-2681 My opinion (humbly) about CSLA: I'm opposed to the idea of Mobile Objects. I don't like the false sense of reuse it gives you. Accessing or hydrating an object locally or remotely can be quite a significant difference you might not want to make implicit. You are likely to still end up with differing local/remote use cases. The industry is trending toward services where you're dealing w/ messages in and out. I like the notion of "the endpoint is the application." That said, it's a pretty complete default architecture and those are few and far between. So, for me, it was worth study and evaluation. It probably works great in a client-server-esque, single application scenario. I am not opposed to a "Governing Metadata Layer" for entities. That is, a layer that will generate entity representations for different purposes: Bindable Client Object, DTOs for Aggregation, DDD-style Entity, JSON arrays, restful XML, etc. More on that later :) My opinion (humbly) about CSLA: I’m opposed to the idea of Mobile Objects. I don’t like the false sense of reuse it gives you. Accessing or hydrating an object locally or remotely can be quite a significant difference you might not want to make implicit. You are likely to still end up with differing local/remote use cases. The industry is trending toward services where you’re dealing w/ messages in and out. I like the notion of “the endpoint is the application.”

That said, it’s a pretty complete default architecture and those are few and far between. So, for me, it was worth study and evaluation. It probably works great in a client-server-esque, single application scenario.

I am not opposed to a “Governing Metadata Layer” for entities. That is, a layer that will generate entity representations for different purposes: Bindable Client Object, DTOs for Aggregation, DDD-style Entity, JSON arrays, restful XML, etc.

More on that later :)

]]> By: Javier Lozano http://laribee.com/blog/2007/03/23/oo-is-hard/#comment-2614 Javier Lozano Mon, 26 Mar 2007 19:30:24 +0000 http://laribee.com/blog/2007/03/23/oo-is-hard/#comment-2614 hear, hear! CSLA...hmm...what are your thoughts on that? hear, hear!

CSLA…hmm…what are your thoughts on that?

]]> By: Dave http://laribee.com/blog/2007/03/23/oo-is-hard/#comment-2595 Dave Mon, 26 Mar 2007 13:05:14 +0000 http://laribee.com/blog/2007/03/23/oo-is-hard/#comment-2595 Hey Javier. Thanks for the tip, I'll check it out. I wouldn't necessarily say lazy (though there is that problem out there.) I'd be more inclined to point a finger toward lack of knowledge or a tendency to look for the "silver bullet" with all of this new knowledge you've accumulated without realizing you've got a ways to go. (Cough, CSLA, cough.) I think the best thing a team using OO can have is a veteran. I think the same is true for a team making a foray into Agile. Hey Javier. Thanks for the tip, I’ll check it out.

I wouldn’t necessarily say lazy (though there is that problem out there.) I’d be more inclined to point a finger toward lack of knowledge or a tendency to look for the “silver bullet” with all of this new knowledge you’ve accumulated without realizing you’ve got a ways to go.

(Cough, CSLA, cough.)

I think the best thing a team using OO can have is a veteran. I think the same is true for a team making a foray into Agile.

]]> By: Javier Lozano http://laribee.com/blog/2007/03/23/oo-is-hard/#comment-2562 Javier Lozano Sun, 25 Mar 2007 15:51:33 +0000 http://laribee.com/blog/2007/03/23/oo-is-hard/#comment-2562 Damn. You hit the nail right on the head. A while back when I worked for "the big insurance company in town", I ran into the same "structured procedural" programming (I guess that's what happens when you take a ton of COBOL developers and put them through a 1 hour Java tutorial...) But if you recall our conversation about how it takes at leat 7 "classes" to map your domain entities, your statement holds true. It's sad that people shy away from it due to it's "complexity"...which I think it's not really that the problem is "complex", but rather that they're lazy. A while back, I ran into this blog post by Harry Pierson: http://blogs.msdn.com/devhawk/archive/2005/10/05/477529.aspx You should check it out. Damn. You hit the nail right on the head. A while back when I worked for “the big insurance company in town”, I ran into the same “structured procedural” programming (I guess that’s what happens when you take a ton of COBOL developers and put them through a 1 hour Java tutorial…)

But if you recall our conversation about how it takes at leat 7 “classes” to map your domain entities, your statement holds true. It’s sad that people shy away from it due to it’s “complexity”…which I think it’s not really that the problem is “complex”, but rather that they’re lazy.

A while back, I ran into this blog post by Harry Pierson: http://blogs.msdn.com/devhawk/archive/2005/10/05/477529.aspx

You should check it out.

]]> By: Interesting finding - 03/25/2007 « Another .NET Blog http://laribee.com/blog/2007/03/23/oo-is-hard/#comment-2517 Interesting finding - 03/25/2007 « Another .NET Blog Sat, 24 Mar 2007 19:31:07 +0000 http://laribee.com/blog/2007/03/23/oo-is-hard/#comment-2517 [...] OO is Hard [...] […] OO is Hard […]

]]>