Agile Software Development: Clean Coding Practices
1h 5mIntermediate2019-11-04
Authors

M. Scott Ford
Software Remodeler, Polyglot Developer
Course details
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.
Learning objectives
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
Learning objectives
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
Skills covered
Agile Software DevelopmentProgramming FoundationsDevOpsSoftware DevelopmentDeep Dive (X:Y)
Concepts
0. Introduction
- 01 - Write code for humans, not machines
- 02 - What you should know
- 03 - Clean code definition
1. Clean Names
- 04 - Why are clean names important
- 05 - Prefer clarity over brevity
- 06 - Acronyms and abbreviations
- 07 - Class and type names
- 08 - Method and function names
- 09 - Variable names
- 10 - Parameter names
- 11 - Constant names
2. Clean Formatting
- 12 - Why clean formatting matters
- 13 - Indendation and bracket placement
- 14 - Line wrapping
- 15 - Whitespace
- 16 - Comments
3. Clean Logic
- 17 - Magic numbers and constants
- 18 - Parameter lists
- 19 - Predicate methods
- 20 - Making good use of loops
4. Clean Unit Tests
- 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
Conclusion
- 26 - Next steps