Monday, September 22, 2008

97 Things Every Software Architect Should Know

Some highlights:
1. Don't put resume ahead of requirements

SOA == WebSerices came from above.

2. Chances are you biggest problem is not technical

3. Learn from Architect of Buildings.
Survic is not going to like this one

4.


My Additions:
1. User Interface rules. Ignore it at your peril.

http://97-things.near-time.net/wiki/show/97-things-every-software-architect-should-know-the-book

A period of stability

Rocky says In both those cases there was a 5-6 year window when the platforms were slow-changing, the dev tools were mature, and disru...