Where are all the pretty code running?

Where are all the pretty code running?

Author: cleverpig

Body:
The serverside Java conference was held in Las Vegas on September 6, May 9. At the meeting, Gregor hohpe told a Java expert that each software development team only employs the best and best programmers, which is certainly correct. Hohpe, software architect at Google, asked: "Which other company will say we want to hire an unintelligent engineer ?" He believes that bad programmers must be guilty in the computer science field.

However, hohpe questioned how he could discover defects in the Code if all application development projects use the first round of drafts. He is not satisfied with the comments such as "this is an error" or "verification required" in the code. How can the best and best programmers write such code and comments?

While repeating his keywords, he asked, "Where are all the pretty code running ?" He joked about software development in a joke tone: "Maybe the guard came in the middle of the night and messed up our code ."

As hohpe sees, code is often confused by common causes that can be prevented. The primary cause is that poor code causes more poor code. His theory is that if the initial developer of an application does not have clear code planning and can be understood by any programmer, Pandora's box will be opened.

The next thing starts with writing code by developers. Even if the code can be run, the Code itself is hard for other programmers to understand. Next, a programmer needs to perform one year of maintenance after the application is mounted. Code becomes a bunch of messy things.

Therefore, the second maintenance programmer may say to himself, "I only add my code here. It won't go bad ."

However, after several rounds of modification above, the feature code originally compiled by the best people has finally become worse and worse.

He provided some suggestions to the audience attending the serverside meeting to avoid the above issues. He said: "The Code forced to write won't be good. Let the next person think that you are making great efforts to write elegant code ." As an architect, he must first understand the value of modeling to applications. He said that this does not require a complicated modeling tool, and even drawing a model on a piece of paper can have good results.

Hohpe repeatedly stressed that programmers should write code for humans rather than for machines. "We need to model people's interactive behaviors," he said. This is especially important when it comes to user interfaces ." He suggested presenting applications to non-programmers to check whether the programmer's understanding of program work is correct for potential end users.

He warned that the so-called business logic is not always the same as what Programmers think. He said: "If the business logic is the same as what Programmers think, then it will not be so difficult. This is why it is important to find out how the end user interacts with the application ."

He urged Java programmers to use their Java experience to write well-designed code and make other programmers feel elegant. "Writing code for people rather than machines" is the core of hohpe's philosophy. He suggested that if programmers only write code for machines, they do not need Java and they can return to the era of assembly code.

Reference resources:
Gregor hohpe-where did all the beautiful code go? Online Video

Hohpe-where did all the beautiful code go? Download original text: [download files]

(This article is reproduced from matrix, original address: http://www.matrix.org.cn/resource/article/44/44414_beauty+code.html)