Tips For Software Architects
1.Dont Put Your Resume Ahead of the Requirements
2. Simplify Essential Complexity Diminish Accidental Complexity
3. Chances Are Your Biggest Problem Isnt Technical
4. Communication Is King Clarity and Leadership Its Humble Servants
5. Application Architecture Determines Application Performance
6. Seek the Value in Requested Capabilities
7. Stand Up
8. Everything Will Ultimately Fail
9. Empower Developers
10. Record Your Rationale
11. Challenge AssumptionsEspecially Your Own
12. Share Your Knowledge and Experiences
13. Pattern Pathology
14. Dont Stretch the Architecture Metaphors
15. Focus on Application Support and Maintenance
16. Prepare to Pick Two
17. Youre Negotiating More Often Than You Think
18. Quantify
19. One Line of Working Code Is Worth 500 of Specification
20. There Is No OneSizeFitsAll Solution
21. Its Never Too Early to Think About Performance
22. Architecting Is About Balancing
23. CommitandRun Is a Crime
24. There Can Be More Than One
25. Business Drives
26. Simplicity Before Generality Use Before Reuse
27. Architects Must Be Hands On
28. Continuously Integrate
29. Avoid Scheduling Failures
30. Architectural Tradeoffs
31. Database As a Fortress
32. Use Uncertainty As a Driver
33. Problems in Mirror May Be Larger Than They Appear
34. Reuse Is About People and Education Not Just Architecture
35. There Is No I in Architecture
36. Get the 1000Foot View
37. Try Before Choosing
38. Understand the Business Domain
39. Programming Is an Act of Design
40. Give Developers Autonomy
41. Time Changes Everything
42. Software Architect Has Only Lowercase as Deal with It
43. Scope Is the Enemy of Success
44. Value Stewardship Over Showmanship
45. Software Architecture Has Ethical Consequences
46. Skyscrapers Arent Scalable
47. Heterogeneity Wins
48. Its All About Performance
49. Engineer in the White Spaces
50. Talk the Talk
51. Context Is King
52. Dwarves Elves Wizards and Kings
53. Learn from Architects of Buildings
54. Fight Repetition
55. Welcome to the Real World
56. Dont Control but Observe
57. Janus the Architect
58. Architects Focus Is on the Boundaries and Interfaces
59. Prefer Principles Axioms and Analogies to Opinion and Taste
60. Start with a Walking Skeleton
61. It Is All About The Data
62. Make Sure the Simple Stuff Is Simple
63. Before Anything an Architect Is a Developer
64. The ROI Variable
65. Your System Is Legacy Design for It
66. If There Is Only One Solution Get a Second Opinion
67. Understand the Impact of Change
68. You Have to Understand Hardware Too
69. Shortcuts Now Are Paid Back with Interest Later
70. Perfect Is the Enemy of Good Enough
71. Avoid Good Ideas
72. Great Content Creates Great Systems
73. The Business Versus the Angry Architect
74. Stretch Key Dimensions to See What Breaks
75. If You Design It You Should Be Able to Code It
76. A Rose by Any Other Name Will End Up As a Cabbage
77. Stable Problems Get HighQuality Solutions
78. It Takes Diligence
79. Take Responsibility for Your Decisions
80. Dont Be Clever
81. Choose Your Weapons Carefully Relinquish Them Reluctantly
82. Your Customer Is Not Your Customer
83. It Will Never Look Like That
84. Choose Frameworks That Play Well with Others
85. Make a Strong Business Case
86. Control the Data Not Just the Code
87. Pay Down Your Technical Debt
88. Dont Be a Problem Solver
89. Build Systems to Be Zuhanden
90. Find and Retain Passionate Problem Solvers
91. Software Doesnt Really Exist
92. Learn a New Language
93. You Cant FutureProof Solutions
94. The User Acceptance Problem
95. The Importance of Consommé
96. For the End User the Interface Is the System
97. Great Software Is Not Built It Is Grown
Source:
Amazon:
Turkish:
