It’s been more than a year since the previous (and only) post to this blog. That doesn’t mean that QAM development has slowed; in fact there’s been a huge amount of work on it, and even some more documentation. We’ve just not been posting about it, something which we really should rectify.
I’ve shown QAM to various people in the past year, and one common thread that seems to have come out of that has been that most people don’t really seem to get what QAM is about. Perhaps it’s just that most developers in large shops don’t have to deal with deploying and running production systems at all, and even the small-shop developers have to deal with only one or three systems or sites. (We currently have thirteen projects running on our production server and twelve on our staging server. A quick look through our repos and some client ones over the last three years shows over thirty different projects built and deployed with QAM.)
So perhaps it’s time to put a bit more effort into telling people about what we do.
A good start is the relatively recent QAM Principles and Purpose document. This covers both the aims of QAM and the basic structure of a QAM project.
Oh, and also, for quite some time we’ve had QAM available for checkout via git: git://git.cynic.net./qam