Announcements
Learning Objectives:
This lecture is about writing code that other people will be able to understand, reuse, and modify. We've distilled this down to five general program-design princples which should be best practices for effective programmers:
- Use Names and Indentations Wisely
- Make Your Data Mean Something
- One Method/One Job
- Don't Repeat Yourself
- Identify and Use Good Abstractions
In this lecture, you will learn to:
- Describe the purpose of our best practices for code-level design
- 5 principles for designing readable code, illustrated with examples
- Identify some violations of the practices and suggest ways to mitigate them
Important Dates:
Lecture:
Activity
Resources
- Code Style Policy for this class
- Book: "The Programmer's Brain" by Felienne Hermans
- Post: "What is cognitive load"
- Paper: I know what you did last summer: an investigation of how developers spend their time, Minelli, Mocci and Lanza
- Paper: A metric for software readability, Buse and Weimer
- Paper: To camelcase or underscore, Dave Binkley et al