With all our experiences we tend to have a biased view. That is how smart people operate. To get to wise level we need to understand that time changes everything.
Same goes for programming...
When you first need to evaluate frameworks, methods and other stuff. You must not jump to conclusions due to last bad experience. I was burnt a lot of times due to selecting the framework that was "cool" last time I used it, and was nowhere as good for a new project. Now I can say that I will not throw out a method or framework just because it's was not as good as I expected last project.
At one time I was angry with RoR for not supporting PostgreSQL, that led to dumping it on next project as a candidate, at the end we dumped all our work and rewrote it in RoR and still made the deadline, just because I "saw the light" and tried it once more. And unfortunately I did the same mistake on next project, but it was the other way around.... RoR was selected just because it was fast... We got in a lot of trouble(mostly due to ACID-icity) and had to switch to Java EE and .NET combo...(I will not give any technical specifics of both projects)
After those 2 project I now have a mind that is more open to possibilities, thus giving me the edge over people that see only one solution to any problem...
So the moral is biblical: Don't judge and you will not be judged....
When approaching any problem you have to let the "old bad" stuff be on the same plank as new and cool.
