Sometimes when you are doing a lot of Plone development you could miss the big picture: Plone is not just a CMS. It's a damn good CMS with almost unlimited possibilities of integration. However its 'unlimity' has started to be one of its biggest limitations.
Solr, contentmirror, WSGI, repoze.bfg, GetPaid, KARL are all hot topics in the Plone community nowadays. Have you ever been wondering how to use them well? With Plone? Make your bright - integrate efficiently your Plone with Python eco-system today!
It's easy to shoot yourself in the foot when developing in any framework. But with the complexity of , it's easy to construct a trap that will shoot you in the foot in half a year.
This rant takes up a list of no-no's. Many of the seems like a good idea, some are common in the community, but still bad ideas, and a few are just a case of using tools that you may not have known about.