As a software architect for the last ~10 years I have to disagree.  His point seems to be that if you get a job as a software architect you'll end doing nothing but meetings and creating UML diagrams.  I'm sure there are places like that, I've worked at one (Rational Process - shudder), but there are many places where they need someone who can provide architect level application design, who can see the forest through the trees, who can balance the needs of the business, the 3rd party integrations, and the technology.  My current contract role has me providing architecture (usually just a 1-2 page design doc, not often UML), mentorship, and coding some of the trickier stuff.<p>I still code a lot, but I also have responsibility over the whole software ecosystem and hence some power to decide how things go.  I mentor developers, perform code reviews, and work on process improvement too.  It's a great role.