Standardization, it should make our lives easier. For webservices the opposite becomes true. The stack of standards is growing very fast since SOAP and WSDL where introduced. I'm working on a list of all web service standards for a couple of weeks now, categorizing them and shortly describe their purpose.
Architecture, Architecting and Architect, terms heard a lot nowadays. A couple of years ago we called someone programming software applications a programmer, now such a person is called a Solution Architect. Much more examples can be given according to the number of job descriptions containing the word ‘Architect'. Yes, I have to admit, my contract also states that I am an Architect. However, if the work an Architect does is architecting and the result of that work is an architecture, most job descriptions seems to be a little bit inaccurate in my opinion. To make that more clear, I will define what the architecture of a system is.