Learn C++ Online

This lesson contains approximately 25 minutes of video content.

Always write readable code

Sources of errors, your program, defensive programming

Questions

QS&E Pt.1, Q1

This question is ungraded.

Which of the following is best practice when writing readable code?

Avoid false clues that obscure the meaning of your code, like `friend_list` for a vector variable.

Names can vary from each other in small ways.

Never use single-letter variable names in any case.

`genymdhms` is a good name for generation date, year, month, day, hour, minute, and second.

Practice question: try as many times as you like

QS&E Pt.1, Q2

This question is ungraded.

Bjarne Stroustrup said, "My guess is that avoiding, finding, and correcting errors is % or more of the effort for serious software development." What integer value fills in the blank?

Practice question: try as many times as you like

QS&E Pt.1, Q3

This question is ungraded.

In this course, which of the following is correct when it comes to sources of errors?

You can assume users will always give valid inputs.

You should always check all data from external sources, input parameters.

You should worry about misbehaving hardware.

You should worry about misbehaving system software.

Practice question: try as many times as you like

QS&E Pt.1, Q4

This question is ungraded.

In the lesson video Always write readable code, we ask you to "Use consistent lexicon" during our discussion of . Fill in the blank with the best answer.

Avoid disinformation

Avoid mental mapping

Make meaningful distinctions

Meaningful names

Pick one word per concept

Use pronounceable names

Practice question: try as many times as you like

QS&E Pt.1, Q5

This question is ungraded.

In the lesson video Always write readable code, we state "Clarity is king" during our discussion of . Fill in the blank with the best answer.

Avoid disinformation

Avoid mental mapping

Make meaningful distinctions

Meaningful names

Pick one word per concept

Use pronounceable names

Practice question: try as many times as you like

Software and errors (part 1)

Always write readable code

Sources of errors, your program, defensive programming

Questions

Q1

QS&E Pt.1, Q1

Q2

QS&E Pt.1, Q2

Q3

QS&E Pt.1, Q3

Q4

QS&E Pt.1, Q4

Q5

QS&E Pt.1, Q5