|
|
|
|
| LEADER |
04281nmm a2200541 u 4500 |
| 001 |
EB001913903 |
| 003 |
EBX01000000000000001076805 |
| 005 |
00000000000000.0 |
| 007 |
cr||||||||||||||||||||| |
| 008 |
210123 ||| eng |
| 020 |
|
|
|a 0136083250
|
| 020 |
|
|
|a 9780136083252
|
| 020 |
|
|
|a 9780136083221
|
| 020 |
|
|
|a 0136083226
|
| 050 |
|
4 |
|a QA76.76.D47
|
| 100 |
1 |
|
|a Martin, Robert C.
|
| 245 |
0 |
0 |
|a Clean code
|b a handbook of agile software craftsmanship
|c Robert C. Martin ; [with] Michael C. Feathers [and others]
|
| 260 |
|
|
|a Upper Saddle River, N.J.
|b Prentice Hall
|c 2009
|
| 300 |
|
|
|a xxix, 431 pages
|b illustrations
|
| 505 |
0 |
|
|a Includes bibliographical references and index
|
| 505 |
0 |
|
|a Clean code -- Meaningful names -- Functions -- Comments -- Formatting -- Objects and data structures -- Error handling -- Boundaries -- Unit tests -- Classes -- Systems -- Emergence -- Concurrency -- Successive refinement -- JUnit internals -- Refactoring serialdate -- Smells and heuristics -- Appendix A: Concurrency II -- Appendix B: Org.jfree.date.serialdate -- Appendix C: Cross references of heuristics -- Epilogue
|
| 653 |
|
|
|a Computer software / Reliability / fast
|
| 653 |
|
|
|a Computer software / Reliability / blmlsh
|
| 653 |
|
|
|a Agile software development / blmlsh
|
| 653 |
|
|
|a Logiciels / Fiabilité
|
| 653 |
|
|
|a COMPUTERS / Software Development & Engineering / General / bisacsh
|
| 653 |
|
|
|a Agile software development / fast
|
| 653 |
|
|
|a Agile software development / http://id.loc.gov/authorities/subjects/sh2007006411
|
| 653 |
|
|
|a Computer software / Reliability
|
| 653 |
|
|
|a Méthodes agiles (Développement de logiciels)
|
| 700 |
1 |
|
|a Feathers, Michael C.
|
| 041 |
0 |
7 |
|a eng
|2 ISO 639-2
|
| 989 |
|
|
|b OREILLY
|a O'Reilly
|
| 490 |
0 |
|
|a Robert C. Martin series
|
| 776 |
|
|
|z 0136083234
|
| 776 |
|
|
|z 9780132350884
|
| 776 |
|
|
|z 9780136083252
|
| 776 |
|
|
|z 9780136083238
|
| 776 |
|
|
|z 0136083226
|
| 776 |
|
|
|z 9780136083221
|
| 776 |
|
|
|z 0132350882
|
| 776 |
|
|
|z 0136083250
|
| 856 |
4 |
0 |
|u https://learning.oreilly.com/library/view/~/9780136083238/?ar
|x Verlag
|3 Volltext
|
| 082 |
0 |
|
|a 005.1
|
| 082 |
0 |
|
|a 620
|
| 520 |
|
|
|a 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
|
| 520 |
|
|
|a 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.
|
| 520 |
|
|
|a 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.
|