First-year work summary

The 12.26 th day of last year is one year after my graduation. Because I have not been blank some time ago, I will write my work summary for this year today. It is estimated that I will write it every year in the future.

The first time I wrote a work summary, I first thought about what to write.

Let's talk about what we have done this year.In fact, my first job company is not the current business software, but a game company. Because this company is relatively small and only offers 4 K/month, it is difficult to work (I was asked to migrate a mobile phone to Android with a classmate), and no guidance was given, so I resigned. Because I think I must be able to learn something at work. It is best for the company to have a master. I know that I am not competent for this job. later, I jumped to the current shangtai software for mobile phone navigation UI, because it was the first Development Year 1 ~ Our work in March is very busy, basically working overtime every day, usually until in the evening. Our boss also accompanied us to add. In April, the project can be demonstrated in basic construction, but the boss is not satisfied with the design, SO 4 ~ In May, I changed the design and made it in May, but the effect is still not good. 6 ~ In August, another version of design was changed. 8 ~ Improved functions in September. 9 ~ In October, I wrote the design document (because it was first developed, So I first wrote the code and did not write the design document). In November ~ Now, it is easy to modify bugs and correspond to new functions, which basically enters the maintenance stage.

 

Then I will talk about my work experience.My work is the UI part of the program. I am mainly responsible for calling the underlying data interface and displaying the interface. I perform logical control on interface operations and migration. The project process in the company is as follows:

Project-style group design style based on the company's actual situation-design group design interface (need to negotiate with the UI group to see if it can be implemented)-UI layout according to design

-"Underlying group (MAP, search, path ...) provide interfaces for the UI according to the style requirements (this type of interface, so that the UI group does not care about data storage, transmission)-"the UI calls the interfaces provided by the underlying layer

The above is the entire project process, of course, this class does not contain the test part. during work, we need to coordinate the style, design, and bottom layer.

Coordination with style:You need to consider whether the underlying layer provides such an interface to complete this function. Is this function reasonable? Is there any case missing if the UI can be implemented.

Coordination with design:Whether the layout can be implemented and whether the design is reasonable. Some of the effects we can achieve on the UI side can be negotiated and recommended with the design, which will help the design.

Coordination with the underlying layer:How can the underlying interface provide the function to fulfill the style requirements? Is this interface asynchronous or synchronous? For the convenience of the UI side, you can submit the interface requirements to the underlying layer.

Communication in coordination:Communication is indispensable at work. If you encounter problems that cannot be solved, ask your colleagues, ask the leaders, and communicate with other groups. when I first started my work, I was not used to communicating with people, that is, solving problems by myself. Sometimes I had to make a phone call and had no logic. the following summarizes some of my experiences during the past year.

1. When you encounter a problem that cannot be solved, if it is a simple problem (the so-called simple here is that you only need to ask someone else, you may get the answer immediately) you should not hesitate to ask, if it is a complicated problem, try to solve it by yourself first, but it cannot be solved, and then ask your colleagues or leaders again.

2. When communicating with other groups, do not think about what you should talk about during communication. You only need to be clear about the problems you want to communicate.

3. If you disagree, you 'd better discuss it (such as writing emails)

4. The progress should be reported in a timely manner. You should try your best to let everyone know about your work (in the group.

SVN server usage: A code management tool is used in the company, and the server maintains a set of (or N sets) version of code (of course not just code, style, design can be placed on top ). the employee downloads the files from the server and starts his/her work. If there are any modifications and the changes need to be reflected to the version, the employee can upload the files to the svn server.

 

Gains at work:

In the past year, I became familiar with the company's basic work process, and used the OA system to manage the attendance information. The entire project development process to the maintenance process, the communication at work, and the most important thing is the technical improvement.

In terms of technology:

1. Familiar with Java syntax and format

2. Call method of JNI Interface

3. proficient in Ui Layout

4. Improved Reading Capability

5. Familiar with Android system controls

Outlook for next year:

 

Work Requirements for next year:

1. Quiet.

2,Learning EnglishFocuses on reading documents. I hope to be familiar with the development documents next year. I plan to use 10 words every day.

3,Complete the basic Android tutorial blog in English.

4. Continue to learn about the Android system.

5. Learn the Java language and design patterns.

6. The company changed to a formal employee because I felt that although the treatment of the dispatched employee is no different from that of the formal employee, the formal employee said that there would be some face-to-face and guaranteed.

7. The salary should be at least 7 K +,

8. If both 5 and 6 are not satisfied, I plan to skip the slot once. It is expected that the end of the year will be reached.

Conclusion:

Day up.