On 8/13/06, Karl-Ludwig Reinhard <[EMAIL PROTECTED]> wrote:
On Aug 13, 2006, at 7:26 PM, Nick Guenther wrote: > > "Look! I can do Java without even writing it! Love me!" > > -Nick > > Hi, i dont think thats the point. its important for development in a team. the head dev can define the structur, andi think oop could be a very complicated thing. In maths you make darfst too.
Yes, yes it is. Firstly, OOP should not be complicated; if it is complicated you are doing something very wrong. In fact this is one of the central principles of computing: Keep It Simple Stupid. We make abstractions to simplify our thoughts and designs, and if our abstraction (e.g. OOP) is making things worse then you should go back and look at your problem, instead of trying to force it into OOP. UML forces a particular problem solving strategy on it's users, and that is a Very Bad Thing. Anyway, who says the head dev will always have the best ideas about structure? This top-down micromanagement model you work in can't be as productive as more freeform teams. And show me a mathematician who works by being commanded from above on how to think. -Nick p.s. what is darfst? Babelfish says it's "may". I don't know what to make of that)
