Document:
ramjee / jackass_solutions_arch.html
>>> I don't^H^H^H know jackass^H^H^H^H^H^H^H about 'solution architecture!'
This is a feedback from Chandrashekar Ramanathan (dr_shekar at hotmail dot com):
Hi Ramjee,
For once, I am really going to throw some brickbats!
- Going by the underlying theme of the write-up, I agree for most part with each of the basic assertions but do not agree with the circus analogy that goes with it. I do not agree that architects' and circus performers' "job profiles" are comparable. By definition, architects do not dirty their hands (mind you, I am not saying this is right or wrong!). Even in circus, they do have veteran trainers who drive the performance. The trainers are the ones who "architect" the show.
- I strongly agree with "kick on the rear side" theme. Architects tend to get away too easily! They should be held accountable for their "creations". I actually see many orgs these days insisting on this by requiring the consultants to stay throughout the lifecycle!
- You have brought about a valid dilemma with respect to hands-on skills of the architect but I do not agree with the thesis there. I think this is not just limited to software architects. If wanna-be architects keep learning new languages and API's that keep getting churned out, they will never ever have the time to "grow"! I came across a real-life case on this one during an interview I was conducting. A guy was working in the US for over 6 years. All he was doing was coding, coding and more coding (no wonder because he was in the *US* all along!). He knows the nuances of VC++ inside out. His answers on the language were spot on. I just stepped up one level and asked him a few basic stuff on design. Trust me, it just involved judicious use of inheritance... nothing more. He could not comprehend what I was asking and what I was talking about. He was not familiar with even some "standard" terminology (not jargons mind you!). My point is that an architect should have definitely had strong hands-on in the *past*. On the other hand, a designer must necessarily have coding knowledge in the *current* environment.
It is impossible (IMVHO) to be strong hands-on in latest technologies and at the same time be able to step back and be able tell how to use the technologies. There are way too many things happening in technology for that to be possible. Yes, I am a bit defensive because I cannot, for example, write a TIBCO adapter for a SAP/R3 implementation. I have seen neither of those! But would that make me less effective as an architect? If it does, too bad, the IT industry will have to live with people like me :-) I think the circus trainer will agree with me :)
==========
All the same, Ramjee, it is a great piece of write-up to kick start an introspection ride. That actually kept me going during my 18 hour train ride from Trivandrum to Bangalore!
Best regards,
Shekar
all rites reversed 2003ramjee
(ramjee swaminathan)
1:24 PM 2/5/2004