"Summary" 2014 Annual summary

2014 Annual Summary

2014 can be divided into two stages, one stage in the school half a year, another phase is the work of half a year time. (a summary of the school, I will not write here)

Time, such as fleeting, half a year in a twinkling. I have been in the job for 6 months now. 6 months is a process of growth and a process of school going to society.

During this time, I got the first one of my own wages, and did the first so-called Project. Before the school, always thought that the actual project should be how tall, how a difficult method, thinking that their own knowledge, there is no way to apply to the actual development. But when it comes to the project, finding a normal project is not as difficult as it might be.

The work time is too fast, faster than in the school. At present, there are many places to study in the new job. It is a fast learning process, both in business and in technology as well as in personal ability.

The following summarizes the six months of harvest, summarize what you learned, and integrate information.

In these 6 months, my harvest is as follows:

First, technical

A) Front end

1. CSS promotion, compatibility adjustment, can be compatible with IE7 and the following versions, Google, etc.
2. The skillful use of JS and jquery (Getting started)
3. Use of Ajax
4. Getting Started with Flex technology (currently in development)
5. Use of the Bootstrap,easyui,jqwidgets,highchart,ztree front-end framework (Getting started)

b) Service-side

1. Upgrade of MSSQL Database
2. Getting Started with Oracle databases
3. The use of Ibatis (instead of the previously used ADO)
4. Getting Started with MVC mode, Getting started with Sqlite (doing a user management system "Easyui+mvc+sqlite")

c) Other

1. Powerdesign skilled use, and some efficient tips
2. Use of SVN version control software (team collaboration development, code management)
3. Use of the company's general background configuration system
4. Understanding of the Company Flex foreground configuration system

Ii. operational (to be strengthened)

1. In the first month of the job, one months of testing--"familiar with and understanding of the company's business
2. In the development process, the knowledge of the business is relatively small. (understanding basic knowledge of getting started, concepts (Eg: Storm surges, what are red tides?) ））

Third, the workplace experience

A) July 2014: some sermon.

1. Completing a task is not equal to getting the result. Results are measurable, valuable and quantifiable (induction training)
2. Perfect to let oneself have the biggest promotion (induction training)
3. Can speak in a short language, do not have too much nonsense (induction training)
4. Interpersonal communication--"and the other side as the center (induction training)
5. Planning is a good habit, every day to have their own goals, you can put the target in the form of sticky notes on the desktop (recommended: Child desktop notes)
6. Learn to summarize and plan, every day will write summary, tomorrow plan. Summary let yourself know what has been harvested recently, plan to let oneself always have a goal, all have the direction of effort.

b) August 2014:

1. Normalization of projects in team collaboration (file, code naming specification, file directory specification, comments)
2. The speech needs to have a clear context. The PPT of the speech best yaotu multiple less. The most important point is to consider what might happen in the middle of the speech and prepare some emergency solutions.
3. Work and study to maintain a good mindset

c) September 2014

1. A task can be clearly divided into several implementation steps, and then to achieve
2. Project needs to connect with others, to timely follow up, not clear where, but also to promptly ask clearly. Do not wait for the problem to butt, otherwise you will do a lot of useless
3. If you are experiencing a lot of repetitive work, take a moment to consider whether there is a more efficient solution, rather than directly copying and pasting the start
4. Group opinion is inconsistent, and no way to achieve the same, then the simple implementation of their own solutions, more timeliness. Choose a high-timeliness (one problem will have multiple solutions).

D) October 2014

1. Front-end and server-side docking (data format, parameter delivery type), and after the server has written the interface, to provide the corresponding interface description document.
2. Spend time cleaning up the business logic in your project, and the smoothness of development and the bugs left behind.
3. Prepare soft test "software designer" (bought two books on the internet, chewed for almost one months) "passed"

e) November 2014

1. Re-experience the importance of project specification in team development.
2. Understand the importance of flowchart (quick interpretation of code, according to the flowchart interpretation)
3. Realize the importance of thinking in development (project development, the idea of the project is very clear, it is easier to achieve)

f) December 2014

1. Experience the object-oriented sweetness (abstract encapsulation of functionality)--"to be strengthened
2. When the project manager has provided the page, then we have to make the page and the same (there is a better way to continue to communicate in the changes)
3. The importance of debugging (be flex to die, do flex development, do not want to install the debug version of Adobe Flash Player, installed on the internet will always pop up the error dialog box)

g) 2014 Summary (a collection of experiences that are deeper in each month)

1. In the work, the short language can be understood, do not talk too much nonsense.
2. Be able to plan your own time, make plans, and plan your computer on the desktop. Recommended "Child desktop Notes"
3. Develop the habit of writing a summary and writing the next plan
4. The importance of the discourse (making it easier for listeners to receive)
5. Importance of Project normalization in team development (description of document planning, file directory normalization, code naming, annotation normalization)
6. Learn the division of tasks, divide large tasks into smaller tasks, and then implement them one after the other
7. Solutions that disagree with the group (the timeliness of their respective solutions, simple implementation of the following solutions)
8. In the development, the importance of the idea of mastery (clear thinking, then high efficiency.) ---"ax)
9. Debugging importance (Program development = dev + Test + Debug)
10. Experience the object-oriented sweetness, a learning direction
11. Technology does not lie in mastering how many kinds, but in mastering how deep. (depth first, then expand breadth)

Iv. projects that have been done, or works

a) company ( the project name will not be disclosed )

1. Item 1 (Data maintenance: More than 500 tables, repeated work too much)
2. Item 2 (Data maintenance: The importance of understanding the idea of mastery)
3. Item 3 (Front-End presentation: page layout tips)
4. Flex3.0 configuration system (Feature development: Drag Control--"generates a configuration file in the specified format)
5. Data transfer Program (c/S: for transfer of internal and external network data)

b) Personal

1. Personal blog (there is a design flaw, the front and back of the station did not leave)
2. User Management System (Easyui+mvc+sqlite)
3. Family file Management System (Bishi)
4. Personal blog (Bishi), imitating

v. Notes, and summary of problems encountered in development (entry level, miscellaneous)

Outline:

Front End:

Service side:

Summary of development issues, tutorials for learning summary

"Summary" 2014 Annual summary