"Pragmatic Programmer" the fifth book review

41 pragmatic team

• Without leaving broken windows

• Do not do the frog in warm water, always noted that external changes such as requirements, business policies

• Do not repeat yourself

• Orthogonality: focus on functionality rather than job titles organized

42 ubiquitous automation

Do not manually

automation:

• test

• Construct

• Generate code

• Approval process