There is a fall that you are not worthy of your ambition, and you have failed to suffer. --ifsblack
2014, in one word, that's pain .
For my 2013 years of career development goals-machine vision, I embarked on a painful transformation of the road
- Last year do the car networking Six months, familiar with TI's dsp--many machine vision companies are using TI DSP, although not a series of chips
- In the first half of this year in Rigol do ultra-high-performance liquid chromatography, familiar with the SPI and can bus and communication protocol design-This is not related to machine vision-I thought I could do the development of optical components of the detector on the chromatograph, but the enterprise only use your strengths
- In the second half of this year in Ericsson do the router OAM subsystem, familiar with the Linux application development and C + + language-machine Vision Library OPENCV is implemented in C + +
- whole 6 month in the idle period saw Gonzalez" Digital Image Processing "(English version) of the first 3 chapters, but the exercise to do 3rd Chapter 7th problem do not go down
To working summary:
- To make a definite move. Before writing the code must have a plan as detailed as possible, the program to work with colleagues review carefully, if colleagues also feel flaky, then do a few more programs to ensure that the thinking is clear and complete, and then write code.
- To have a phased outcome. All companies are result-oriented, in the field of software development, spend 1 months to write 10 modules but not run up, the effect is far worse than write only 1 modules but can run up and run stably.
- Stabilize the bottom layer first. Software is usually layered, the lower layer must first do the stability (through full testing to achieve), then do the upper layer, or the top of the problem, you do not know whether the upper layer itself has problems, or it depends on the underlying problems. This is not contradictory to the previous article, if the duration is tight, you can do feature set very small bottom, but must be stable!
- Assess risks and escalate risks in a timely manner. Even if the plan is well-planned, the implementation of the process will still be unexpected, it is important to report the accident as soon as possible, let the team know your difficulties.
- Actively face the leadership of the reprimand. Napoleon said: "Never (the problem you encounter) attributed to (others) malicious, this is precisely the (your own) incompetence", if the leader scold you, most of the time, it is really you have a problem, then ask yourself what to do wrong, really do not understand to ask the leader where he did wrong. To have rise above it consciousness.
Life Aspects:January 8, can mouth scheme overturned 5 times, big change more than 10 times, small change did not stop, the results of my design documents in up to 2.5 hours of review was granted a useless. March 19 Rigol Mister Wang Yue Please research and Development Department instrument group to eat and drink, his left arm tied with Crape, the original is mother died-high place cold. March 30 visit Beijing Botanical Garden. April 5 Visit the National Museum.
May 31 Separation Rigol.
June 1 with the letter along with the Shidu played the next rafting.
June 7 30 stand, go to the Temple of Heaven to celebrate!
June 22 Summer Palace Day tour.
July back to Xi ' an to collect the house, hands through the intermediary Maya House rented to others, experience the feeling of being a landlord.
July 14, Pactera, outsourced to Ericsson.
August 17 in Jinsong mouth put me on the crown of 4 years, 22nd number with team to go to Tsing Lung Gorge farm, mountain climbing.
September and with the letter to go to Zhangjiakou walk around, all kinds of ancient Great Wall highlights desolation, oat face didn't imagine the delicious, back found ID lost.
October National Day to wife's home, September 30 with the graduate students in the same dormitory, Jia Zhi eat, 4 years gone.
From October 10 to November 13, one months of development of Lua Binder eventually failed.
November 14 to December 14, engaged in one months of network management message Repeater, success.
December 16 to date, engaged in a half-month card incident report, because the need to communicate the issue did 5 version is not over, to cross the year.
2014 Year-end summary
