Dev Express, a new company's web development choice control, is too bad and found that the project structure is also chaotic.

The Ajax model is different from other models.

There is no popular AjaxPanel concept. There is a callbackpanel written according to its example. The result shows that the object is null and is not selected. After reading other people's code, I found that many users have to use the client to pass the value. (The help in official documents is not easy to understand, and its model is also characteristic)

3-4 times more code writing

Aspxgridview should use a complicated method to deal with rotten custom pages. (If you find that some code is not paged at all, you can directly obtain 1000 entries and bind them .. It puts a lot of pressure on elder brother and it is too difficult to rewrite. I can't stand it anymore .) Telerik's onneed_datasource model is powerful.

 

I used to develop projects. It's just like the cloud is running smoothly, and it's too bad. A bunch of long code is encountered when you change the code or add a new function. More than 200 rows. HTML does not need to be written in the code.

Every in-depth development of a function finds that the code is poorly written. And they are accompanied by 1-3 super obvious bugs.

Later, we can only modify and refactor the new functions, which makes it impossible to complete them smoothly. Those with little impact can only be placed first. Step by step, the Code is not very good. It is unlikely that the entire process is complete.

 

The project architecture is not consistent (The purpose of the WCF framework application is unclear, and N multiple projects fight for each other .)
Project structure, (N classes will be placed in the same file) folder is not well divided, the public base class project is not well done.
The development process is not completed. (If the previous round of functions is not completed, and the test is not completed, the next round of development will be conducted .)
The project owner does not recognize or check the code written by team members.

The function level is not good. There are too many repeated codes. The function is too long. Responsibilities are not independent. All the mistakes were made.

However, the entire project can still run.

 

The most important thing is the process. That is, we need to have a structure for the entire project. In this way, the people who come in later can continue to work in this structure. Then the owner should take care of the new users. Then slowly reduce the observation.

Make sure that the code it writes meets the standard requirements (more important than the code writing specifications .)

1. Simply put, a page carries multiple functions, and the independent usercontrol should be independent. Instead of the side where the page is always mixed.

2. Repeat the code more than twice and you must organize it.

3. A single class has a single responsibility. Sort related items together and remove irrelevant ones. Too big to consider whether to split.

4. Use the design mode. Instead of making n more catch.

5. The unit of the transfer type in the project should be a class, rather than a string to be combined into another method, which can be split again (it was never imagined that someone was using this method)

6. When the business model (domain model) has no inheritance significance, do not inherit it because their physical models are similar. There is no need (the SQL statements generated using the ef4.1 results are terrible, and thousands of rows of thousands of SQL statements are used .)

7. Don't make things simple and complicated. A lot of simple things are much more complicated (some are restricted by class libraries. But it is more caused by humans. For example, the paging of a bird grid will become complicated)

8. reasonably separate directories (as the amount of Code increases, this move should continue)

9. N classes are written as a file (Forbidden. Facilitate quick code locating)

In the 10.html structure, the contained items must be included, rather than the parallel relationship. In the Li structure, they are independent options.

11. Do not use N checkboxes where checkobxlist is used properly.

(To be continued, if any new problem is found)

Conclusion: you will feel the beauty of the Code, as if the world was supposed to be like this. People who need to write code have a sensitive heart to feel them and abstract and summarize them.

Author: lovebanyi
Source: http://www.cnblogs.com/Lovebanyi/
About the author: I am engaged in automated stock trading software
The copyright of this article is shared by the author and the blog. You are welcome to repost this article. However, you must keep this statement without the author's consent and provide the original article connection clearly on the article page.