“Architect” – It’s one of the most overly used, abused and least understood of software engineering roles. Every senior developer thinks they are one. Many aspire to become one. The rest can’t stand them. The word takes on a totally different meaning if prefixed with development, solution or enterprise. It gets even more divided when referring to architects for technologies (i.e., UI architect, Java architect, etc.). The topic is hardly covered in formal education and every new meetup/conference will give you their perspective.
Well, Mike and Rajesh have their views on it, too. Attend this Tech Talk to learn more about what being an architect really means, their role in the organization, their responsibilities and the blind spots that budding architects can fall into.