Other Things Software Architects Should Know
The axioms have been accepted into the web project but not the 97 Things book
1. Architects should be Pragmatic
2. Applications are for making users as effective as possible
3. Community
4. Know all the rules — so you know which ones you’re breaking
5. Not all problems are solved with a layer of abstraction
6. Learn to be humble
7. Architecture is more than just the pieces
8. Responsible explorer
9. Design for limited resources
10. The fastest system components are the one’s that aren’t there
11. The closer the better
12. It’s not an architecture if it can’t be managed
13. Your project does not exist in a vacuum
14. Design for needs, not wants
15. Consider application failures, and design for ease of recovery
16. Risk priority
17. Test the Architecture
18. An architect’s responsibility never finishes after the architecture is created
19. Change is a constant; architecture needs to be adaptable and the architect needs to be a change driver
20. One alternative is a trap, two are a dilemma, three are freedom
21. Work on thy soft skills just as much as on your hard skills
22. Examine the sourcing of calculated fields
23. Feel it
24. No, the goal is not the code nor the design
25. Quality is a feature
26. Good Requirements Are Boring
27. Don’t Make Worlds, Make Containers for Worlds
28. Architecture = SPICE RTM
29. Know your limitations
30. Tarchitects vs. Marketects vs. Carhitects
31. Read Philoophy (and related Arts)
32. Prioritize Challenges to Drive Architecture Decisions
33. Reduce Conceptual Distance
34. The User Interface drives the User Experience
35. If you’re unwilling to be hands-on, maybe you should keep your hands off
36. Lead by Influence
37. Software Should Be Invisible
38. Requirements are not the measure of success but the beginnings of a conversation
