Software Technology Architect

I got a chance to search for the things that a software architect should be capable of and I came across the following link from O'Reilly. http://architect.97things.oreilly.com/wiki/index.php/97_Things_Every_Software_Architect_Should_Know_-_The_Book. It has many topics and I first looked into "Architects must be hands on". It really impressed me. Thanks a lot to the author of that topic. I liked few points that I enlisted below. - Architects should be bought into the team at the earliest part of the project. - Architects should not sit in an ivory tower dictating the way forward. - An architect is like an airline pilot, he might not look busy all of the time. - Architect should have responsibility for the delivery and quality of the projects. They gave clear picture on the roles of a software architect. There are two ultimate statements we can never miss. I copied them below. (1)The project manager (co-pilot) performs the day-to-day management tasks leaving the architect ...