- Format
- Häftad (Paperback)
- Språk
- Engelska
- Antal sidor
- 456
- Utgivningsdatum
- 2004-10-01
- Upplaga
- 1 Ed. of 2005
- Förlag
- PRENTICE-HALL
- Dimensioner
- 235 x 175 x 30 mm
- Vikt
- Antal komponenter
- 1
- Komponenter
- ,
- ISBN
- 9780131177055
- 840 g
Du kanske gillar
-
Hacking: The Art of Exploitation Book/CD Package 2nd Edition
Jon Erickson
Mixed media product -
Refactoring
Martin Fowler
Inbunden
Working Effectively with Legacy Code
WORK EFFECT LEG CODE _p1
Fri frakt inom Sverige för privatpersoner.
Passar bra ihop
De som köpt den här boken har ofta också köpt The Pragmatic Programmer: From Journeyman to Ma... av Andrew Hunt, David Thomas (häftad).
Köp båda 2 för 970 krKundrecensioner
Fler böcker av Michael Feathers
-
The Art of Unit Testing
Roy Osherove, Michael Feathers, Robert C Martin
Dies ist ein umfassendes Handbuch zum Arbeiten mit Unit Tests. Es führt Sie Schritt für Schritt von einfachen Unit Tests bis hin zu Tests, mit denen sich der Code umfangreicher Softwareprojekte überprüfen und analysieren lässt. Das Buch ist für .N...
Bloggat om Working Effectively with Legacy Code
Övrig information
MICHAEL C. FEATHERS works for Object Mentor, Inc., one of the world's top providers of mentoring, skill development, knowledge transfer, and leadership services in software development. He currently provides worldwide training and mentoring in Test-Driven Development (TDD), Refactoring, OO Design, Java, C#, C++, and Extreme Programming (XP). Michael is the original author of CppUnit, a C++ port of the JUnit testing framework, and FitCpp, a C++ port of the FIT integrated-testing framework. A member of ACM and IEEE, he has chaired CodeFest at three OOPSLA conferences. (c) Copyright Pearson Education. All rights reserved.
Innehållsförteckning
Preface.
Introduction.
I. THE MECHANICS OF CHANGE.
1. Changing Software.
2. Working with Feedback.
3. Sensing and Separation.
4. The Seam Model.
5. Tools.
II. CHANGING SOFTWARE.
6. I Dont 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 Cant Get This Class into a Test Harness.
10. I Cant 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 Do I Have To Break.
13. I Need To Make a Change but I Dont Know What Tests To Write.
14. Dependencies on Libraries Are Killing Me.
15. My Application Is All API Calls.
16. I Dont 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 Dont Want It to Get Any Bigger.
21. Im Changing The Same Code All Over the Place.
22. I Need To Change a Monster Method and I Cant Write Tests for It.
23. How Do I Know That Im Not Breaking Anything?
24. We Feel Overwhelmed. It Isnt Going To Get Any Better.
III. DEPENDENCY BREAKING TECHNIQUES.
25. Dependency Breaking Techniques.
Appendix: Refactoring.
Glossary.