I think of this as avoiding 'premature polishing', much as I try to avoid premature optimisation. The evils are of a comparable nature, IMHO, even though I don'

I think of this as avoiding 'premature polishing', much as I try to avoid premature optimisation. The evils are of a comparable nature, IMHO, even though I don't seem to be in the majority on that one. 'Clean lines' is my mantra. Whether it be done through a remote API, a database queue or a multitude of classes, loose coupling and sensible, strict and adaptable communication between clearly separated units is my number one priority. Everything else has, at the very least, the danger of encouraging the traces of the architecture astronaut within me... and he's enemies number one, two and three :) The units themselves can be as good or as thrown-together as circumstances demand, but the separation/communication being of a professional standard is set in stone.