احتمالاْ این نوشته، طولانی‌ترین نوشته وبلاگ خواهد شد.
فهرست زیر شامل نود و هفت پند و ارز است برای معماران نرم‌افزار که توسط تعدادی از خود آنان نوشته شده است.
این متن را خانم ملکوتی‌خواه برایم ارسال نموده‌اند که صمیمانه از ایشان تشکر کرده و برایشان آرزوی توفیق دارم.
The following are axioms for software architects by software architects.
The following are the 97 axioms selected for the book, 97 Things Every Software Architect Should Know, which will be published by O’Reilly Media in early 2009.
۱. Don’t put your resume ahead of the requirements by Nitin Borwankar
۲. Simplify essential complexity; diminish accidental complexity by Neal Ford
۳. Chances are your biggest problem isn’t technical by Mark Ramm
۴. Communication is King by Mark Richards
۵. Architecting is about balancing by Randy Stafford
۶. Always ask for the value to be provided by a requested capability by Einar Landre
۸. Talk about the arch, but se the scaffolding beneath it by Micheal Nygard
۹. You’re negotiating more often than you think by Michael Nygard
۱۰. Quantify by Keith Braithwaite
۱۱. One line of working code is worth 500 of specification by Allison Randal
۱۲. There is no one-size-fits-all solution by Randy Stafford
۱۳. It’s never too early to think about performance and resiliency testing by Rebecca Parsons
۱۴. Application architecture determines application performance by Randy Stafford
۱۵. Commit-and-run is a serious crime. Respect your Colleagues by Niclas Nilsson
۱۶. There Can be More than One by Keith Braithwaite
۱۷. Business Drives by Dave Muirhead
۱۸. Simplicity before generality, use before reuse by Kevlin Henney
۱۹. Architects must be hands on by John Davies
۲۰. Continuously Integrate by Dave Bartlett
۲۱. Sometimes it’s better to let the train pass you by by Norman Carnovale
۲۲. Architectural Tradeoffs by Mark Richards
۲۳. Database as a Fortressby Dan Chak
۲۴. Use uncertainty as a driver by Kevlin Henney
۲۵. Scope is the enemy of success by Dave Quick
۲۶. Reuse is about people and education, not just architecture by Jeremy Meyer
۲۷. There is no ‘I’ in architecture by Dave Quick
۲۸. Get the 1000ft view by Erik Doernenburg
۲۹. Try before choosing by Erik Doernenburg
۳۰. Understand The Business Domain by Mark Richards
۳۱. Programming is an act of design by Einar Landre
۳۲. Time changes everything by Philip Nelson
۳۳. Take the hill! by Philip Nelson
۳۴. Value stewardship over showmanship by Barry Hawkins
۳۵. If you’re unwilling to be hands-on, maybe you should keep your hands off by Barry Hawkins
۳۶. The title of software architect has only lower-case ‘a’s; deal with it by Barry Hawkins
۳۷. Software architecture has ethical consequences by Michael Nygard
۳۸. Everything will ultimately fail by Michael Nygard
۳۹. Context is King by Edward Garson
۴۰. It’s all about performance by Craig L Russell
۴۱. Engineer in the white spaces by Michael Nygard
۴۲. Talk the Talk by Mark Richards
۴۳. Heterogeneity Wins by Edward Garson
۴۴. Dwarves, Elves, Wizards, and Kings by Evan Cofsky
۴۵. Learn from Architects of Buildings by Keith Braithwaite
۴۶. Fight repetition by Niclas Nilsson
۴۷. Welcome to the real world by Gregor Hohpe
۴۸. Don’t Control, but Observe by Gregor Hohpe
۴۹. Architect as Janitor by Dave Bartlett
۵۰. Architects focus is on the boundaries and interfaces by Einar Landre
۵۱. Challenge assumptions – especially your own by Timothy High
۵۲. Record your rationale by Timothy High
۵۳. Empower developers by Timothy High
۵۴. It is all about the data by Paul W. Homer
۵۵. Control the data, not just the code by Chad LaVigne
۵۶. Architecture Metaphors Can Only Be Stretched As Far As A, Um, Stretchy Thing by David Ing
۵۷. If the application can’t be supported, the project is a failure by Mncedisi Kasper
۵۸. Lead by Influence by Travis Illig
۵۹. Prefer principles, axioms and analogies to opinion and taste by Michael Harmer
۶۰. From Pencil Neck Geek to Mr. Olympia by Clint Shank
۶۱. Share your knowledge and experiencesby Paul W. Homer
۶۲. Make sure the simple stuff is simple by Chad LaVigne
۶۳. If you design it, you should be able to code it by Mike Brown
۶۴. The ROI variable by George Malamidis
۶۵. Your system is legacy, design for it by Dave Anderson
۶۶. If there is only one solution, get a second opinion by Timothy High
۶۷. Requirements are not the measure of success but the beginnings of a conversation by Christopher Dempsey
۶۸. Capacity to implement is as important as knowing how to implement by Kamal Wickramanayake
۶۹. Shortcuts now are paid back with interest later by Scot Mcphee
۷۰. “Perfect” is the Enemy of “Good Enough” by Greg Nyberg
۷۱. Avoid “Good Ideas” by Greg Nyberg
۷۲. Great content creates great systems by Zubin Wadia
۷۳. The Business Vs. The Angry Architectby Chad LaVigne
۷۴. Stretch key dimensions to see what breaks by Stephen Jones
۷۵. Before anything, an architect is a developer by Mike Brown
۷۶. A rose by any other name will end up as a cabbage by Sam Gardiner
۷۷. Stable problems get high quality solutions by Sam Gardiner
۷۸. Diligence and the Mundane by Brian Hart
۷۹. Take responsibility for your decisions by Yi Zhou
۸۰. Dont Be a Problem Solver by Eben Hewitt
۸۱. Software Should Be Invisible by Eben Hewitt
۸۲. Your Customer is Not Your Customer by Eben Hewitt
۸۳. It will never look like that by Peter Gillard-Moss
۸۴. Choose Frameworks that play well with others by Eric Hawthorne
۸۵. Making a strong business case by Yi Zhou
۸۶. The insidious pattern bug by Chad LaVigne
۸۷. Learn a new language by Burk Hufnagel
۸۸. Dont Be Clever by Eben Hewitt
۸۹. Build Systems to be Zuhanden by Keith Braithwaite
۹۰. Employ developers that are recognition motivated by Chad LaVigne
۹۱. Software doesnt really exist by Chad LaVigne
۹۲. Pay down your technical debt by Burk Hufnagel
۹۳. You can’t future-proof solutions by Richard Monson-Haefel
۹۴. Interaction Design is Critical by Richard Monson-Haefel
۹۵. The Importance of Consommé by Eben Hewit
۹۶. For the end-user, the interface is the system by Vinayak Hegde
۹۷. Great software is not built, it is grown by Bill de hÓra
گزیده:
Modeling Principle: Design a model so that the most frequent modification of the model causes changes to the least number of types. Martin Fowler, Analysis Pattern
دیدگاهتان را بنویسید