English | MP4 | AVC 1280×720 | AAC 48KHz 2ch | 1h 02m | 155 MB
In nearly every organization, developers are forced to grapple with old code that gets in the way of writing new features. Is legacy code limiting your development team’s agility? If so, let this course be your guide for how to embrace a legacy system and improve it while paying down technical debt. Instructor Scott Ford explains how to review legacy code and fence in the technical debt by creating and running a test suite. He also demonstrates how to introduce dependency management and update dependences and tools, how to remove noise and distractions from your code, and how to keep technical debt at bay by remaining test driven and monitoring code quality.
Topics include:
- Assessing the technical debt
- Creating and running a test suite
- Handling failing tests
- Updating dependencies and tools
- Paying down technical debt
- Remaining test driven
- Monitoring code quality
Table of Contents
1 Embrace the legacy and tackle the debt
2 What you should know
3 Definitions
4 Familiarize yourself
5 Remember the prime directive
6 Take ownership
7 Set up a dev environment
8 Skim the code
9 Technical debt grows without tests
10 Create a test suite (if one is missing)
11 Run the test suite
12 Handle failing tests
13 Build out test coverage
14 Build dependency behavior tests
15 Aging tools make technical debt worse
16 Introduce dependency management
17 Update dependencies and tools
18 Remove noise and distractions
19 Read by refactoring
20 Isolate external services and devices
21 Code like a scientist
22 Technical debt will grow like weeds
23 Stay test driven
24 Practice refactoring
25 Keep code clean
26 Monitor code quality
27 Next steps
Resolve the captcha to access the links!