Oct 23, 2009

Architecture in the Small Presentation

Last night I was privileged to be the first speaker at the newly formed Sydney Architecture User Group put together by Paul Glavich (@glav) and Omar Besiso (@omarbesiso) and sponsored by Datacom.

There was a strong turnout and plenty of people in the audience willing to ask questions.  I’ve uploaded my slide deck from last night to Slideshare in case you weren’t able to make it there in person or you just wanted to go back over it for yourself.


  1. Hi Richard

    Great talk last night, thoroughly enjoyed it and looking forward to the next one. Thanks for the slides.


  2. Hey Richard - great presentation, and sorry I missed the meeting.

    I would challenge you on one thing, and that's the type of architect. Application Architects need to code, perhaps.

    Saying all architects need to code is like saying that all construction architects need to lay bricks, mix cement, be electricians, install plumbing.

    Not all IT architects need to code, in the same way they don't all need to lay cabling, configure and connect SANS, design VLAN's and DNS hierarchies. Yes, they do need to understand all of the impacts of the technology (and the business) and be able to communicate to the tech leads of those disciplines, in their language. They also need to lead by empowering their technical teams, and trusting them to write secure, maintainable, efficient code - or design secure, simple, maintainable networks - or implement efficient, maintainable, identity directories - or configure affordable, scalable, and maintainable storage systems, etc.

    Like I said, great presentation, but Application Architecture specific. I believe, evidenced in a number of industries, that architect is a different role from engineer, and not necessarily a superlative or subsequent role (although very often in IT this is the career path proposed).

    Architecture skills, dealing with ambiguity, communication, the top-down/bottom-up dilemma you describe so well, are different to engineer (developer) skills. They need to be, and the one doesn't precede or preclude, the other.

    Good work though - I'd love to see more of the group. Check out the Australasian Enterprise Architecture Group on LinkedIn.

  3. The moron has left the building.

  4. Good stuff, thanks for the post. Marketing and sales are essentially educational activities. The starting point in both is that the prospective client doesn't KNOW enough in order to make a POSITIVE decision. The bigger the decision is, the more steps you need as the ability of people to absorb information sets definite limits to how much data you can give at any one time. Imagine a staircase that you have to get the prospect to climb on his own willingness.