...this one uses a business rule engine (drools) to allow you to declare in a text file your idea of good taste and enforce it for your code base.There's also macker that seems to do the same.
I do know that a lot of times if the programmer gets good, while he is getting good, he learns that most people do not understand what he does. So that's really separating for programmers. Programmers are kind of driven apart by that realization that they are dealing with things that most people do not understand, and after a while they give up trying to communicate.I often find it hard, even among developpers, to communicate and understand each others. Unfortunatly I don't think computers are the only place where people find it hard to exchange ideas...
Architecture design is so important we have to do it all the time. There is a little resistance to doing it before we're sure what to design, especially producing what is called the big design up front where you write a document and then someone tries to hold you to that design; "We don't care if you made a mistake, we want you do what you said." That is foolishness, but there is no resistance to thinking.
There is resistance to "if I have kind of an idea how this is going to go and you have kind of an idea how this is going to go, instead of having the argument today let us just to do the part we need to do today, that [part] we agree on and we will wait tomorrow to see what we have to do [then]. If we need to have an argument tomorrow, it will be about tomorrow's stuff.Good wisdom ;-)
