97 Things Every Software Architect Should Know > Start with a Walking Skeleton - Pg. : Safari Books Online

Table of Contents

Download Safari Books Online apps: Apple iOS | Android

Entire Site

Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.

This Book

97 Things Every Software Architect Should Know

97 Things Every Software Architect Should Know

Search

Contents

Ch. 1. Don't Put Your Resume Ahead of the Requirements

Ch. 2. Simplify Essential Complexity; Diminish Accidental Complexity

Ch. 3. Chances Are, Your Biggest Problem Isn't Technical

Ch. 4. Communication Is King; Clarity and Leadership, Its Humble Servants

Ch. 5. Application Architecture Determines Application Performance

Ch. 6. Seek the Value in Requested Capabilities

Ch. 7. Stand Up!

Ch. 8. Everything Will Ultimately Fail

Ch. 9. You're Negotiating More Often Than You Think

Ch. 10. Quantify

Ch. 11. One Line of Working Code Is Worth 500 of Specification

Ch. 12. There Is No One-Size-Fits-All Solution

Ch. 13. It's Never Too Early to Think About Performance

Ch. 14. Architecting Is About Balancing

Ch. 15. Commit-and-Run Is a Crime

Ch. 16. There Can Be More Than One

Ch. 17. Business Drives

Ch. 18. Simplicity Before Generality, Use Before Reuse

Ch. 19. Architects Must Be Hands On

Ch. 20. Continuously Integrate

Ch. 21. Avoid Scheduling Failures

Ch. 22. Architectural Tradeoffs

Ch. 23. Database As a Fortress

Ch. 24. Use Uncertainty As a Driver

Ch. 25. Warning: Problems in Mirror May Be Larger Than They Appear

Ch. 26. Reuse Is About People and Education, Not Just Architecture

Ch. 27. There Is No 'I' in Architecture

Ch. 28. Get the 1,000-Foot View

Ch. 29. Try Before Choosing

Ch. 30. Understand the Business Domain

Ch. 31. Programming Is an Act of Design

Ch. 32. Give Developers Autonomy

Ch. 33. Time Changes Everything

Ch. 34. "Software Architect" Has Only Lowercase a's; Deal with It

Ch. 35. Scope Is the Enemy of Success

Ch. 36. Value Stewardship Over Showmanship

Ch. 37. Software Architecture Has Ethical Consequences

Ch. 38. Skyscrapers Aren't Scalable

Ch. 39. Heterogeneity Wins

Ch. 40. It's All About Performance

Ch. 41. Engineer in the White Spaces

Ch. 42. Talk the Talk

Ch. 43. Context Is King

Ch. 44. Dwarves, Elves, Wizards, and Kings

Ch. 45. Learn from Architects of Buildings

Ch. 46. Fight Repetition

Ch. 47. Welcome to the Real World

Ch. 48. Don't Control, but Observe

Ch. 49. Janus the Architect

Ch. 50. Architects' Focus Is on the Boundaries and Interfaces

Ch. 51. Empower Developers

Ch. 52. Record Your Rationale

Ch. 53. Challenge Assumptions—Especially Your Own

Ch. 54. Share Your Knowledge and Experiences

Ch. 55. Pattern Pathology

Ch. 56. Don't Stretch the Architecture Metaphors

Ch. 57. Focus on Application Support and Maintenance

Ch. 58. Prepare to Pick Two

Ch. 59. Prefer Principles, Axioms, and Analogies to Opinion and Taste

Ch. 60. Start with a Walking Skeleton

Ch. 61. It Is All About The Data

Ch. 62. Make Sure the Simple Stuff Is Simple

Ch. 63. Before Anything, an Architect Is a Developer

Ch. 64. The ROI Variable

Ch. 65. Your System Is Legacy; Design for It

Ch. 66. If There Is Only One Solution, Get a Second Opinion

Ch. 67. Understand the Impact of Change

Ch. 68. You Have to Understand Hardware, Too

Ch. 69. Shortcuts Now Are Paid Back with Interest Later

Ch. 70. "Perfect" Is the Enemy of "Good Enough"

Ch. 71. Avoid "Good Ideas"

Ch. 72. Great Content Creates Great Systems

Ch. 73. The Business Versus the Angry Architect

Ch. 74. Stretch Key Dimensions to See What Breaks

Ch. 75. If You Design It, You Should Be Able to Code It

Ch. 76. A Rose by Any Other Name Will End Up As a Cabbage

Ch. 77. Stable Problems Get High-Quality Solutions

Ch. 78. It Takes Diligence

Ch. 79. Take Responsibility for Your Decisions

Ch. 80. Don't Be Clever

Ch. 81. Choose Your Weapons Carefully, Relinquish Them Reluctantly

Ch. 82. Your Customer Is Not Your Customer

Ch. 83. It Will Never Look Like That

Ch. 84. Choose Frameworks That Play Well with Others

Ch. 85. Make a Strong Business Case

Ch. 86. Control the Data, Not Just the Code

Ch. 87. Pay Down Your Technical Debt

Ch. 88. Don't Be a Problem Solver

Ch. 89. Build Systems to Be Zuhanden

Ch. 90. Find and Retain Passionate Problem Solvers

Ch. 91. Software Doesn't Really Exist

Ch. 92. Learn a New Language

Ch. 93. You Can't Future-Proof Solutions

Ch. 94. The User Acceptance Problem

Ch. 95. The Importance of Consommé

Ch. 96. For the End User, the Interface Is the System

Ch. 97. Great Software Is Not Built, It Is Grown

URL

Help

Chapter 60. Start with a Walking Skeleton

Clint Shank is a software developer, consultant, and mentor at Sphere of Influence, Inc., a software design and engineering services company for commercial and federal clients.
—Clint Shank

You are currently reading a PREVIEW of this book.

Get instant access to over
$1 million worth of books and videos.

Start a Free Trial