Perl Best Practices (excerpt)---01

Written in the first chapter:

--------------------------------------------------------------------------------------

This series is the learning excerpt from the Perl best practices!

Interested friends can use the mailbox and I communicate! (You are very welcome to communicate)

My email: veic_2005#163.com (replace # with @)

------------------------------------------------------------------the perfect dividing line---Chapter One: Best Practices 1.1 three goals

A good coding style can reduce the cost of a software project. 1.1.1 Strong

L Coding style can minimize the chance of first mistake.

The coding style helps to check for incorrect boundary conditions (edge case), where the defect is often invisible.

L Coding style helps you avoid components that cannot be properly scaled (construct).

The coding style can improve how the program code handles failures.

The coding style can improve how the program code should respond to failures.

L Coding style can improve the structure of program code. 1.1.2 Efficiency 1.1.3 Maintainability

In general, the time to maintain program code is at least 4 times times that of writing program code. (Note 1)

Note that maintenance costs and initial development costs are 4:1 of the results are often referred to as the Boehm law (BOEHMS ' laws). Over the past 30 years, the real world has been observing that maintenance is more dominant than development, but the actual cost ratio is from 2:1 to 10:1 of what is significantly exceeded.

6 months after you complete the code, the program code is just like someone else wrote (note 2)

Note This is the law of Eagleson (Eaglesons ' laws). Other experts painfully assert that the critical time interval is approximately 3 weeks.

Perl Best Practices (excerpt)---01