This kind of thing really gets me going:
Industry: IT
Type: Contract/Permanent
Position: Enterprise Architect
Skills: Excellent opportunity in Baltimore for an experienced
Enterprise Architect. This is a temp to perm position. You will be
required to design architecture and develop enterprise applications
using J2EE, JBoss, ANT and Oracle PL/SQL. Must have ability to write
system and integrated test cases and Datamodelling. Ability to provide
technical oversight to one or more Java/J2EE Programmers. Manage
large-scale projects to coordinate cross functional groups and project
plans. You will lead the effort to…
Location: Baltimore, MD
They obviously want a Solutions Architect in the Enterprise context.
It would be really nice if we could get our own definitions is order so that the rest of the industry could use them. It leads to all sorts of misunderstandings and mis-alignments of concepts. I personally think this is one of the reasons for establishing Process webs, so that the terminology starts becoming more standard.
Does anyone else have any strong feelings about this type of thing?
