Agile Software Development: Clean Coding Practices

Agile Software Development: Clean Coding Practices
Agile Software Development: Clean Coding Practices
English | MP4 | AVC 1280×720 | AAC 48KHz 2ch | 1h 04m | 179 MB

As a writer of code, the complier isn’t your only audience. Your coworkers—and even your future self, when you fix bugs—must be able to easily understand your original intent. In this course, learn why it’s important to write code that’s clean—or, easily understood by both computers and humans—and how to do it in practice. Instructor Scott Ford reviews how to ensure that different aspects of your code are clearly and thoughtfully constructed, including names, formatting, and logic. Plus, he explains what a “clean” unit test looks like, and how to ensure that your tests are fast and efficient.

Topics include:

  • The importance of clean names
  • Naming classes and types
  • Rules for naming local and member variables
  • Why clean formatting matters
  • Making good use of loops
  • Keeping your unit tests isolated
Table of Contents

1 Write code for humans, not machines
2 What you should know
3 Clean code definition
4 Why are clean names important
5 Prefer clarity over brevity
6 Acronyms and abbreviations
7 Class and type names
8 Method and function names
9 Variable names
10 Parameter names
11 Constant names
12 Why clean formatting matters
13 Indendation and bracket placement
14 Line wrapping
15 Whitespace
16 Comments
17 Magic numbers and constants
18 Parameter lists
19 Predicate methods
20 Making good use of loops
21 What’s a unit test
22 Keep your tests fast
23 Single assertion per test
24 Keep your tests isolated
25 DRY vs. WET tests
26 Next steps