97 Things Every Software Architect Should Know
없습니다
도서+교보Only(교보배송)을 함께 15,000원 이상 구매 시 무료배송
15,000원 미만 시 2,500원 배송비 부과
20,000원 미만 시 2,500원 배송비 부과
15,000원 미만 시 2,500원 배송비 부과
1Box 기준 : 도서 10권
알립니다.
- 본 상품은 주문 후 제작되는 맞춤도서입니다.
주문기간에 따라 도서 출고일은 영업일 기준 최소 3일에서 최대 8일이 소요됩니다. - 해외주문도서는 고객님의 요청에 의해 주문하는 '개인 오더' 상품이기 때문에, 단순한 고객변심/착오로 인한 취소, 반품, 교환의 경우 '해외주문 반품/취소 수수료'를 부담하셔야 합니다. 이점 유의하여 주시기 바랍니다.
- 반품/취소 수수료:(1)서양도서-판매정가의 12%, (2)일본도서-판매정가의 7% (반품/취소 수수료는, 수입제반비용(FedEx수송비용, 관세사비, 보세창고료, 내륙 운송비, 통관비 등)과 재고리스크(미판매 리스크, 환차손)에 따른 비용을 포함하며, 서양도서는 판매정가의 12%, 일본도서는 판매정가의 7%가 적용됩니다.)
- 외국도서의 경우 해외제공정보로만 서비스되어 미표기가된 정보가 있을 수 있습니다. 필요한 정보가 있을경우 1:1 문의게시판 을 이용하여 주십시오.
취소/반품에 대한 안내
POD도서는 고객 주문 후 제작되는 도서로, 단순변심 및 착오로 인한 취소, 반품이 절대 불가하니 이점 반드시 유의하여 주시기 바랍니다.
해외주문/바로드림/제휴사주문/업체배송건의 경우 1+1 증정상품이 발송되지 않습니다.
패키지
북카드
Written by an expert in the field, this volume contains 97 things every software architect should know.
Richard Monson-Haefel is the author of Enterprise JavaBeans, 3rd Edition, Java Message Service and one of the world's leading experts and book authors on Enterprise Java. He is the lead architect of OpenEJB, an open source EJB container used in Apple Computer's WebObjects plateform, and has consulted as an architect on J2EE, CORBA, Java RMI and other distributed computing projects over the past several years.
Richard Monson-Haefel , an independent software developer, coauthored all five editions of Enterprise JavaBeans and Java Message Service (all O'Reilly). He's a software architect specializing in multi-touch interfaces and a leading expert on enterprise computing. More detail on his work and writings can be found at www.monson-haefel.com.
In this truly unique technical book, today's leading software architects present valuable principles on key development issues that go way beyond technology. More than four dozen architects -- including Neal Ford, Michael Nygard, and Bill de hOra -- offer advice for communicating with stakeholders, eliminating complexity, empowering developers, and many more practical lessons they've learned from years of experience. Among the 97 principles in this book, you'll find useful advice such as:Don't Put Your Resume Ahead of the Requirements (Nitin Borwankar) Chances Are, Your Biggest Problem Isn't Technical (Mark Ramm) Communication Is King; Clarity and Leadership, Its Humble Servants (Mark Richards) Simplicity Before Generality, Use Before Reuse (Kevlin Henney) For the End User, the Interface Is the System (Vinayak Hegde) It's Never Too Early to Think About Performance (Rebecca Parsons)To be successful as a software architect, you need to master both business and technology. This book tells you what top software architects think is important and how they approach a project. If you want to enhance your career, 97 Things Every Software Architect Should Know is essential reading.
97 Things represents a new kind of technical book. It's not about code; it's not about UML diagrams; and, it's about what really matters: the principles that the best software architects have pulled out of their experience. Benefit from their experience; find out what's really important. It's not always technology - in fact, it usually isn't. Communications with stakeholders, understanding requirements, eliminating complexity before it gets you tied up in knots - all of these trump technology issues. Many projects fail, but projects rarely fail because the developers chose to write in Python or Ruby or Java or C. Get into the mind of today's leading software architects! Find out what they think about when they're approaching a project. If you want to take your career in software development to the next level, this book is essential reading.
In this truly unique technical book, today's leading software architects present valuable principles on key development issues that go way beyond technology. More than four dozen architects -- including Neal Ford, Michael Nygard, and Bill de hOra -- offer advice for communicating with stakeholders, eliminating complexity, empowering developers, and many more practical lessons they've learned from years of experience. Among the 97 principles in this book, you'll find useful advice such as: Don't Put Your Resume Ahead of the Requirements (Nitin Borwankar) Chances Are, Your Biggest Problem Isn't Technical (Mark Ramm) Communication Is King; Clarity and Leadership, Its Humble Servants (Mark Richards) Simplicity Before Generality, Use Before Reuse (Kevlin Henney) For the End User, the Interface Is the System (Vinayak Hegde) It's Never Too Early to Think About Performance (Rebecca Parsons) To be successful as a software architect, you need to master both business and technology. This book tells you what top software architects think is important andhow they approach a project. If you want to enhance your career, 97 Things Every Software Architect Should Knowis essential reading.
In this truly unique technical book, today's leading software architects present valuable principles on key development issues that go way beyond technology. More than four dozen architects -- including Neal Ford, Michael Nygard, and Bill de hOra -- offer advice for communicating with stakeholders, eliminating complexity, empowering developers, and many more practical lessons they've learned from years of experience. Among the 97 principles in this book, you'll find useful advice such as:Don't Put Your Resume Ahead of the Requirements (Nitin Borwankar) Chances Are, Your Biggest Problem Isn't Technical (Mark Ramm) Communication Is King; Clarity and Leadership, Its Humble Servants (Mark Richards) Simplicity Before Generality, Use Before Reuse (Kevlin Henney) For the End User, the Interface Is the System (Vinayak Hegde) It's Never Too Early to Think About Performance (Rebecca Parsons)To be successful as a software architect, you need to master both business and technology. This book tells you what top software architects think is important and how they approach a project. If you want to enhance your career, 97 Things Every Software Architect Should Know is essential reading.
In this truly unique technical book, today's leading software architects present valuable principles on key development issues that go way beyond technology. More than four dozen architects -- including Neal Ford, Michael Nygard, and Bill de h ra -- offer advice for communicating with stakeholders, eliminating complexity, empowering developers, and many more practical lessons they've learned from years of experience. Among the 97 principles in this book, you'll find useful advice such as:Don't Put Your Resume Ahead of the Requirements (Nitin Borwankar) Chances Are, Your Biggest Problem Isn't Technical (Mark Ramm) Communication Is King; Clarity and Leadership, Its Humble Servants (Mark Richards) Simplicity Before Generality, Use Before Reuse (Kevlin Henney) For the End User, the Interface Is the System (Vinayak Hegde) It's Never Too Early to Think About Performance (Rebecca Parsons)To be successful as a software architect, you need to master both business and technology. This book tells you what top software architects think is important and how they approach a project. If you want to enhance your career, 97 Things Every Software Architect Should Know is essential reading.
Collective Wisdom from the Experts
In this truly unique technical book, today's leading software architects present valuable principles on key development issues that go way beyond technology. More than four dozen architects offer advice for communicating with stakeholders, eliminating complexity, empowering developers, and many more practical lessons they've learned from years of experience.
작가정보
목차
- Preface;Permissions;How to Contact Us;Safari® Books Online;Acknowledgments;Chapter 1: Don't Put Your Resume Ahead of the Requirements;Chapter 2: Simplify Essential Complexity; Diminish Accidental Complexity;Chapter 3: Chances Are, Your Biggest Problem Isn't Technical;Chapter 4: Communication Is King; Clarity and Leadership, Its Humble Servants;Chapter 5: Application Architecture Determines Application Performance;Chapter 6: Seek the Value in Requested Capabilities;Chapter 7: Stand Up!;Chapter 8: Everything Will Ultimately Fail;Chapter 9: You're Negotiating More Often Than You Think;Chapter 10: Quantify;Chapter 11: One Line of Working Code Is Worth 500 of Specification;Chapter 12: There Is No One-Size-Fits-All Solution;Chapter 13: It's Never Too Early to Think About Performance;Chapter 14: Architecting Is About Balancing;14.1 ;Chapter 15: Commit-and-Run Is a Crime;Chapter 16: There Can Be More Than One;Chapter 17: Business Drives;Chapter 18: Simplicity Before Generality, Use Before Reuse;Chapter 19: Architects Must Be Hands On;Chapter 20: Continuously Integrate;Chapter 21: Avoid Scheduling Failures;Chapter 22: Architectural Tradeoffs;Chapter 23: Database As a Fortress;Chapter 24: Use Uncertainty As a Driver;Chapter 25: Warning: Problems in Mirror May Be Larger Than They Appear;Chapter 26: Reuse Is About People and Education, Not Just Architecture;26.1 ;Chapter 27: There Is No 'I' in Architecture;Chapter 28: Get the 1,000-Foot View;Chapter 29: Try Before Choosing;Chapter 30: Understand the Business Domain;Chapter 31: Programming Is an Act of Design;Chapter 32: Give Developers Autonomy;Chapter 33: Time Changes Everything;33.1 ;Chapter 34: "Software Architect" Has Only Lowercase a's; Deal with It;Chapter 35: Scope Is the Enemy of Success;Chapter 36: Value Stewardship Over Showmanship;Chapter 37: Software Architecture Has Ethical Consequences;Chapter 38: Skyscrapers Aren't Scalable;Chapter 39: Heterogeneity Wins;Chapter 40: It's All About Performance;Chapter 41: Engineer in the White Spaces;Chapter 42: Talk the Talk;Chapter 43: Context Is King;Chapter 44: Dwarves, Elves, Wizards, and Kings;Chapter 45: Learn from Architects of Buildings;Chapter 46: Fight Repetition;Chapter 47: Welcome to the Real World;Chapter 48: Don't Control, but Observe;Chapter 49: Janus the Architect;Chapter 50: Architects' Focus Is on the Boundaries and Interfaces;Chapter 51: Empower Developers;Chapter 52: Record Your Rationale;Chapter 53: Challenge Assumptions-Especially Your Own;Chapter 54: Share Your Knowledge and Experiences;Chapter 55: Pattern Pathology;Chapter 56: Don't Stretch the Architecture Metaphors;Chapter 57: Focus on Application Support and Maintenance;Chapter 58: Prepare to Pick Two;Chapter 59: Prefer Principles, Axioms, and Analogies to Opinion and Taste;Chapter 60: Start with a Walking Skeleton;Chapter 61: It Is All About The Data;Chapter 62: Make Sure the Simple Stuff Is Simple;Chapter 63: Before Anything, an Architect Is a Developer;Chapter 64: The ROI Variable;Chapter 65: Your System Is Legacy; Design for It;Chapter 66: If There Is Only One Solution, Get a Second Opinion;Chapter 67: Understand the Impact of Change;Chapter 68: You Have to Understand Hardware, Too;Chapter 69: Shortcuts Now Are Paid Back with Interest Later;Chapter 70: "Perfect" Is the Enemy of "Good Enough";Chapter 71: Avoid "Good Ideas";Chapter 72: Great Content Creates Great Systems;Chapter 73: The Business Versus the Angry Architect;Chapter 74: Stretch Key Dimensions to See What Breaks;Chapter 75: If You Design It, You Should Be Able to Code It;Chapter 76: A Rose by Any Other Name Will End Up As a Cabbage;Chapter 77: Stable Problems Get High-Quality Solutions;Chapter 78: It Takes Diligence;Chapter 79: Take Responsibility for Your Decisions;Chapter 80: Don't Be Clever;Chapter 81: Choose Your Weapons Carefully, Relinquish Them Reluctantly;Chapter 82: Your Customer Is Not Your Customer;Chapter 83: It Will Never Look Like That;Chapter 84: Choose Frameworks That Play Well with Others;Chapter 85: Make a Strong Business Case;Chapter 86: Control the Data, Not Just the Code;Chapter 87: Pay Down Your Technical Debt;Chapter 88: Don't Be a Problem Solver;Chapter 89: Build Systems to Be Zuhanden;Chapter 90: Find and Retain Passionate Problem Solvers;Chapter 91: Software Doesn't Really Exist;Chapter 92: Learn a New Language;Chapter 93: You Can't Future-Proof Solutions;93.1 ;Chapter 94: The User Acceptance Problem;Chapter 95: The Importance of Consomme;Chapter 96: For the End User, the Interface Is the System;Chapter 97: Great Software Is Not Built, It Is Grown;Colophon;
기본정보
ISBN | 9780596522698 ( 059652269X ) |
---|---|
발행(출시)일자 | 2009년 03월 17일 |
쪽수 | 220쪽 |
크기 |
155 * 227
* 13
mm
/ 299 g
|
총권수 | 1권 |
언어 | 영어 |
Klover
e교환권은 적립 일로부터 180일 동안 사용 가능합니다.
리워드는 작성 후 다음 날 제공되며, 발송 전 작성 시 발송 완료 후 익일 제공됩니다.
리워드는 리뷰 종류별로 구매한 아이디당 한 상품에 최초 1회 작성 건들에 대해서만 제공됩니다.
판매가 1,000원 미만 도서의 경우 리워드 지급 대상에서 제외됩니다.
일부 타인의 권리를 침해하거나 불편을 끼치는 것을 방지하기 위해 아래에 해당하는 Klover 리뷰는 별도의 통보 없이 삭제될 수 있습니다.
- 도서나 타인에 대해 근거 없이 비방을 하거나 타인의 명예를 훼손할 수 있는 리뷰
- 도서와 무관한 내용의 리뷰
- 인신공격이나 욕설, 비속어, 혐오발언이 개재된 리뷰
- 의성어나 의태어 등 내용의 의미가 없는 리뷰
리뷰는 1인이 중복으로 작성하실 수는 있지만, 평점계산은 가장 최근에 남긴 1건의 리뷰만 반영됩니다.
구매 후 리뷰 작성 시, e교환권 200원 적립
문장수집
e교환권은 적립 일로부터 180일 동안 사용 가능합니다. 리워드는 작성 후 다음 날 제공되며, 발송 전 작성 시 발송 완료 후 익일 제공됩니다.
리워드는 한 상품에 최초 1회만 제공됩니다.
주문취소/반품/절판/품절 시 리워드 대상에서 제외됩니다.
구매 후 리뷰 작성 시, e교환권 100원 적립