Jeremy D. Miller -- The Shade Tree Developer - All Comments

re: My friend needs some help on an article

Derick Bailey — Fri, 09 May 2008 14:45:20 GMT

There's a lot of suggested topics about underlying principles, and "high" level patterns. I'd like to see an article that ties things together - a look at why patterns exist, in the context of the principles.

for example, MVP/MVC are great patterns - but if you truely understand DI, LSP, SoC, Orthogonality, etc. etc., then MVP/MVC are some of the possible natural outcome of the code you will want to write for a UI.

re: Should I Blog?

Will — Fri, 09 May 2008 13:23:20 GMT

"You're going to make a very opinionated, inflammatory post and get criticized for it."

This is also known as the "Stored Procedures Post."

re: My friend needs some help on an article

Kiris — Fri, 09 May 2008 03:34:12 GMT

+1 to object stereo types. While the other stuff is interesting, I think this one is under served in terms of coverage.

re: My friend needs some help on an article

J.P. Hamilton — Fri, 09 May 2008 01:33:30 GMT

Object Stereotypes or Creational Patterns

index portfolio management techniques

index portfolio management techniques — Thu, 08 May 2008 20:10:56 GMT

Pingback from index portfolio management techniques

re: My friend needs some help on an article

Chad Myers — Thu, 08 May 2008 13:54:15 GMT

@Bil That's the first stage in bending the mind around IoC and away from 'traditional' creation patterns. I started out using ObjectFactory.Get<IFoo>() all over the place, but what I found was that it was essentially just a replacement for the 'new' operator and I still had many of the same problems. Sure, I have a lot more flexibility, but it's still not true INVERSION of control, it's more DELEGATION of control.

The next phase (that I went through at least) was to get to the point where no object is creating another object (well, at least the objects I control, new StringBuilder() is OK, for example).

The only place I want to see ObjectFactory.Get<TYPE>() anywhere is when the app is initializing or in some central place that kicks off a cascading dependency resolution fiasco that results in all my objects being ready to go when they're needed.

re: Agile Antipatterns discussion

Bil Simser — Thu, 08 May 2008 13:32:21 GMT

Something else, not pushing the PO or customer on more clarification on user stories. If the team doesn't know what the story means they need to push back and have the customer explain it. Far too often, people just take it as gospel and "figure it out". I say "No!". Stop and ask and get the customer to tell you what they really want. In addition, I repeat it back to them in my words so we're both on the same page before any work starts (partially so I know what they said but more that they understand my perspective on what they told me)

re: My friend needs some help on an article

Bil Simser — Thu, 08 May 2008 13:27:22 GMT

Heh. What's funny is *everyone* uses "IoC" describing inversion of control (and hey, why not, it's shorter to type). I bet *everyone* has an IoC static class with a couple of methods like Resolve and Resolve<T> in them and an initialize method that takes in IWindsorContainer.

The debate now is should "IoC" be "Locator" since that's what it's doing which introduces more DDD like terms to replace the technobabble.

re: My friend needs some help on an article

andrew finkenstadt — Thu, 08 May 2008 13:23:36 GMT

1+ control of inversion

re: My friend needs some help on an article

isaiah — Thu, 08 May 2008 11:53:07 GMT

design vectors and object sterotypes please

re: My friend needs some help on an article

Andy Stopford — Thu, 08 May 2008 11:51:29 GMT

>> I think what I'm going to do first is the Object Stereotypes, but probably use some IoC scenarios as illustrative examples

when you say 'I' you mean your friend, right? ;-)

re: My friend needs some help on an article

Robz — Thu, 08 May 2008 01:45:48 GMT

+1 IoC

re: My friend needs some help on an article

Jeremy D. Miller — Thu, 08 May 2008 00:45:16 GMT

@Nat,

""The importance of separating functionality from the grunge work of assembling object graphs". In OO code, you can't separate functionality from assemblage of objects."

Yes you can, and many times you should. Object graphs do real work in and by themselves. Assembling those object graphs from storage, the database, Xml config, or whatnot is often a separate responsibility from the business logic performed by those object graphs. Sorry, but I think the IoC article has some value based on your comment.

re: My friend needs some help on an article

Nat — Wed, 07 May 2008 21:10:26 GMT

I vote for the design vectors. It sounds like your friend has a lot of personal experience and wisdom to put across.

From your short abstracts, I think your friend needs to work more on the IoC/DI/object-construction topics. For example...

"The importance of separating functionality from the grunge work of assembling object graphs". In OO code, you can't separate functionality from assemblage of objects. The functionality IS the assemblage of objects. If you can separate functionality from composition, it means your classes are too large. If you try to separate functionality from composition, you end up with code only expresses how the system works, instead of what it does and why.

The others sound like your friend is repeating what he has read elsewhere. I'd much rather read his thoughts about software than his rewording of someone elses.

re: My friend needs some help on an article

Seth Petry-Johnson — Wed, 07 May 2008 20:18:54 GMT

+1 IoC, +1 Persistence and Data Access.