Coverart for item
The Resource Working effectively with legacy code, Michael C. Feathers

Working effectively with legacy code, Michael C. Feathers

Label
Working effectively with legacy code
Title
Working effectively with legacy code
Statement of responsibility
Michael C. Feathers
Creator
Subject
Language
eng
Summary
"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."--Jacket
Member of
Cataloging source
VLB
http://library.link/vocab/creatorName
Feathers, Michael C
Dewey number
005.1
Illustrations
illustrations
Index
index present
Language note
English
LC call number
QA76.76.A65
LC item number
F43 2005
Literary form
non fiction
Nature of contents
dictionaries
Series statement
Robert C. Martin series
http://library.link/vocab/subjectName
  • Application software
  • Application software
  • Engineering & Applied Sciences
  • Computer Science
Label
Working effectively with legacy code, Michael C. Feathers
Instantiates
Publication
Note
Includes index
Carrier category
online resource
Carrier category code
  • cr
Carrier MARC source
rdacarrier
Color
black and white
Content category
text
Content type code
  • txt
Content type MARC source
rdacontent
Contents
  • 4.
  • seam model
  • 5.
  • Tools
  • 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?
  • Foreword
  • 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
  • Robert C. Martin
  • 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
  • 1.
  • 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?
  • Changing software
  • 24.
  • We feel overwhelmed : it isn't going to get any better
  • 25.
  • Dependency-breaking techniques
  • App.
  • Refactoring
  • 2.
  • Working with feedback
  • 3.
  • Sensing and separation
Control code
660166658
Dimensions
unknown
Extent
1 online resource (xxi, 434 pages)
Form of item
online
Isbn
9780132931748
Media category
computer
Media MARC source
rdamedia
Media type code
  • c
Other physical details
illustrations.
http://library.link/vocab/ext/overdrive/overdriveId
0be0d0ae-965d-4cf0-9ece-112e5a05587d
Specific material designation
remote
System control number
(OCoLC)660166658
Label
Working effectively with legacy code, Michael C. Feathers
Publication
Note
Includes index
Carrier category
online resource
Carrier category code
  • cr
Carrier MARC source
rdacarrier
Color
black and white
Content category
text
Content type code
  • txt
Content type MARC source
rdacontent
Contents
  • 4.
  • seam model
  • 5.
  • Tools
  • 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?
  • Foreword
  • 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
  • Robert C. Martin
  • 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
  • 1.
  • 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?
  • Changing software
  • 24.
  • We feel overwhelmed : it isn't going to get any better
  • 25.
  • Dependency-breaking techniques
  • App.
  • Refactoring
  • 2.
  • Working with feedback
  • 3.
  • Sensing and separation
Control code
660166658
Dimensions
unknown
Extent
1 online resource (xxi, 434 pages)
Form of item
online
Isbn
9780132931748
Media category
computer
Media MARC source
rdamedia
Media type code
  • c
Other physical details
illustrations.
http://library.link/vocab/ext/overdrive/overdriveId
0be0d0ae-965d-4cf0-9ece-112e5a05587d
Specific material designation
remote
System control number
(OCoLC)660166658

Library Locations

    • Curtis Laws Wilson LibraryBorrow it
      400 West 14th Street, Rolla, MO, 65409, US
      37.955220 -91.772210
Processing Feedback ...