Presented by Chris Deweese
Photography by Jeremy West
Accepting my responsibility as an architect I will
strive daily to learn and perfect my trade.
Readily will I defend my organizations IT
investments from complexity, our greatest enemy.
Changing requirements will not break my design for it will
be flexible and able to change with the requirements.
Helping developers to understand the reasons for the
architecture and seeking their input is of great
importance to our su...
I will never use acronyms or suggest technologies that
are not pertinent to the problem at hand.



                      ...
Technologies evolve and I know that solid architectures
should accommodate and enable these evolutions.
Every day I will strive to help our software achieve ideals
that will make it flexible and easy to maintain.
Concern for the success of my organizations IT
investments will drive me to make appropriate decisions.
Teaching others about my trade will be an overarching
responsibility that I accept as part of my duties.
The Software Architect’s Creed
    Accepting my responsibility as an architect I will strive daily to learn and

    perf...
Contact / Photo Credits

    Chris Deweese

     http://christopherDeweese.com
     Twitter: @cdeweese


    Photo Cred...
Software Architects Creed
Software Architects Creed
Upcoming SlideShare
Loading in …5
×

Software Architects Creed

2,171 views
1,998 views

Published on

Nine action statements you can take with you and apply to be a better software architect.

Published in: Technology, Business
4 Comments
5 Likes
Statistics
Notes
No Downloads
Views
Total views
2,171
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
57
Comments
4
Likes
5
Embeds 0
No embeds

No notes for slide

Software Architects Creed

  1. Presented by Chris Deweese Photography by Jeremy West
  2. Accepting my responsibility as an architect I will strive daily to learn and perfect my trade.
  3. Readily will I defend my organizations IT investments from complexity, our greatest enemy.
  4. Changing requirements will not break my design for it will be flexible and able to change with the requirements.
  5. Helping developers to understand the reasons for the architecture and seeking their input is of great importance to our success.
  6. I will never use acronyms or suggest technologies that are not pertinent to the problem at hand. MVC MSMQ SOA SRP DDD TDD WS-* BDD TOGAF REST ATOM IoC FEA MEF
  7. Technologies evolve and I know that solid architectures should accommodate and enable these evolutions.
  8. Every day I will strive to help our software achieve ideals that will make it flexible and easy to maintain.
  9. Concern for the success of my organizations IT investments will drive me to make appropriate decisions.
  10. Teaching others about my trade will be an overarching responsibility that I accept as part of my duties.
  11. The Software Architect’s Creed Accepting my responsibility as an architect I will strive daily to learn and  perfect my trade. Readily will I defend my organizations IT investments from  complexity, our greatest enemy. Changing requirements will not break my design for it will be flexible and  able to change with the requirements. Helping developers to understand the reasons for the architecture and  seeking their input is of great importance to our success. I will never use acronyms or suggest technologies that are not pertinent  to the problem at hand. Technologies evolve and I know that solid architectures should  accommodate and enable these evolutions. Every day I will strive to help our software achieve ideals that will make it  flexible and easy to maintain. Concern for the success of my organizations IT investments will drive me  to make appropriate decisions. Teaching others about my trade will be an overarching responsibility that  I accept as part of my duties.
  12. Contact / Photo Credits Chris Deweese   http://christopherDeweese.com  Twitter: @cdeweese Photo Credits   Jeremy West http://www.flickr.com/photos/28119858@N07/

×