第 1/1 張圖片
圖片庫
第 1/1 張圖片
有類似物品要出售？
Robert C. Martin Ser.: Clean Code : A Handbook of Agile Software...
US $18.25
大約HK$ 141.98
狀況：
良好
曾被閱讀過的書籍，但狀況良好。封面有諸如磨痕等在內的極少損壞，但沒有穿孔或破損。精裝本書籍可能沒有書皮。封皮稍有磨損。絕大多數書頁未受損，存在極少的褶皺和破損。使用鉛筆標注文字處極少，未對文字標記，無留白處書寫文字。沒有缺頁。
Oops! Looks like we're having trouble connecting to our server.
Refresh your browser window to try again.
運送：
免費 USPS Media MailTM.
所在地：Eagle Mountain, Utah, 美國
送達日期：
估計於 9月18日 (星期四)至 9月22日 (星期一)之間送達 運送地點 94104
退貨：
不可退貨.
保障：
請參閱物品說明或聯絡賣家以取得詳細資料。閱覽全部詳情查看保障詳情
（不符合「eBay 買家保障方案」資格）
賣家必須承擔此刊登物品的所有責任。
eBay 物品編號：316993513814
物品細節
- 物品狀況
- ISBN
- 9780132350884
關於產品
Product Identifiers
Publisher
Pearson Education
ISBN-10
0132350882
ISBN-13
9780132350884
eBay Product ID (ePID)
28068284382
Product Key Features
Number of Pages
464 Pages
Publication Name
Clean Code : a Handbook of Agile Software Craftsmanship
Language
English
Subject
Software Development & Engineering / Quality Assurance & Testing, Software Development & Engineering / General, Information Theory
Publication Year
2008
Type
Textbook
Subject Area
Computers
Series
Robert C. Martin Ser.
Format
Trade Paperback
Dimensions
Item Height
0.9 in
Item Weight
26.1 Oz
Item Length
9.2 in
Item Width
7 in
Additional Product Features
Intended Audience
Scholarly & Professional
LCCN
2008-024750
Dewey Edition
22
Illustrated
Yes
Dewey Decimal
005.1
Table Of Content
Foreword xix Introduction xxv On the Cover xxix Chapter 1: Clean Code 1 There Will Be Code 2 Bad Code 3 The Total Cost of Owning a Mess 4 Schools of Thought 12 We Are Authors 13 The Boy Scout Rule 14 Prequel and Principles 15 Conclusion 15 Bibliography 15 Chapter 2: Meaningful Names 17 Introduction 17 Use Intention-Revealing Names 18 Avoid Disinformation 19 Make Meaningful Distinctions 20 Use Pronounceable Names 21 Use Searchable Names 22 Avoid Encodings 23 Avoid Mental Mapping 25 Class Names 25 Method Names 25 Don''t Be Cute 26 Pick One Word per Concept 26 Don''t Pun 26 Use Solution Domain Names 27 Use Problem Domain Names 27 Add Meaningful Context 27 Don''t Add Gratuitous Context 29 Final Words 30 Chapter 3: Functions 31 Small! 34 Do One Thing 35 One Level of Abstraction per Function 36 Switch Statements 37 Use Descriptive Names 39 Function Arguments 40 Have No Side Effects 44 Command Query Separation 45 Prefer Exceptions to Returning Error Codes 46 Don''t Repeat Yourself 48 Structured Programming 48 How Do You Write Functions Like This? 49 Conclusion 49 SetupTeardownIncluder 50 Bibliography 52 Chapter 4: Comments 53 Comments Do Not Make Up for Bad Code 55 Explain Yourself in Code 55 Good Comments 55 Bad Comments 59 Bibliography 74 Chapter 5: Formatting 75 The Purpose of Formatting 76 Vertical Formatting 76 Horizontal Formatting 85 Team Rules 90 Uncle Bob''s Formatting Rules &n
Synopsis
Even bad code can function. But if code isn't clean, it can bring a development organization to its knees. Every year, countless hours and significant resources are lost because of poorly written code. But it doesn't have to be that way. Noted software expert Robert C. Martin presents a revolutionary paradigm with Clean Code: A Handbook of Agile Software Craftsmanship . Martin has teamed up with his colleagues from Object Mentor to distill their best agile practice of cleaning code "on the fly" into a book that will instill within you the values of a software craftsman and make you a better programmer--but only if you work at it. What kind of work will you be doing? You'll be reading code--lots of code. And you will be challenged to think about what's right about that code, and what's wrong with it. More importantly, you will be challenged to reassess your professional values and your commitment to your craft. Clean Code is divided into three parts. The first describes the principles, patterns, and practices of writing clean code. The second part consists of several case studies of increasing complexity. Each case study is an exercise in cleaning up code--of transforming a code base that has some problems into one that is sound and efficient. The third part is the payoff: a single chapter containing a list of heuristics and "smells" gathered while creating the case studies. The result is a knowledge base that describes the way we think when we write, read, and clean code. Readers will come away from this book understanding How to tell the difference between good and bad code How to write good code and how to transform bad code into good code How to create good names, good functions, good objects, and good classes How to format code for maximum readability How to implement complete error handling without obscuring code logic How to unit test and practice test-driven development This book is a must for any developer, software engineer, project manager, team lead, or systems analyst with an interest in producing better code., Even bad code can function. But if code isn't clean, it can bring a development organisation to its knees. Every year, countless hours and significant resources are lost because of poorly written code. But it doesn't have to be that way. Noted software expert Robert C. Martin presents a revolutionary paradigm with Clean Code: A Handbook of Agile Software Craftsmanship. Martin has teamed up with his colleagues from Object Mentor to distil their best agile practice of cleaning code "on the fly" into a book that will instil within you the values of a software craftsman and make you a better programmer--but only if you work at it. What kind of work will you be doing? You'll be reading code--lots of code. And you will be challenged to think about what's right about that code, and what's wrong with it. More importantly, you will be challenged to reassess your professional values and your commitment to your craft. Clean Code is divided into three parts. The first describes the principles, patterns, and practices of writing clean code. The second part consists of several case studies of increasing complexity. Each case study is an exercise in cleaning up code--of transforming a code base that has some problems into one that is sound and efficient. The third part is the payoff: a single chapter containing a list of heuristics and "smells" gathered while creating the case studies. The result is a knowledge base that describes the way we think when we write, read, and clean code. Readers will come away from this book understanding How to tell the difference between good and bad code How to write good code and how to transform bad code into good code How to create good names, good functions, good objects, and good classes How to format code for maximum readability How to implement complete error handling without obscuring code logic How to unit test and practice test-driven development, Even bad code can function. But if code isn't clean, it can bring a development organization to its knees. Every year, countless hours and significant resources are lost because of poorly written code. But it doesn't have to be that way. Noted software expert Robert C. Martin presents a revolutionary paradigm with Clean Code: A Handbook of Agile Software Craftsmanship . Martin has teamed up with his colleagues from Object Mentor to distill their best agile practice of cleaning code "on the fly" into a book that will instill within you the values of a software craftsman and make you a better programmer but only if you work at it. What kind of work will you be doing? You'll be reading code lots of code. And you will be challenged to think about what's right about that code, and what's wrong with it. More importantly, you will be challenged to reassess your professional values and your commitment to your craft. Clean Code is divided into three parts. The first describes the principles, patterns, and practices of writing clean code. The second part consists of several case studies of increasing complexity. Each case study is an exercise in cleaning up code of transforming a code base that has some problems into one that is sound and efficient. The third part is the payoff: a single chapter containing a list of heuristics and "smells" gathered while creating the case studies. The result is a knowledge base that describes the way we think when we write, read, and clean code. Readers will come away from this book understanding How to tell the difference between good and bad code How to write good code and how to transform bad code into good code How to create good names, good functions, good objects, and good classes How to format code for maximum readability How to implement complete error handling without obscuring code logic How to unit test and practice test-driven development This book is a must for any developer, software engineer, project manager, team lead, or systems analyst with an interest in producing better code.
LC Classification Number
QA76.76.D47M3652
賣家提供的物品說明
賣家信用評價 （251）
- eBay automated Feedback- 買家留下的信用評價。過去 1 個月Order completed successfully – tracked and on time
- eBay automated Feedback- 買家留下的信用評價。過去 1 個月Order completed successfully – tracked and on time
- eBay automated Feedback- 買家留下的信用評價。過去 1 個月Order completed successfully – tracked and on time
賣家信用評價 （251）
- eBay automated Feedback- 買家留下的信用評價。過去 1 個月Order completed successfully – tracked and on time
- eBay automated Feedback- 買家留下的信用評價。過去 1 個月Order completed successfully – tracked and on time
- eBay automated Feedback- 買家留下的信用評價。過去 1 個月Order completed successfully – tracked and on time