I found a great blog entry today by Frank Kelly called How to spot the dreaded non-coding architect (NCA), which is about some of the differences between architects that can code and architects that can't (or don't). Since this site is about "coding the architecture", I thought you might find it interesting too.
These NCA folks can be really quite dangerous and give dev teams a bad name ... But how can you spot one? For most developers it's pretty easy but just in case you can't I've compiled a list of example scenarios that should help - comparing the often dogmatic attitude of the NCA with the pragmatism of the experienced Coding Architect (CA).
Recommended reading and a little humour to brighten up your Monday.