I want to be a qualified engineer and a qualified engineer

I want to be a qualified engineer and a qualified engineer

I want to talk about it. After a three-month trial period in the new company, I finally completed the confirmation reply two days ago, in fact, the answer is two project managers in two of our project teams (one project manager is about to leave, and the other is two months new, the former is used as the project manager .), Another person is a colleague. Even a department manager or a slightly larger leader did not participate in my defense. I feel that the answer has no meaning, but the question is that the new project manager says "I have plans to study in training courses" and "I want to learn about database applications ", I don't think it's just a simple irony. Is my infrastructure too poor? In fact, I did not use MVC before I came to this company, and this capability is also slightly weaker than this project manager. But I can say that my other abilities will never be lost to him. Because the Code he wrote and the implementation methods of some functional points have seen a little. Let me show you the following:

I want to use left join. He said that I want to use inner join to not Display Error Data. In fact, I want to display the error data and solve the problem after discovery. The hidden problems will never be saved, user Data is getting messy.

I used in, and he used =. I learned that it is really inefficient to use in, because our company didn't need to think too much about this problem, leading to my writing habits, the execution speed is acceptable to the customer. After all, the customer's data volume is there.

As I mentioned above, I have corrected my problems. But do not use the kind of attitude that you stand tall, and others are not satisfied. I didn't know it.

Let's talk about the question "How can I be a qualified engineer". As a web software engineer, we must know the basics of four points: front-end, backend, database, and deployment. Each point is a requirement. It is called a "standard" in professional terms ". In fact, this specification is accumulated over a long period of time, and the experience described in texts is convenient for everyone to use together, improving work efficiency and avoiding disorder. First 《. the beauty of NET, written by Zhang Ziyang 《. net project code style requirements below I start with these four points, gradually talk about my understanding and experience, pay attention to the way I will adopt flashback, improper points I hope you will correct.

I. Deployment

A. Introduction

When we build a web project, we always need to install and deploy it on the customer's server. Different server hardware and server system software will affect the use of the software.

B. Requirements

1) Hardware: servers are divided into blades, towers, and racks.

2) software: Windows Server series and Linux Series

3) Network: Lan, man, Wan

C. Understanding and experiences

Why do we need to master the above knowledge? This is because different customer levels have different requirements for the office environment. After all, these environments are linked to money, the consideration and funding for small customers and major customers are different. This gives us the information we need to know when positioning our products. This is related to the number of users, number of online users, concurrency and data volume. In this way, we can push back the quality of the deployment environment that the customer can provide us. Then, in the coding stage, the code implementation method will certainly be affected by these conditions. (Note: Linux can deploy. net mvc, and the article link is ghost)

Ii. Database

A. Introduction

The database aims to store data. Currently, mainstream relational databases include Oracle, DB2, Microsoft SQL Server, Microsoft Access, and MySQL.

B. Requirements

Master SQL statements, triggers, stored procedures, functions, cursors, views, indexes, and so on. Although the syntax of each database is quite different, the learning cost of SQL Syntax of other databases is reduced by learning one of them.

C. Understanding and experiences

No matter who you are, I want to understand that data is a "gold" concept. Whenever there is a problem with our electronic products, we will worry about whether the data in it will be lost or not. Whenever someone uses our electronic products, we will be careful if they will accidentally delete or mess up the data. You can imagine that data is sometimes not measured directly by money, because it is difficult to recover from loss or chaos.

The following are some suggestions for Database Design:

1) Ensure strong cohesion and weak coupling between tables

2) Avoid unnecessary data redundancy whenever possible

3) Try not to store one-to-many relationships in a field.

4) The column names must be clear, understandable, and unambiguous. Try to use common names. Do not be unconventional.

5) The most important thing is that the table name and column name should be annotated.

6) you can use a foreign key to establish a table relationship.

Note: In fact, most of these are the requirements of the three paradigm, but I found that many people are considering reading data through SQL at the later stage, without considering data maintenance, and whether the business is reasonable.Iii. Background

A. Introduction

In fact, this is very simple, that is, C #. Many people think that C # is very studious and Java is hard to learn. But I do not feel that it takes a long time for a language to be proficient.

B. Requirements

It is actually what we have mentioned in many books. It is not difficult to develop these skills.

C. Understanding and experiences

1) There must be a hierarchical classification concept of code

2) good comments

3) standard coding style

4) Strong encapsulation capability (simplified parameters, less heavy load, and more optional parameters)

5) code optimization

6) The column names must be clear, easy to understand, and unambiguous. Try to use common names.

Iv. Front-end

A. Introduction

This is the html part, which is also a weakness of many. net engineers. Of course it is also my weakness. But I will make some basic adjustments and some code specifications. It also involves the placement of various folders and files in the project.

B. Requirements

Html, css, and JavaScript

C. Understanding and experiences

1) css and js reference sequence, css first and then js

2) js I have always thought it is to improve the user experience and is not suitable for a large number of client operations.

3) the front-end code should be spam and useless and meaningless comments should be cleared.

4) encapsulate js

5) debugging, css and js

6) Front-end Optimization

Here we will do 1 ~ Reply to the reply on the 6 th floor: First of all, I would like to thank all the friends of the park for making bricks. I wrote this article by the way, rather than focusing on the content, we can learn from blog posts. I believe everyone has heard of it, "you can give me some advice, but please don't give me some advice ". I have also stressed that it is my problem and I must correct it. This is my progress. I know exactly where my vulnerabilities are. When new colleagues are not familiar with each other, they will come to a conclusion later. If you are not sure about it, don't say it, because everyone has been working for several years and will have their own fixed thinking. The problem I mentioned earlier was caused by a similar problem in the project team, so there is no need to talk about it separately. Maybe he has his own considerations in implementation. In a word, I have no glass heart, and I have nothing to hold down. The pressure also requires you to have such a problem. If you have any problems, simply say the problem. Do not deliberately zoom in on small issues, especially for some specific occasions. Otherwise, it will only make others think you are false. There is no way to deceive people when developing programs and Program Programs closely tied to your ability to work.