The best way to understand a dense chunk of code is to refactor it as you go. Explore just the refactoring basics here, mostly extract method and rename a variable, nothing fancy.
- [Instructor] Chances are that you've encountered a chunk … of code that was so difficult to understand, … you didn't even know where to begin. … Situations like that are perfect candidates … for the read by refactoring technique … that was first created by Arlo Belshee. … As the name implies, this technique involves employing … refactoring to make changes to the code … as you're reading it. … More specifically, the changes that you're making … are very small. … And each one is attempting to capture some understanding … that you've gained from reading the code. … For example, … if you encounter a variable with a name … that doesn't clearly indicate how it's used, … you can study the code a little bit … to gain a better understanding … of what that variable is doing. … And then use the renamed variable refactoring … to improve the variables name. … Here on the screen, … we have a small method from the Ruby Sinatra library. … We're specifically looking at version 1.0, … which was released back in 2010. …
Author
Released
11/1/2019- 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
Skill Level Intermediate
Duration
Views
Related Courses
-
Agile Software Development
with Shashi Shekhar1h 53m Beginner -
Agile Software Development: Code Quality
with M. Scott Ford1h 40m Intermediate -
Agile Software Development: Refactoring
with Richard Kasperowski1h 31m Intermediate
-
Introduction
-
Definitions2m 2s
-
1. Getting Started: Review the Technical Debt
-
Familiarize yourself2m 48s
-
Remember the prime directive1m 53s
-
Take ownership1m 59s
-
Set up a dev environment4m 50s
-
Skim the code3m 18s
-
-
2. Fence in the Technical Debt
-
Run the test suite1m 23s
-
Handle failing tests2m 34s
-
Build out test coverage3m 11s
-
3. Improve Your Tools
-
4. Pay Down Technical Debt
-
Read by refactoring3m 35s
-
Code like a scientist2m 49s
-
5. Keep Technical Debt at Bay
-
Stay test driven1m 39s
-
Practice refactoring1m 39s
-
Keep code clean1m 10s
-
Monitor code quality1m 34s
-
Conclusion
-
Next steps51s
-
- Mark as unwatched
- Mark all as unwatched
Are you sure you want to mark all the videos in this course as unwatched?
This will not affect your course history, your reports, or your certificates of completion for this course.
CancelTake notes with your new membership!
Type in the entry box, then click Enter to save your note.
1:30Press on any video thumbnail to jump immediately to the timecode shown.
Notes are saved with you account but can also be exported as plain text, MS Word, PDF, Google Doc, or Evernote.
Share this video
Embed this video
Video: Read by refactoring