Lecture 5 Flashcards

1
Q

Why is pair programming not necessarily inefficient?

A

There is evidence that it works.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What is a team benefit for pair programming?

A

Sharing of knowledge that happens during pair programming is very important as it reduces the overall risks to a project when team members leave.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

How does the code benefit from pair programming?

A

It helps support refactoring - collective ownership and immediate feedback.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What is 2x4 pair programming?

A

1-2 3-4 5-6
1-6 3-2 5-4
so on…

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What, at a high level, continuous integration achieves?

A

Automated build and product releases.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Why deploy regular builds?

A
  • Frequent regression testing and refactoring

* Make sure the code doesn’t compromise current build

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What are the four environments for continuous deployment?

A
  • development
  • integration
  • staging
  • production
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What type of methods should be documented?

A

Public and protected

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What should a comment include for a method?

A

• Description

Params, return, throws

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What is self-documenting code?

A

Careful choice of naming classes, interfaces, enums, variables.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What code comments shouldn’t do?

A

Explain poorly written code.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What is Ant?

A

An XML build for that is generally platform independent.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly