Summarizes the work week (3)

This week's advance work less than ideal. First table design, the system might have been related to the impact of naming framework comes with a table, we did not do a very good leader in the design naming the table, some fields with pinyin spelling of some words with the head letters, lower case some completely, some with a small hump as userName, some with a large hump as UserName, some fields with the words, these names appear in different styles when a data table, often giving a very messy feel, for example, some words you do not know what that means, spelling better said, but on the field all lowercase English blinded, because in the end the last letter of a word is not clear which, when multiple words field, this is the problem . Another point, the field is set in the MSSM in field descriptions, but some fields in the design of the field did not clearly written instructions, such as a certain type of representation or state int type field, indicating only write "** state "or" ** type ", it is very general terms, can clear the usefulness of this particular field, the information should be put to the known, such as UserType: user type [0: user 1: salesman, 2: other……】.

There is the problem of the project target framework, and now I do not know how you think the boss, the boss is skilled, but let us use the framework is webform, and this is a wonderful framework that can do background management system, write interface returns json, more wonderful is that the user interface is the background and something called a developer platform through a framework by configuring engage in out, in short, it is everything can be solved by configuration. Currently I feel that I have the ability to write basic sql statement, there are a number of c # basic skills and knowledge of front-end, but I'm embarrassed to write the code is not clear where? This goal went wide ...... framework framework is .net framework2, some of the components on the frame can run properly on the target framework 2.0 or 3.5, but the 4.0, some components will not work, though not an error. The question is precisely when I was writing before the two-dimensional code generation and posters calling Ali cloud messaging features, the project will target the 4.0 framework changed, after the project is compiled without error, it did not find problems with the framework. So it is submitted, know two days after it was noted that some components have a bug, we realized the problem target framework, finalized up to 3.5 no problem. This means that I write or call the two methods of finishing to be adapted to suit the low version, is really very unhappy, the other 3.5, many grammar habits are impossible, really is enough. I am not convenient lose their jobs, you can only choose to break slowly adapt to this framework.

Because not familiar with this framework, the framework and example in the use of small, frame maintenance or off-site developer with us. So sort out the business logic to identify some basic table design and effects Figure out some of my first basic logic functions written by stored procedures. Case and then later determine the project will use this framework to write and does not allow the use of stored procedures, I will write stored before conversion by splicing sql way in the program. Well, originally a logical access a database on the line, now may need to access a database of more than three times the job. Really not used to, like the boss on the line, the function can do out on the line. One more point, and now Microsoft officials have declared .net core is .net alternatives, and the official made clear that asp.net core asp.net higher than in performance, attachment should be very clear in Microsoft's Internet companies or developers after the road.

Friday, when customers come, might imagine, before customer sign a contract, it is not what you want to see the product prototype and renderings, and even the requirements document did not give. Friday you can imagine, the results of the customer was gone. Most functions are cut off, or that are not currently needed in the future that may be required. So, this is a major problem in the process, but considering that this is a newly established subsidiary, so it can be understood. Summarize the lesson is, do the prototype when the prototype knowledge consent leadership, technology leadership agreed, but fewer customers agree. Renderings do is look at the prototype, the front end is looking at renderings do. Prototype is a problem, then back to work for nothing is not normal for you? Our technology leadership, or is the project leader, in effect drawing and the front end had been done when it is the first time to communicate with customers, then carry out major changes. So, no sooner and customers to communicate technical level it is also a problem later have to pay attention. In my current experience or knowledge, the Internet company to others should be the product of this process roughly like this:

Talk about customer service manager, technician or business personnel to do the prototype, operational and technical staff to reach a consensus on the prototype, prototype review by the customer to view, and then propose amendments, the technology has chosen to modify the prototype and reached a consensus with the user to determine the prototype select the database design renderings make technical implementation, the user confirms the renderings (visual effects involving only changes), renderings consensus, front and rear side development.

Above, the most important is a multi-and customer communication, selectively comply with the wishes of customers, prototype / renderings find out first customer to confirm consensus.

Guess you like

Origin www.cnblogs.com/gds-1202b/p/11261832.html