The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
I enjoyed England vs Italy, a game played well on both sides, in my opinion.
I especially like the fact you give the Italian Olympic Diving team something to do between Olympics.
Michael Martin Australia
"I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible." - Mr.Prakash One Fine Saturday. 24/04/2004
1. Your country has never even qualified for a World Cup. 2. England aren't yet mathematically out, if we can beat CR and Italy win their two games we can still finish above CR and Uruguay on goal difference. 3. Even if we were, you should be posting this about Spain, Cameroon and Australia instead.
It's finally occurred to me that when it is a pattern, it is by definition inefficient and counter productive.
It became clear as I am surrounded by guys swearing by pattern this, pattern that! If it's a good technique why do you need to impose it? Shouldn't it self evidently win everyone heart? Nope because patterns are more like religion, used stubbornly in spite of contrary evidence.
I rather prefer the term technique. Technique is something you should learn first. Then you use it or not, whether it helps you or not. And its need is self evident. If it's not obviously needed there is no need to use or impose it either. Plus one can improve upon a technique, whereas one cannot touch the holy pattern until a new software best seller fad comes along!
Remark maybe it has nothing to do with pattern but more to do with stupid people imposing their rote learning on me...
I think your final observation is the correct one, I don't see patterns "imposing", being imposed by stubborn, hide bound old senior devs (ow that hurt) happens of course but I'm slowly relearning to be more flexible, honest.
Patterns are a tool, people become comfortable and productive with a toolset, changing reduces that and most of us are too lazy to do that willingly. Arguing over the merits of patterns is simply a form of entertainment, give the silly buggers some work to do, that generally shuts them up!
Never underestimate the power of human stupidity RAH
It should exist an anti pattern called "Pattern programming"
I'm also surrounded by developers swearing by pattern and I'm in an Agile team. For me there is an incompatibility between "pattern" and "Agility" because when you are Agile your architecture emerge and there is no reason to think in term of patterns or pre defined solutions.
Most important is not to know a pattern but to know the anti patterns.
or me there is an incompatibility between "pattern" and "Agility" because when you are Agile your architecture emerge
This sounds like the classic misunderstanding of agile that goes roughly along the lines of 'since things change, we never need to design'. I work mostly on agile projects and I can tell you that design patterns are very important to make sure you develop in a way which can accommodate that change. If anything, getting a good framework design is more important in agile because it strongly affects your ability to adapt during development, and that's the essence of agile.
This sounds like the classic misunderstanding of agile that goes roughly along the lines of 'since things change, we never need to design'.
Agility (and Scrum) pretend architecture emerge. I also work mostly on agile projects and I'm agree that design is very important to make sure you develop in a way which can accommodate that change but design patterns are not the only way to design something.
I remember the time I had to argue against patterns that now are become anti pattern. And that the problem with patterns. When a pattern is not correct it's hard to argue against it because every book, every web page defend it until he became an anti pattern years latter... It is why I think it is more important to know its anti patterns. And I'm not talking about teams that don't really understand to goal of a pattern and that incorrectly implement it. And some patterns are so complex they don't respect the Keep It Simple and Stupid rule.
The problem is not with the patterns. When used with thought, they indeed help in solving problems without causing new ones.
The real problem are the people. The simple version is the Voodoo programmer. Those people have little to no understanding of what they are doing. Instead, they try to copy and paste code snippets, of which they must have an impressive collection. And this collection is then used like a book of magic spells for and against every situation.
More 'advanced' Voodoo programmers have made an art of at least appearing less stupid. They have endless lists of rulrs, coventions and patterns (which in reality are just nice names for their magic code snippets) and want everyone to follow these rules just as religiously as they are.
Remember, they more often than not they really don't understand their magic spells. They use things because 'it's a pattern', or beacause 'Mr. ABC said so in his book/article/blog/speech/whatever'.
In some companies management really likes religious code monkeys. They are easier to manage, cost less and look sufficiently competent to outsiders.
That is fun. I call them the alchemist for the same reason. An alchemist don't do real magic. An alchemist combine products to create spells or a potions. Most of the time he only read precipices in a book. But for me an alchemist is not a bad programmer. He can be very good in his craft. He just prefer combine thinks than creating things.
And yes today most companies prefer Alchemists or Voodoo programmers