The IT Grind


Latest Post | Last 10 Posts | Archives


Previous Post: No rest for the weary techie
Next Post: Is there a better way to be handed a pink slip?

My Awesome IT Job: Enterprise Architect, IBM

Posted in:

Hey, we all complain about work from time to time; we've all had lousy jobs. But before you call it a day and head off to the support group that meets at the bar, here are a few words from an IT pro that loves their work.
Name: Martine Combes Location: Paris, La Defense - France Profession and specialization: I am Enterprise Architect in IBM and recertified Consulting IT specialist in Business Analysis. I am reporting to the IBM CIO organisation and I lead architecture in Europe. I have thirty years of experience in various domains, like project management, Business Architecture and implementations of SAP and CRM Siebel. Hobby: I have the chance to live in Paris that I love. I like to stroll in Paris streets, comparing old Paris from past pictures with the modern Paris, taking photographs on my turn; Paris streets are a changing scenery across the centuries. I also read books where I can discover and learn about the History and stories of these different places, and I love visiting the antiques to unearth old books. There is also a literary geography provided by novels where we can discover streets and quarters as described by great novelists. This is this secret and ghost Paris that I either physically discover or virtually across old picture and novel pages. I am just at the starting point of assembling my personal discovery in a book. Last book read: Paris: The Secret History, by Andrew Hussey Latest accomplishment: Being part of the IBM CIO organization, I am involved in internal large initiatives of Business Transformation and IT programs at the global level. This includes participation to the definition of the strategic enterprise architecture, building the transition architecture at global and geography/ Europe levels, performing architecture reviews with teams of architects and executives. Within a large company, application architecture tend to be complex, because of the weight of the history and legacy applications that were developed to support a specific process and specific set of offerings. Toughest technology lesson learned: Architecture is one thing, delivery is another thing. You can design wonderful architecture on the paper, but which can reveal at the end quite challenging and very expensive to execute. ...It is very easy to become overwhelmed by complexity and it is very difficult to maintain simplicity, especially when the scope is large, the number of team members is high. So better to have a simple architecture from the start, clearly showing the benefits for the Business. Advice to an up-and-comer: [Know someone who thinks their IT job is awesome? Introduce them to me at debperelman [at] gmail [dot] com.]

posted by Deb Perelman
October 31, 2008 @ 4:03 pm

Previous Post: No rest for the weary techie
Next Post: Is there a better way to be handed a pink slip?


Last 10 posts:

more Posts (Archives)

WordPress Mobile Edition available at alexking.org.

powered by WordPress.