|
|
|
|
| LEADER |
02822cam a2200301Ia 4500 |
| 001 |
99919133204151 |
| 005 |
20241030105349.0 |
| 008 |
050427s2005 maua 001 0 eng d |
| 010 |
|
|
|a 2004108115
|
| 020 |
|
|
|a 0131177052
|
| 020 |
|
|
|a 9780131177055
|
| 035 |
|
|
|a (OCoLC)59715717
|
| 035 |
|
|
|a (OCoLC)ocm59715717
|
| 040 |
|
|
|a UNA
|c UNA
|d OCL
|d DLC
|d OCLCQ
|d OCLCO
|d U@S
|
| 049 |
|
|
|a U@SA
|
| 050 |
0 |
0 |
|a QA76.76.A65
|b F43 2005
|
| 082 |
0 |
0 |
|a 005.1
|2 22
|
| 100 |
1 |
|
|a Feathers, Michael C.
|
| 245 |
1 |
0 |
|a Working effectively with legacy code /
|c Michael C. Feathers.
|
| 260 |
|
|
|a Boston :
|b Addison-Wesley :
|b Prentice Hall :
|b Pearson Education,
|c c2005.
|
| 300 |
|
|
|a xxi, 434 p. :
|b il. ;
|c 25 cm.
|
| 490 |
1 |
|
|a Robert C. Martin series
|
| 500 |
|
|
|a Incluye índice.
|
| 505 |
0 |
|
|a Foreword / Robert C. Martin -- Preface -- Introduction -- Part I. The mechanics of change: 1. Changing software -- 2. Working with feedback -- 3. Sensing and separation -- 4. The seam model -- 5. Tools -- Part II. Changing software: 6. I don't have much time and I have to change it -- 7. It takes forever to make a change -- 8. How do I add a feature? -- 9. I can't get this class into a test harness -- 10. I can't run this method into a test harness -- 11. I need to make a change : what methods should I test? -- 12. I need to make many changes in one area -- 13. I need to make a change but I don't know what tests to write -- 14. Dependencies on libraries are killing me -- 15. My application is all API calls -- 16. I don't understand the code well enough to change it -- 17. My application has no structure -- 18. My test code is in the way -- 19. My project is not object-oriented : how do I make safe changes? -- 20. This class is too big and I don't want it to get any bigger -- 21. I'm changing the same code all over the place -- 22. I need to change a monster method and I can't write tests for it -- 23. How do I know that I'm not breaking anything? -- 24. We feel overwhelmed. It isn't going to get any better -- Part III. Dependency-breaking techniques: 25. Dependency breaking techniques -- Appendix: Refactoring.
|
| 520 |
1 |
|
|a "In this book, Michael Feathers offers start-to-finish strategies for working more effectively with large, untested legacy code bases. This book draws on material Michael created for his own renowned Object Mentor seminars: techniques Michael has used in mentoring to help hundreds of developers, technical managers, and testers bring their legacy systems under control." "This book also includes a catalog of twenty-four dependency-breaking techniques that help you work with program elements in isolation and make safer changes."--Descripción del editor.
|
| 650 |
|
0 |
|a Application software
|x Development.
|
| 650 |
|
7 |
|a Software de aplicación
|x Desarrollo.
|2 UDESA
|
| 830 |
|
0 |
|a Robert C. Martin series
|