One should not wait for permission to work on something important to the enterprise.Īs technical employees become more capable and integral to successful business outcomes, they naturally become more able to identify and solve problems that are impactful to the enterprise. This isn’t an architectural principle, rather it is a career-path principle. I want to tell you about a principle I finally stumbled across after many years of overlooking it in my career. TOGAF 9.1, one of the leading standards in Enterprise Architecture, defines architecture principles as "general rules and guidelines, intended to be enduring and seldom amended, that inform and support the way in which an organization sets about fulfilling its mission.” Principles help us decide between seemingly equally appealing courses of action. You see, the reason I mistyped this word is that in Enterprise Architecture, ‘principle’ is a very important idea, so much so that my fingers naturally wanted to type p-r-i-n-c-i-p-l-e. As I was correcting my grammatical faux pas, I realized that this might be the perfect topic for my first ever blog post as an official Rackspace technical leader. I’m embarrassed to tell you that when I changed my LinkedIn profile, I misspelled ‘principal architect’ as ‘principle architect’. What is the TCT? Here is Rackspace’s answer: "The TCT Program is a technical leadership program designed to identify, develop and target the very best technical resources in Rackspace on our top challenges, providing value to the business and meaningful challenges to employees.” This weekend I finally changed my LinkedIn title to reflect my recent promotion at Rackspace to ‘Principal Architect.’ I have to tell you that I am really very honored to be included among the other leading architects and engineers at Rackspace who are members of the technical career track (TCT) at Rackspace.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |