Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with legacy-system
Search options not deleted
user 147
Legacy code can mean a number of related things, the most common of which are code inherited from someone else; code from a previous version of the application; code that is deprecated or outdated; or code that is untested. Many legacy systems meet all these criteria, and legacy code typically requires a different, more delicate approach than new code.
37
votes
1.5 Million lines of code. 0 tests. Where should we start?
I seem to recall there is a book that specifically addresses this exact scenario. Just a sec while I search Amazon...
...here we go: Working Effectively with Legacy Code
I admit I haven't read this …
- 784