Rocky Burt wrote a good story about keeping client concerns separate . So, how to structure your code in such a way that the specific customisations for the customer don't bite the reusable parts. All made possible by a good sprinkling of zope 3 technologies.
I want to emphasise another thing: developer cooperation. Zope 3 makes it way easier to keep things separate than ever before. Some personal examples from the last few weeks:
view.categories, iterate over
view.resultsthat returns dictionaries with keys
title, etc. I put in some sample data and hand it over to our local CSS hero Mirella.
She gets to do her magic, I get to fill in the functionality. We both don't disturb eachother. Separation of concerns. Works like a charm.
Because everything was so neatly separated, the two remaining bugs were also well-isolated from the rest of the code and thus findable. And even though we were customising things inside our own custom product, nothing felt hacky or so. Everything was so neat and clean: it made us all feel pretty good at the end of the week. Another piece of solid functionality that'll delight the customer!
Me is real happy to work in such a cooperative environment and such a cooperative community with such cooperative coworkers. Great!
My name is Reinout van Rees and I work a lot with Python (programming language) and Django (website framework). I live in The Netherlands and I'm happily married to Annie van Rees-Kooiman.
Most of my website content is in my weblog. You can keep up to date by subscribing to the automatic feeds (for instance with Google reader):