Software transition development

zhaozj2021-02-16  101

Software Transition Development: The programmer uses unnecessary ways, which has adopted unnecessary extensions on the developed software. Divided into technical and business transitions. Technically, programmers generally learn the purpose To use new learning things to have a daily work. Business, programmers want to expand some components to meet the designs that may not form.

Any project manager or the development manager has a headache for this, not only does not complete the task on time, but also the problem of low software performance, difficult to maintain.

new technology

New technology is the number one sinner developed by the transition. Sometimes, for a very simple demand, whether the customer / manager / sales / technical supervisor often recommends the latest technology (of course, the purpose), the most advanced design. Results Do you have any words. I have taken over a system, there are two phases. The first phase uses JSP / servlet, the second phase is Struts, EJB. Leave only pain, the first phase More tidy, written things are easy to understand, directly, maintenance is also very simple. The second process is to change the edge, the customer is not satisfied, and it is not satisfied.

new method.

Let's take a look at this program.

class:

Class a {

Private int ID;

Public void getId () {

Return ID;

}

Public void setid (int id) {

THIS.ID = ID;

}

}

Method A

A geta () {

A a = new a ();

A.SetId (GetValuea ());

Return A;

}

Method B

Interface updater () {

Public int getValueid ();

}

Class A1 Extends a {

Public A1 (Updater UPD) {

setId (Upd.getValueID ());

}

}

A geta () {

A1 A1 = New A1 (New Updater () {

Public int getValueid () {

Return getValuea ();

}

}));

Return A1;

}

It can be compared, methods A and methods B. From several respects, code length / execution efficiency / maintenanceability, who is omnipotent? Really unimaginable, can write method B's programmer can spend so much Write such a "difficulty" and "challenge" code.

Future demand

This is an idea that the designer or programmer will often commit a mistake. I have also made this mistake. At that time, I needed to operate an XML file. The way DOM provided was not enough. I spent a few days. A common class for an XML file operation. The result is a lot, and the method that can be used is then a bit. Now think about it, it is really stupid.

To know what is needed, what is not helpful, I grew up slowly.

转载请注明原文地址:https://www.9cbs.com/read-11757.html

New Post(0)