Completely buried with two projects and the main one is going to CTP #2 at a major back in Paris/London next week so going to scrape this together quickly. I have also been pairing with Steve back on the main project on solving performance problems - yesterday, he and I optimized a section of the system where an operation was taking 25 to 30 minutes and got it down to 30 seconds! Now that's a good boost! I have much in my head concerning where we are at and my current feelings on being agile, architecture and such but they will have to wait. I tried to blog about the Apple iPhone announcement but couldn't muster up enough interest... Architecture and SOA, Agile SOA and BI Impendence Mismatch Arnon has great comments on a presentation (via Shahid Sah's blog) by Ron Jacobs on the Software Architect's Role. he says, "In this presentation, entitled Architects and the Architecture of Software , Ron compares the architect's role to that of an explorer, advocate, and designer," and "However, I would personally replace "advocate" with "mentor", and "explorer" with a "polymath" or "Renaissance" man. I'd also add a leader and visionary (although Ron mentions that as part of the discussion on explorer)." I agree with his additions, at least how I see my role. He also has some outstanding comments on Agile Iterations and what I really want to write about (and finding) when I have time: "To me, that is just a reminder why JEDUF is important. I find that in projects that are large or overly complex "sacrificing" one, two, or even three iterations for handling technical risks and forming a candidate architecture goes a long way ( and I don't care if this makes my project not agile. I am fine if it is pliant , lagum or what-not)." I am actually finding its quite a bit more than 1-3 Iterations depending on the project and environment. Actually this ties in with Jim's Design Maps . Cazz on Building Software Factories Today Richard Venyard on SOA Algebra WCF/Indigo Harry finds Indigo daunting
Read More...