After more than a year of employment, I became more familiar with my work and became more and more comfortable! Of course, the most profound feeling and the biggest change is the work mentality. Last year, I first came into contact with maps. My work was mainly at the learning stage. I had too many idea projects and tried many experiments in my spare time. At that time, my mentor always stressed that I must have output. At that time, this sentence was indeed heard. No matter what you do, you will write a document. Of course, the document mainly records a lot of details. Every day, you still insist on using Evernote to write a work diary, after a short summary of various details, output a document to the mentor. Later, I had to stick to it.
OpenKingsoft DiskIt is filled with various idea documents and technical ppt files previously written.EvernoteIt records the daily work content. Work diaries are written every day, and many idea files are recorded in time from time to time. Good idea emails are sent to the Group for discussion. More and more documents, more and more busy and more specialized. Documents are stored there, but they are rarely viewed, especially the work diaries filled with various details. For those ideas and documents that are not summative enough, I am too lazy to open them later. Remember before mentor leaves
In my last communication with me, I asked me if I had any idea recently. I smiled and said, "I have no idea. It is enough to do everything well. At that time, mentor was a little disappointed, because every time he talked to me and asked me what I thought during the year of employment, I would share something I had done with him for the first time. He often listened with appreciation.
There are several reasons for changes:
1. I am not energetic. I am very tired when I work for a day.
2. There are a lot of things. Different things need to be prioritized and assigned weights.
3. The previous work was not good enough, because I didn't realize what would happen when I looked back at the document for a year later. All some documents are filled with too many details, and the summative nature is not strong enough. It is difficult to enter the previous state at once.
One year of employment, the main task is to learn and do the following:
1) use OpenGL to draw traffic conditions in real time in a graphical manner.
Output:
One, a PPT was shared in a group for the first time. The PPT contains some conclusive data and charts, even though it looks intuitive now.
An APK package cannot be installed now. You need to manually configure the texture resources required for painting. It is too troublesome to find and install the texture resources in time, don't bother getting it anymore...
2) use the FBO method to plot road conditions as textures and then draw road conditions as images.
This idea was implemented only in May, but unfortunately there was no demo APK. At that time, the effect was very good for others. Later, the android system was too wonderful.
3) street scene highlight Road Network demo
Nothing left.
4) I have made a survey on rendering performance of different models. I still keep a batch of Excel files I wrote earlier, which record the time when different models were used to draw different images. It seems that it is of little significance now.
5) The road network data is compressed, and a document records the entire process. But now it seems that the most significant thing is the table in it, which optimizes the data size comparison before and after optimization.
6) last year, I had some more in-depth studies on OpenGL. At that time, I had written a PPT, or a blog, which is still of great significance to the present.
7) The latest Android ADT and ndk support native code debugging in eclipse. At that time, mentor asked me to do research, and I also made a ppt and shared it with a group. Check it from time to time.
8) the Apache server development and nginx + FastCGI Server installation and configuration development last year were summarized and output in a timely manner when the status was good.
Of course there are still many ideas,GtaskMany idea lists in are not completed yet. The above nonsense is a personal experience. At the time of employment, mentor said that it should be output and the team lead said that it should always be summarized and maintained. When I heard a report from Niu Ren a few days ago, I should be good at summarizing the methodology http://blog.csdn.net.
These are really "Old Man's words", experience!
Looking back at the past, there are successful and failed things: Successful things have outstanding conclusions and are of guiding value to the present. What fails is the documents filled with various details, direct Delete is a bit reluctant, so it won't look at it again.
So much nonsense, just want to explainSummary, induction, and document writing. Work must start and end with good understanding. Only a summary can mark the completion or complete termination of the work. When doing things, you must write a document to summarize the details. The longer the time, the more details you forget, and the more you pay attention to the conclusions, the possibility of re-occurrence of states that are addicted to various details is also getting lower and lower...
The summary can be in various forms: Word documents, emails, PPT, pure comparison data, graphical tables, and executable programs. In short, the summary content must be intuitive, concise, and easy to reproduce (such as executable programs must be easy to install), in order to minimize the review cost.