How to become a master

This is a summary of today's communication with the school recruiting new colleagues. I hope the school recruiting new colleagues can review and write their own summary.

 

1. What isCodeMaster? How do you prove that you are a master of code?

There are many people who know many code skills and JS colorful skills. You know how many. NET functions are meaningless. It doesn't make sense to know how many new IT terms and technical introductions you have. It makes sense to build a prototype, build a project, and solve your difficult problems.

1. quickly and accurately understand what others say-> -〉

2. Rapid Development also accurately reflects others' needs-> -〉

3. stable, with minimal bugs-> -〉

4. High Performance: you can hold on to 0.1 million records. Can you hold on to 10 million records? This is a test of technical skills

5. This is not enough. Can your code be quickly understood by others?

6. Can your code easily accept the requirements of different customers?

This requires your analytical skills, architecture skills, and coding skills everywhere.

2. How to become a master?

1. Read excellent Open SourceSource code. The amount of code is small first. Thoroughly read and analyze the relationships between classes and classes. Why design such a class architecture and why design interfaces like this. These ideas are quite deep.

2. Modify the open source code as needed. Because the open-source code is an integrated system, whether the functions you add are well integrated with the existing code. This is a test of knowledge.

3. Reading: who invented this thing and who studied whose book. To learn
Sqlserver, you must read the books written by the sqlserver Development Manager or technical team. Books written by others may be ambiguous. Read through and read the design principles repeatedly. Do not just learn to use it. Ratio
For example, if SQL Server is used, does SQL Server understand SQL Server and SP? We must understand how SQL Server's data page is organized. Why is it organized like this?
How is it loaded into the memory and written back to the physical device. We need to reach this depth. Otherwise, you only have to know what it means. You can watch it as a master at ordinary times. When it comes to real difficulties, you can immediately take a break.

If the technology you have learned does not help you solve your current problems, it means that you have not learned enough.

4. Find your master. It is difficult for a person to learn and learn from each other.
Refining. This process is slow. If you want to develop rapidly, you must find your guide in this company. He may be your mentor or someone else. You must observe and be positive when you look at it.
Contact him closely and follow him. I usually ask him more about his ways of thinking and how to do things.

5. Establish a belief for yourself:I want to become a recognized technical expert in the company in X years. I want to become the first-class software industry in China at the end of XProgramMember.
Goals must be set up and always strive for this goal. Every day, we have to read, think, develop, and modify code for over 16 hours. One story tells us that it takes 10 thousand hours for every professional task to succeed. That's what I mean. Not crazy.

Iii. Recommended Bibliography:

1. the. NET Enterprise Application Architecture Model provides an overview of the data layer, business layer, and performance layer, with moderate difficulty and depth, but a comprehensive picture. It is recommended to read. Let everyone see that enterprise-level software development is not a package of VB.net + SQL. Let everyone understand the product code structure from the perspective of architecture.

2. R & D culture: <> the it r & D culture I have read is very good.
. It truly reflects the complexity, anxiety, pressure, and creation of software development. In addition, there are two other books that are also good and worth recommending. They are: "follow the wisdom", which tells the story of the establishment of the Microsoft Asia Research Institute.
Borland legends describes the ups and downs of Borland's IT industry changes, business wars, and technological changes.

After you read these three books, you will be amazed at the twists and turns and difficulties of the birth of a successful product, and how many business competitions will happen in the middle, how many independent code heroes will emerge.

I often say whether a person can become a software master or not. He has an unclear temperament. You know, it is the programmer spirit. He is different from each other and you can clearly feel it.

3. I usually read the magazine programmer, which contains many cutting-edge technical trends. There are also entrepreneurs and IT manager world, which have good IT applications.

However, as an individual, technically, I have always focused on the data architecture layer and intermediate architecture layer. I have no experience in front-end architecture and design. In terms of business, I have been paying attention to industrial chains, industrial clusters, supply chains, production sequence decomposition, light companies, Internet life services, Internet marketing, and Internet customer relationships.Community.

 

Last sentence:

The ultimate beauty is crazy. I hope everyone can make up their minds when developing every product in their daily work: It's my
Baby!

 

Yes, it is the child you have created. You need to care for it with your heart.