Editing Technical books and notes
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
== Business/Publishing_and_Printing/Publishing/Books/Business/Addison_Wesley == | == Business/Publishing_and_Printing/Publishing/Books/Business/Addison_Wesley == | ||
=== The Pragmatic Programmer === | === The Pragmatic Programmer === | ||
* … | * … | ||
== Business/Publishing_and_Printing/Publishing/Books/Business/Manning == | == Business/Publishing_and_Printing/Publishing/Books/Business/Manning == | ||
=== Minimal Perl === | === Minimal Perl === | ||
Line 11: | Line 9: | ||
== Business/Publishing_and_Printing/Publishing/Books/Business/O'Reilly_and_Associates == | == Business/Publishing_and_Printing/Publishing/Books/Business/O'Reilly_and_Associates == | ||
=== 97 Things Every Programmer Should Know === | === 97 Things Every Programmer Should Know === | ||
==== #06: Before You Refactor ==== | ==== #06: Before You Refactor ==== | ||
* The best approach for restructuring starts by taking stock of the existing codebase and the tests written against that code. | * The best approach for restructuring starts by taking stock of the existing codebase and the tests written against that code. | ||
Line 54: | Line 51: | ||
==== installing the tools elsewhere ==== | ==== installing the tools elsewhere ==== | ||
Appendix A lists the command-line tools together with their home pages. | Appendix A lists the command-line tools together with their home pages. | ||