Simon Brown wrote:Hi Luke, great question. I completely agree that there's often not enough emphasis on the software architecture aspects, and that's another reason why I wrote the book. I run training courses all across Europe and I've frequently seen this for myself. Many people seem to think that there is a conflict between architecture and agile, but that's not the case -> https://leanpub.com/software-architecture-for-developers/read#conflict
My approach is based around a minimal set of lightweight software architecture practices that include doing "just enough" up front design, communicating the resulting software architecture through a collection of simple sketches and taking a risk-driven approach to the delivery. It's something that (I feel) complements agile approaches and reintroduces some emphasis back onto the (often neglected) software architecture aspects.
Simon Brown wrote:Hi Comal, I'm not quite sure if you're asking about process (iterations) or technology (object pooling) ... could you expand on the question, please?
Simon Brown wrote:Thanks for the clarification, much appreciated ... unfortunately it's not a topic that I'm familiar with I'm afraid.